The NIS 2 Directive (Directive (EU) 2022/2555) does not hand you a neat list of mandatory documents. It sets out duties: manage cyber risk, report incidents, and make senior management accountable. Regulators and auditors will expect written evidence that you do these things.
This article turns those duties into a working document set. Use it to plan your documentation, spot gaps and avoid writing more than you need.
Start with the principle: document to prove, not to impress#
NIS 2 is a directive, so each EU member state transposes it into national law. Details such as supervisory bodies, deadlines and sector rules vary. Check the requirements of the country (or countries) where you operate. Some digital infrastructure and ICT service entities are also subject to a separate EU implementing regulation with more detailed technical requirements.
Across all of these, the logic is the same. You need three layers of documents:
- Governance documents: who is accountable, what is in scope, what the rules are.
- Procedures and controls: how each security measure is carried out in practice.
- Records and evidence: proof that the procedures actually run, such as logs, test results, training records and approvals.
Governance and scope documents#
NIS 2 places responsibility on management bodies. They must approve cybersecurity risk-management measures, oversee their implementation and undergo training. That needs a paper trail.
- Applicability and scope statement: why you are an essential or important entity, which services and systems are in scope, and which national authority you answer to.
- Cybersecurity policy: a top-level policy approved by management, setting objectives and commitments.
- Roles and responsibilities matrix: who owns security, who reports incidents, who deputises.
- Management approval and oversight records: minutes, sign-offs and review reports showing that leadership has actually reviewed risk and measures.
- Management training records: evidence that board members and senior managers have received cybersecurity training.
Documents that map to the Article 21 risk-management measures#
Article 21 requires "appropriate and proportionate" technical, operational and organisational measures, based on an all-hazards approach. It lists minimum areas. The table maps each to the documents you would normally expect.
| Measure area | Typical documents |
|---|---|
| Risk analysis and information system security policies | Risk management policy, risk assessment methodology, risk register, risk treatment plan |
| Incident handling | Incident management policy and procedure, severity criteria, incident log, post-incident review template |
| Business continuity, backup, disaster recovery, crisis management | Business continuity plan, disaster recovery plan, backup procedure, crisis communication plan, test records |
| Supply chain security | Supplier security policy, supplier risk assessment, security clauses for contracts, supplier register |
| Security in acquisition, development and maintenance, including vulnerability handling | Secure development and change management procedure, vulnerability and patch management procedure, vulnerability disclosure process |
| Assessing the effectiveness of measures | Internal audit procedure, audit plan and reports, metrics and review records, corrective action log |
| Cyber hygiene and training | Security awareness programme, training plan, attendance and completion records |
| Cryptography and encryption | Cryptography policy, key management procedure |
| HR security, access control, asset management | HR security procedure, access control policy, joiner-mover-leaver process, asset inventory, asset classification rules |
| Multi-factor authentication and secured communications | Authentication standard, secure communications and remote access rules, emergency communication arrangements |
You do not need ten thick manuals. Small organisations can often combine related topics into one policy, provided each area is clearly covered and someone owns it.
Incident reporting documents#
Reporting is where documentation gaps hurt most, because the deadlines are short. Under Article 23, significant incidents trigger a staged process: an early warning within 24 hours of becoming aware, an incident notification within 72 hours, and a final report within one month of the notification. Confirm the exact format and channel with your national authority or CSIRT.
To meet this, prepare:
- Significant incident criteria: a clear definition of when an incident becomes reportable, so the decision is not improvised at 2 a.m.
- Reporting procedure: who decides, who files, which authority, which channel and what the backup is if the primary contact is unavailable.
- Report templates: pre-built forms for the early warning, the 72-hour notification and the final report.
- Escalation and contact list: internal decision-makers, legal, communications, and external contacts such as the national authority and key suppliers.
- Incident records: timeline, actions taken, decisions and evidence, kept consistently.
- Customer and recipient notification guidance: where services are affected, how and when you inform them.
Run a tabletop exercise and keep the output. A tested procedure is far more convincing than a polished but untested one.
Records that show the system is alive#
Policies alone will not satisfy a supervisor. Plan to keep evidence such as:
- Completed risk assessments with dates and approvers
- Backup and restore test results
- Patch and vulnerability scan reports with remediation status
- Access review records
- Supplier assessments and signed contract clauses
- Internal audit reports and management review minutes
- Training attendance and completion records
- A gap assessment showing where you stand against the requirements and what you plan to fix
A gap assessment is a good first document. It tells you which of the above already exist, which are weak and which are missing, so you write only what you need.
A sensible order of work#
- Confirm scope and national requirements.
- Run a gap assessment against Article 21 and your national rules.
- Write or update the governance documents and get management approval.
- Complete the risk assessment, then prioritise policies and procedures by risk.
- Build the incident reporting procedure and test it early.
- Start collecting records from day one, so evidence builds up as you implement.
- Review, audit internally and report to management.
If you already run an ISO/IEC 27001 management system, reuse it. Many policies, risk processes and audit records will carry over, though you still need to check them against NIS 2 requirements such as management accountability, supply chain security and reporting deadlines.
Frequently asked questions#
Does NIS 2 require specific named documents?#
Not as a fixed list. The Directive requires measures and outcomes, and national law or implementing rules may add detail. In practice you need documents that describe your measures and records that prove they operate.
Is ISO 27001 certification enough to comply with NIS 2?#
Not automatically. ISO 27001 gives a strong foundation, and much of the documentation overlaps. NIS 2 also has legal duties, including incident reporting to authorities and management accountability, so a gap check against the Directive is still needed.
Can a small organisation keep its documentation light?#
Yes. The measures must be proportionate to your size, risk exposure and the impact of incidents. Shorter, combined documents are acceptable if every required area is covered, owned and evidenced.
If you would rather not start from a blank page, the NIS 2 Toolkit offers editable policies, procedures, checklists, worked examples and a gap assessment checklist that you can adapt to your organisation and national requirements.
