Skip to main content
All news

Risk Management ·

NIS2: the technical measures of Art. 21 — the CISO's checklist

Art. 21 of Legislative Decree 138/2024 (D.Lgs. 138/2024, Italy's transposition of the NIS2 Directive) sets out the minimum technical and organisational measures that every NIS2 entity must adopt to manage the security risks of its information systems. This practical checklist, designed for the CISO and for those responsible for implementation, turns the 10 families of measures in Art. 21 into concrete evidence: what is needed, where to document it and how to demonstrate it during an ACN (National Cybersecurity Agency) inspection.

By Fabio Vantaggiato, CEO & Co-Founder

The principle: measures proportionate to risk, evidence mandatory

Art. 21 introduces a key principle: measures must be proportionate to the organisation's level of risk, taking into account its size, the criticality of the services it provides, the threats specific to its sector and the state of the art. There is no "closed list" of products or configurations: there is an expected security outcome, to be achieved with the technologies and processes best suited to the context.

What does not vary, however, is the requirement for evidence. For each family of measures there must be documentation that can be reconstructed: an approved policy, an executed process, a retained log, a periodic report. In the event of an inspection, substantive compliance without documentary evidence amounts to non-compliance.

The Art. 21 checklist: 10 families of measures, evidence by evidence

1. Risk analysis and information system security policies

What is needed: a formalised risk assessment methodology (ISO/IEC 27005, NIST SP 800-30 or equivalent), a risk register updated at least annually, and an Information Security Policy approved by the management body.

Evidence: methodology document, dated and versioned risk register, minutes of the policy's approval.

2. Incident handling

What is needed: an incident response procedure (detection, classification, containment, eradication, recovery, lessons learned), runbooks for the most likely types of incident, and integration with the Art. 25 notification procedure.

Evidence: formalised procedure, logs of any incidents handled with a timeline of actions, periodic exercises (tabletop or full-scale).

3. Business continuity: backup, disaster recovery, crisis management

What is needed: a Business Impact Analysis (BIA), a Business Continuity Plan (BCP), a Disaster Recovery Plan (DRP) with RPO and RTO defined for critical processes, and a crisis management plan for worst-case scenarios.

Evidence: up-to-date BIA, BCP/DRP tested at least annually, records of the tests and their results, backup logs periodically verified for recoverability.

4. Supply chain security

What is needed: mapping of critical suppliers, a vendor risk assessment process, contractual security clauses (including SLAs on incident response and the right to audit), and continuous monitoring of critical suppliers' security posture.

Evidence: supplier register, completed due diligence questionnaires, contracts with NIS2-compliant clauses, any supplier certifications (ISO/IEC 27001, SOC 2 Type II).

5. Security in the acquisition, development and maintenance of systems

What is needed: a Secure SDLC with security gates (threat modelling, SAST, DAST, SCA), vulnerability handling (vulnerability management and patch management with SLAs by severity), and a responsible disclosure process.

Evidence: SDLC policy, SAST/DAST/SCA reports for each release, vulnerability dashboard with MTTR metrics by severity, register of applied patches.

6. Policies for assessing the effectiveness of measures

What is needed: a periodic internal audit programme, annual vulnerability assessments and penetration tests (more frequent for the most critical systems), and red teaming for advanced scenarios.

Evidence: annual audit plan, VA/PT reports with an associated remediation plan, evidence of closed remediations.

7. Basic cyber hygiene and training

What is needed: a tiered NIS2 training plan (management, CISO, IT, operational staff), ongoing security awareness, and periodic phishing simulations.

Evidence: annual training plan, register of hours delivered for each profile, certificates of attendance, phishing simulation reports with click rate and reporting rate metrics.

8. Cryptography policies

What is needed: a cryptography policy defining permitted and prohibited algorithms (in line with ENISA and NIST guidelines), a Key Management System to manage the key lifecycle, and encryption at rest and in transit for critical data.

Evidence: approved policy, key register, compliant TLS/SSL configurations, any documented HSMs or cloud key management services.

9. Human resources security, access control and asset management

What is needed: onboarding/offboarding processes with prompt revocation of access, the principle of least privilege, IAM and PAM for privileged access, and an up-to-date, classified asset inventory.

Evidence: integrated HR-IT procedures, retained logs of privileged access, asset inventory with owners and classification, periodic access reviews.

10. Multi-factor authentication and secured communications

What is needed: mandatory MFA for privileged access, remote access and critical applications; secured communication channels for incident handling and emergency communications.

Evidence: MFA policy, IdP configurations, logs of MFA-protected access, a tested emergency communication plan.

Turning the checklist into a roadmap

A checklist is not a plan. Turning it into a concrete compliance roadmap takes three steps: gap analysis (what the current state is for each family of measures), residual risk scoring (which gaps expose the organisation to unacceptable risk) and prioritisation (which actions must be taken immediately, which within 6-12 months and which later).

A CISO who can take the roadmap to the Board along these three dimensions — status, risk, priority — secures budget approval and political backing for the work. This is exactly the collaboration between the management body and technical management that Art. 20 requires.

Related resources

For the complete regulatory framework: NIS2: the complete guide to Legislative Decree 138/2024. For the incident notification procedure: NIS2 incident notification: the 24h / 72h / 1-month procedure. For supplier risk management: NIS2 and the supply chain. For the penalty regime: NIS2 penalties under Art. 38. For CISO training: NIS2 Course for CISOs.

Related articles

Would you like to find out more?

Get in touch to find out how our solutions can support your healthcare organisation.

Talk to an expert

Talk to us

Tell us how care is organised in your area: we'll prepare a demo on your own pathways, not on a textbook case.

NIS2: the technical measures of Art. 21 — the CISO's checklist | Easy Health