← 3fts.ai Concord Open full screen

It shows you what you can evidence, what is missing, and what to fix next.

Software alone cannot make you compliant.

A 3fts.ai product · NIS2 · DORA · GDPR

Three regimes.
One assessment.

Most organisations run NIS2, DORA and GDPR as three programmes, collect the same assurance three times, and find out at audit that one artefact was being asked for under three article numbers.

Concord keeps one control library, maps every control to every obligation it satisfies, and turns the gaps into one sequenced plan — with the article reference and the evidence behind each claim.

  • 58controls, written once
  • 69obligations mapped
  • 208control-to-article links
  • 37controls serving all three

The demo below is not a recording. It is the product’s Rust engine compiled to WebAssembly, running in this page: no account, no server, no network call, and nothing you enter leaves the browser.

What it answers

Three regimes, one model of the work

A regime is scored only where it applies, and the scope result says why. The same control can carry an Article 21 NIS2 measure, a DORA protection duty and a GDPR security obligation without pretending they are identical.

NIS2 · 23 obligations

Scope before size

Annex I and II, the Article 2 size screen, then the Article 3 essential/important ladder. A medium Annex I entity is important, not essential — the product applies both tests separately.

  • Art. 21(2) measures, including the “where appropriate” MFA qualifier
  • 24h / 72h / one-month reporting, with the final report run from the notification
  • Art. 27 digital-provider registry split from the Art. 3(3)-(4) national list
DORA · 20 obligations

Financial entities, not everyone

The Article 2(1) entity list, the small-insurer exclusion, and a critical ICT provider treated as an oversight case rather than scored against the financial-entity chapters.

  • ICT risk framework, detection, response, backup and learning
  • Incident clock from RTS 2025/301, capped by classification + 4h and awareness + 24h
  • Register of information, concentration and contractual clauses
GDPR · 26 obligations

Rights, records and the clock

Controller and processor duties are filtered by role; an Art. 3(2) actor gets the Article 27 representative obligation, and the breach clock is calculated rather than remembered.

  • ROPA, lawful basis, retention, DPIA and the rights in Chapter III
  • 72 hours to the authority; data subjects without undue delay
  • Transfers, processors and the small-organisation ROPA exemption

Test the assumption

Is that actually compliant?

Six statements we hear in almost every assessment. Hover or tap for the short answer and the article behind it. The point is not the verdict — it is the reasoning you can reuse.

We are 40 people, so NIS2 does not apply.

Hover or tap
Not automatically

The size test is at least 50 staff or turnover above €10m and balance sheet above €10m. Forty staff does not decide it: both financial tests can still bring you in, and sector rules can too.

NIS2 Art. 2(1); Annex I/II; national transposition

A medium-sized Annex I company is automatically essential.

Hover or tap
No

A medium Annex I entity is important, not essential. Essential is for large enterprises and specific cases (qualified trust services, TLD registries, telecoms, CER critical entities). The ladder is Article 3, not the Annex alone.

NIS2 Art. 3(1), (3)–(4)

A critical ICT provider must meet every DORA financial-entity duty.

Hover or tap
No

Financial-entity chapters apply to financial entities. A critical ICT third-party provider is subject to the oversight framework and its Article 30 contractual duties; it is not scored against the financial entity's risk chapters.

DORA Art. 2(1), 30–44

We published a privacy policy, so GDPR is done.

Hover or tap
No

A notice is one Article 13 duty. It does not create a lawful basis, a ROPA, security measures, a breach process or Article 28 processor contracts. A policy is evidence of transparency, not of compliance.

GDPR Arts. 5, 6, 13, 28, 30, 32–33

Every breach must be reported within 72 hours.

Hover or tap
It depends

GDPR's 72 hours applies to a personal-data breach likely to result in risk. NIS2 uses a 24-hour early warning, a 72-hour notification and a final report within one month. DORA has its own classification clock. The regime and the facts decide, not one number.

GDPR Art. 33; NIS2 Art. 23; DORA RTS 2025/301

The processor is responsible, so our GDPR problem is theirs.

Hover or tap
No

The controller remains responsible for the processing and for choosing a processor with sufficient guarantees. Article 28 requires a contract; the processor has its own duties, but it does not absorb the controller's accountability.

GDPR Arts. 28, 82

Not legal advice, and national transposition can change an answer. The point is the reasoning, not a verdict.

The demo

Use the product, not a video

The frame below is the real client, unchanged, talking to the Rust engine through WebAssembly. The buttons above it ask the frame to change view — the same click you would make in the app.

concord / demo / wasm Open full screen ↗

Try this: in Assessment, change GOV-01 from 3 to 2 and watch the score above fall; then open Roadmap and see the plan reorder. In Scope, change the headcount to 30 and watch a regime leave scope. In Incidents, calculate a NIS2 deadline.

The overlap

Find the work you do not have to repeat

This is the real crosswalk from the embedded content, not a sample typed for the page. Filter by regime to see which controls carry obligations in more than one.

208obligation-to-control links
150links that reuse an existing control
37controls serving NIS2, DORA and GDPR
52 controls

Loading the crosswalk from the content library…

The clock

The first hours decide the fine

Enter when you became aware. The embedded engine calculates every deadline for the regime and returns what each notification must contain. The numbers come from the same Rust code the app uses.

The clock is calculated in the demo frame, not on a server. Try a NIS2 case, then switch to DORA and watch the first deadline become earlier.

Choose a regime and a time; the engine will lay out the deadlines here.

The output

A document a board can argue with

The report carries the scope determination with reasons, the posture by regime, the ten largest gaps, the sequenced plan, the evidence position and the method — including what the score cannot tell you.

It is generated by the same Rust code, self-contained, and prints to PDF from the browser. No chart in it is a screenshot.

Open in a new tab

Traceable to the article

Every obligation carries its reference and the controls that answer it. The crosswalk is a curated reading, and the report says so; a reviewer can check each link against the text.

Runs on the device

The demo is WebAssembly in this tab, the workspace is local storage, and there is no analytics tag. The app itself is a single Rust binary with no unsafe code and two dependencies.

Honest about limits

It is not legal advice, not a certification, and not a guarantee. The open modelling gaps — DORA Art. 16, GDPR Arts. 9/22, national transposition — are written down rather than hidden.

One assessment. Three regimes.
Every claim with a receipt.

Open the demo and change an answer. If a control is mapped to the wrong article, or a scope rule reads differently in your Member State, tell the studio — the library is meant to be argued with.