NIS2 · Article 21 · Supply chain

NIS2 Wants
Evidence.
Not Promises.

Whether your business is in scope or sells to companies that are, you will be asked to show documented risk analysis and vulnerability handling. CyberRiskGuru builds that record as you work — and is honest about what it does not cover.

Does This Apply To You?

Two Ways NIS2 Reaches You.

Directly in scope

Your business is covered

Generally medium and large companies — 50 or more employees, or over €10 million turnover — in the sectors listed in the directive's annexes. Article 21 requires risk-management measures you can document.

Through your customers

Your customers are covered

Supply chain security is one of the mandatory Article 21 measures, so covered companies must assess their suppliers. Expect security questionnaires and contract clauses — even if you are too small to be in scope yourself.

General information, not legal advice. Whether and how NIS2 applies to you depends on your sector, your size and how your country implements the directive.

What It Covers

Article 21, Honestly.

The ten minimum measures in Article 21(2), and where CyberRiskGuru gives you evidence. The rest is policy and process work — yours, or your consultant's.

MeasureEvidenceWhat you get
(a)Risk analysis and information system security policiesCoveredA threat model per application: assets, attack surface, design weaknesses (MITRE CWE), attack methods (CAPEC) and your risk posture over time.
(b)Incident handlingPartlyIncidents logged against the attack vectors in your model. Your incident response procedure itself is yours to write.
(c)Business continuity, backup and crisis managementNot coveredPolicy and process work.
(d)Supply chain securityPartlyAn inventory of the third-party software in your stack, with versions, monitored for vulnerabilities. Assessing your suppliers is not covered.
(e)Security in acquisition, development and maintenance, including vulnerability handlingCoveredNightly matching against the exact versions you run, known-exploited (CISA KEV) first — each finding verified, mitigated or dismissed, with dates.
(f)Assessing the effectiveness of the measuresCoveredControls and their status, maturity level and residual risk tracked over time — a dated trail, not a one-off report.
(g)Basic cyber hygiene and trainingNot coveredThe in-app mentor videos help, but they are not training records.
(h)Cryptography and encryptionNot coveredPolicy work.
(i)HR security, access control and asset managementNot coveredYour model's asset and user-role profile supports this work, but is not an HR or access-control process.
(j)Multi-factor authentication and secured communicationsNot coveredPolicy and configuration work.
Evidence Over Time

A Record, Not A Snapshot.

Dated from day oneFindings, controls and your risk level are dated, so you can show what you knew and when you acted.
Version-preciseThe vulnerabilities that affect the software versions you actually run — not keyword noise.
Known-exploited firstVulnerabilities on CISA's known-exploited list lead the queue, because attackers are already using them.
Get Started

How Do You Want To Do It?

Pick what fits — it tells us how to help. Every option starts with a free account.

YOUR CHOICE:

A verification email is sent to this address

You already have an account? Log in here.