Incident to report to a regulator?Incident to report? Intake Line

NIS2 Italy vs SecNumCloud

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

NIS2 ItalyEssential and important entities

SecNumCloud

At a Glance

They differ on 33 of 33 topics. Each verdict names what it rests on; read the wording before relying on it.

  • NIS2 Italy Asks more on 33 topics Alone on 0 topics More detailed on 0 topics
  • SecNumCloud Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
Requirements per topic and verdict
Topic NIS2 ItalySecNumCloud Verdict
Governance
Management accountability NIS2 Italy: 2 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Roles and independence NIS2 Italy: 3 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Security policy NIS2 Italy: 4 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Awareness and training NIS2 Italy: 4 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Risk management
Risk management framework NIS2 Italy: 5 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Risk assessment NIS2 Italy: 4 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Review, audit and improvement NIS2 Italy: 5 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Asset management NIS2 Italy: 7 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Protection
Access control NIS2 Italy: 5 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Authentication NIS2 Italy: 3 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Cryptography and encryption NIS2 Italy: 2 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Data security NIS2 Italy: 1 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Network security NIS2 Italy: 3 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Secure communications NIS2 Italy: 2 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Secure acquisition and development NIS2 Italy: 2 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Configuration, change and patch management NIS2 Italy: 3 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Vulnerability handling NIS2 Italy: 4 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Human resources security NIS2 Italy: 3 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Physical and environmental security NIS2 Italy: 3 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Detection and response
Monitoring and detection NIS2 Italy: 3 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Incident handling NIS2 Italy: 3 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Incident classification NIS2 Italy: 4 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Reporting to authorities NIS2 Italy: 6 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Informing customers and the public NIS2 Italy: 3 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Threat intelligence and information sharing NIS2 Italy: 2 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Continuity and resilience
Business continuity and crisis management NIS2 Italy: 4 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Backup and recovery NIS2 Italy: 3 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Security testing NIS2 Italy: 2 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Third parties and supply chain
Supplier and third-party risk NIS2 Italy: 5 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Contract requirements NIS2 Italy: 1 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Register of third-party arrangements NIS2 Italy: 3 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Supervision and enforcement
Registration with authorities NIS2 Italy: 3 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive
Penalties and liability NIS2 Italy: 2 SecNumCloud: – NIS2 Italy asks morenational law departs from the Directive

What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

  • NIS2 Directive (EU) 2022/2555 Articles 3, 20, 21, 23, 27, 29, 34 · 31 requirements
  • NIS2 Implementing Regulation Commission Implementing Regulation (EU) 2024/2690 Articles 3 to 14 · Annex · 17 requirements Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

National requirements

  • IT-NIS2 Articles 7, 23, 25, 30, 38, 42
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 127434/2026
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025
  • ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) Determination 379907/2025

49 national requirements recorded, as departures from the Directive or additions to it. Everything else applies as the Directive has it.

Status

Reviewed against the official texts.

Included

  • SecNumCloud SecNumCloud requirements framework v3.2 (8 March 2022), approved by order of 12 August 2026; Law No. 2024-449 of 21 May 2024 (SREN), Article 31; Decree No. 2026-272 of 14 April 2026 5 requirements

Status

Reviewed against the official texts.

Key Numbers

Incident reports go to

NIS2 Italy: CSIRTComputer Security Incident Response Team Italia

SecNumCloud: Not in the acts covered

First notice of an incident

NIS2 Italy: Without undue delay and in any event within 24 hours of becoming aware

SecNumCloud: Not in the acts covered

Incident notification

NIS2 Italy: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust serviceAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2. providers, for incidents affecting their trust servicesAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2.)

SecNumCloud: Not in the acts covered

Intermediate report

NIS2 Italy: On request

SecNumCloud: Not in the acts covered

Final report

NIS2 Italy: Within one month of the incident notification; monthly progress reports while an incident is ongoing

SecNumCloud: Not in the acts covered

Deadline to have the measures in place

NIS2 Italy: Basic measures within 18 months, incident notification within 9 months of the inclusion notice

SecNumCloud: Not in the acts covered

Review of the risk framework

NIS2 Italy: Risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. and treatment plan at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers); Security policies at least yearly; risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. at least every two years

SecNumCloud: Not in the acts covered

Testing of critical systems

NIS2 Italy: VulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. assessments or penetration tests periodically and before go-live (essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities.)

SecNumCloud: Not in the acts covered

Register of third-party arrangements

NIS2 Italy: Directory of direct suppliers and service providers (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers); Inventory of suppliers, and of the ICTInformation and Communication Technology services they provide

SecNumCloud: Not in the acts covered

Registration with the authority

NIS2 Italy: Every year, 1 January to 28 February, plus a yearly update from 15 April to 31 May; changes within 14 days

SecNumCloud: Not in the acts covered

Management body training

NIS2 Italy: Required

SecNumCloud: Not in the acts covered

Management body liability

NIS2 Italy: Liable for breaches of the whole decree; can be barred from management functions (Article 38(6))

SecNumCloud: Not in the acts covered

Maximum fines

NIS2 Italy: Essential: up to EUR 10 million or 2% (minimum one twentieth of the maximum). Important: up to EUR 7 million or 1.4% (minimum one thirtieth). Registration and cooperation breaches: up to 0.1% or 0.07% of turnover. Public administrations: EUR 25,000 to 125,000.

SecNumCloud: Not in the acts covered

Governance

Management accountability

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4

  • Management approves, oversees and is liable Wider scope

    The management bodies approve how the risk-management measures are implemented, oversee the obligations of the chapter and registration, and are responsible for breaches of the decree.

    NIS2 Italy, Article 23(1)

  • Management informed of incidents Adds

    The management bodies are informed periodically, or promptly where appropriate, of incidents and notifications.

    NIS2 Italy, Article 23(3)

Nothing in the acts covered.

Roles and independence

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3

  • Roles, responsibilities and authorities

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Security roles assigned and communicated to the management bodies, at least one person reporting directly to them, conflicting duties segregated where applicable, and the assignment reviewed by the management bodies at planned intervals and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 1.2 · applies as in the Directive

  • Security organisation Adds

    The management bodies approve the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. organisation and its roles. Keep a list of the people with security roles, including the point of contact, the CSIRTComputer Security Incident Response Team contact and their substitutes. Review the roles at least every two years and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure GV.RR-02

  • Security roles of third-party staff Adds

    Define the security roles given to third-party staff and add them to the list of people with security roles.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure GV.SC-02

Nothing in the acts covered.

Security policy

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1

  • Risk analysis and security policies

    Policies on risk analysis and on information system security.

    NIS2, Article 21(2)(a) · applies as in the Directive

  • Network and information system security policy

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A security policy approved by the management body, reviewed at least annually and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 1.1 · applies as in the Directive

  • Security policies for 16 areas Adds

    Adopt documented security policies for at least 16 areas, from risk management and roles to monitoring and incident responseThe coordinated work an organisation carries out to deal with a cybersecurity incident and limit its consequences. An incident is an event that compromises, or threatens to compromise, the security of systems or information. Response can include investigating what happened, containing the problem, removing its cause and restoring affected services. It helps reduce damage and return operations to a controlled state., approved by the management bodies.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure GV.PO-01

  • Yearly policy review Adds

    Review the policies at least once a year, and after regulatory changes, significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes, checking that they comply with the law. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also keep a record of each review.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure GV.PO-02

Nothing in the acts covered.

Awareness and training

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3

  • Management body training

    Members of the management body follow training to identify risks and assess cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management practices. Entities are encouraged to offer similar training to employees regularly.

    NIS2, Article 20(2) · applies as in the Directive

  • Cyber hygiene and training

    Basic cyber hygiene practices and cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. training.

    NIS2, Article 21(2)(g) · applies as in the Directive

  • Training plan and register Adds

    A security training plan for staff and the management bodies, approved by the management bodies, with a register of who was trained.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.AT-01

  • Training for specialised roles Adds

    Applies to: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. only

    Dedicated training for staff in specialised roles, including system administrators.

    NIS2 Italy, ACN Determination 379907/2025, Annex 2, measure PR.AT-02

Nothing in the acts covered.

Risk management

Risk management framework

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1

  • Appropriate and proportionate measures

    Technical, operational and organisational measures to manage the risks to network and information systems, set by the state of the art, relevant standards, cost, the entity's exposure and size, and the likelihood and severity of incidents.

    NIS2, Article 21(1) · applies as in the Directive

  • All-hazards approach

    The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.

    NIS2, Article 21(2) · applies as in the Directive

  • Risk management framework

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 2.1 · applies as in the Directive

  • Phased deadlines Differs

    Entities have 18 months from the notice of inclusion in the NIS list to adopt the basic security measures, and 9 months to meet the incident notification duty. For entities first listed in 2026, the measures are due by 31 July 2027 and the notification duty applies from 1 January 2027.

    NIS2 Italy, Article 42(1)(c); ACN Determination 379907/2025, Article 3; ACN Determination 127434/2026, Article 1

  • Cybersecurity risk management plan Adds

    Define, apply, update and document a plan to identify, analyse, assess, treat and monitor cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risks, within the entity's risk management.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure GV.RM-03

Nothing in the acts covered.

Risk assessment

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2

  • Risk analysis and security policies

    Policies on risk analysis and on information system security.

    NIS2, Article 21(2)(a) · applies as in the Directive

  • Risk management framework

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 2.1 · applies as in the Directive

  • Risk assessment every two years Adds

    Carry out and document a risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change., including dependencies on suppliers, at least every two years and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes. The management bodies approve it.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure ID.RA-05

  • Risk treatment plan Adds

    A documented risk treatment plan with options, owners, timelines and reasons for accepting residual risksThe risk that remains after risk treatment has been applied. The NIST AI RMF notes that residual risk directly affects end users and affected communities, and asks system providers to document it so users understand the possible negative impacts., including compensating measures where a requirement is not met. The management bodies approve it.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure ID.RA-06

Nothing in the acts covered.

Review, audit and improvement

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10

  • Assessing effectiveness

    Policies and procedures to assess whether the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures work.

    NIS2, Article 21(2)(f) · applies as in the Directive

  • Corrective measures

    An entity that finds it does not comply with the measures takes the necessary corrective measures without undue delay.

    NIS2, Article 21(4) · applies as in the Directive

  • Independent review

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Independent reviews of network and information securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. at planned intervals and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 2.3 · applies as in the Directive

  • Yearly policy review Adds

    Review the policies at least once a year, and after regulatory changes, significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes, checking that they comply with the law. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also keep a record of each review.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure GV.PO-02

  • Improvement plan Adds

    An improvement plan following the policy review, approved by the management bodies, with periodic reports to them. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also keep a plan to assess the effectiveness of the measures.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure ID.IM-01

Nothing in the acts covered.

Asset management

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 ID.AM · ISO/IEC 27001:2022 A.5.9 to A.5.13

  • Asset management

    Asset managementAsset Management in Information Security.

    NIS2, Article 21(2)(i) · applies as in the Directive

  • Asset inventory

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A complete, accurate, up-to-date and consistent inventory of assets, with changes recorded in a traceable way.

    NIS2 Implementing Regulation, Annex, point 12.4 · applies as in the Directive

  • Yearly list of activities and services Adds

    Every year from 1 May to 30 June, list the entity's activities and services on the ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) platform, describe them and give each a relevance category under the ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) model. ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) answers within 90 days.

    NIS2 Italy, Article 30

  • List of relevant systems Adds

    Keep an up-to-date list of the relevant network and information systems.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure GV.OC-04

  • Hardware and software inventories Adds

    Keep up-to-date inventories of hardware (ITInformation Technology, IoTInternet of Things, OTOperational Technology and mobile) and of services, systems and software, including commercial, open-source and custom applications.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure ID.AM-01 and ID.AM-02

  • Inventory of network flows Adds

    Applies to: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. only

    Keep an up-to-date inventory of the network flows between the entity's systems and the outside.

    NIS2 Italy, ACN Determination 379907/2025, Annex 2, measure ID.AM-03

  • Inventory of supplier services Adds

    Keep an up-to-date inventory of the ICTInformation and Communication Technology services provided by suppliers, including cloud services.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure ID.AM-04

Nothing in the acts covered.

Protection

Access control

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3

  • Access control policies

    Access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. policies.

    NIS2, Article 21(2)(i) · applies as in the Directive

  • Access rights and privileged accounts

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Management of access rights, and stricter controls on privileged and system administration accounts.

    NIS2 Implementing Regulation, Annex, points 11.2 and 11.3 · applies as in the Directive

  • Accounts and credentials Adds

    Record and approve every account, including administrator and remote accounts, and keep them individual unless there are documented technical reasons. Use strong credentials, and review accounts and permissions on relevant systems periodically.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.AA-01

  • Least privilege Adds

    Grant permissions on least privilegeThe principle that a security architecture gives each user, process or other entity only the system authorisations and resources it needs to perform its function. It limits the damage a compromised account or component can do., separation of duties and need to know, with separate administrator accounts and credentials.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.AA-05

  • Remote access and perimeter Adds

    For relevant systems, define the allowed remote activities and secure remote access. Keep a list of all remotely accessible systems, and maintain perimeter systems such as firewalls.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.IR-01

Nothing in the acts covered.

Authentication

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5

  • Multi-factor authentication

    Multi-factor or continuous authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. solutions, where appropriate.

    NIS2, Article 21(2)(j) · applies as in the Directive

  • Multi-factor authentication

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Multi-factor or continuous authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. where appropriate, in line with the classification of the asset accessed.

    NIS2 Implementing Regulation, Annex, point 11.7 · applies as in the Directive

  • Multi-factor authentication Adds

    AuthenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. matched to risk, and multi-factor authenticationAuthentication through verification of at least two different types of factor: something a person knows, such as a password; something they have, such as a token; or something they are, such as a biometric. NIS2, PCI DSS, the NYDFS regulation and the FTC Safeguards Rule call for it. for at least the relevant systems, in line with the risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.AA-03

Nothing in the acts covered.

Cryptography and encryption

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24

  • Cryptography

    Policies and procedures on the use of cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. and, where appropriate, encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it..

    NIS2, Article 21(2)(h) · applies as in the Directive

  • Encryption at rest and in transit Adds

    Encrypt data on laptops, phones, tablets and removable media, disable autorun and scan removable media, and encrypt data sent outside the entity, including voice, video and text, in line with the risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.DS-01 and PR.DS-02

Nothing in the acts covered.

Data security

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

  • Encryption at rest and in transit Adds

    Encrypt data on laptops, phones, tablets and removable media, disable autorun and scan removable media, and encrypt data sent outside the entity, including voice, video and text, in line with the risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.DS-01 and PR.DS-02

Nothing in the acts covered.

Network security

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22

  • Network security and segmentation

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Network security measures, and systems segmented into networks or zones by risk and from third parties' systems.

    NIS2 Implementing Regulation, Annex, points 6.7 and 6.8 · applies as in the Directive

  • Inventory of network flows Adds

    Applies to: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. only

    Keep an up-to-date inventory of the network flows between the entity's systems and the outside.

    NIS2 Italy, ACN Determination 379907/2025, Annex 2, measure ID.AM-03

  • Remote access and perimeter Adds

    For relevant systems, define the allowed remote activities and secure remote access. Keep a list of all remotely accessible systems, and maintain perimeter systems such as firewalls.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.IR-01

Nothing in the acts covered.

Secure communications

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.14

  • Secured communications

    Secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate.

    NIS2, Article 21(2)(j) · applies as in the Directive

  • Protected emergency communications Adds

    Applies to: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. only

    Use protected emergency communication systems, in line with the risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..

    NIS2 Italy, ACN Determination 379907/2025, Annex 2, measure PR.IR-03

Nothing in the acts covered.

Secure acquisition and development

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.25 to A.8.31

  • Secure acquisition, development and maintenance

    Security in the acquisition, development and maintenance of network and information systems, including vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. handling and disclosure.

    NIS2, Article 21(2)(e) · applies as in the Directive

  • Secure development Adds

    Adopt documented secure coding practices.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.PS-06

Nothing in the acts covered.

Configuration, change and patch management

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.9, A.8.19, A.8.32

  • Configuration, change and patch management

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Secure configurations, controlled changes, repairs and maintenance, and security patches applied within a reasonable time after release, unless the disadvantages outweigh the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. benefits and the reasons are documented.

    NIS2 Implementing Regulation, Annex, points 6.3, 6.4 and 6.6 · applies as in the Directive

  • Hardened configurations and hardware Adds

    Applies to: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. only

    Documented hardened reference configurations for relevant systems, secure disposal of storage devices and a hardware maintenance log.

    NIS2 Italy, ACN Determination 379907/2025, Annex 2, measure PR.PS-01 and PR.PS-03

  • Supported software and patching Adds

    Install only software that still receives security updates, and apply the latest security updates without undue delay. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also test updates to critical software before use.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.PS-02

Nothing in the acts covered.

Vulnerability handling

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8

  • Secure acquisition, development and maintenance

    Security in the acquisition, development and maintenance of network and information systems, including vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. handling and disclosure.

    NIS2, Article 21(2)(e) · applies as in the Directive

  • Find vulnerabilities Adds

    Use vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. information to identify vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition.. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also run vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. assessments or penetration tests on relevant systems periodically and before they go live, and document the results.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure ID.RA-01

  • Vulnerability management plan Adds

    Monitor CSIRTComputer Security Incident Response Team Italia, sector CERTsComputer Emergency Response Team and ISACs for vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. information, fix vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. promptly or accept the risk in the treatment plan, and keep a vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. management plan approved by the management bodies. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also monitor the channels of suppliers of critical software.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure ID.RA-08

  • Supported software and patching Adds

    Install only software that still receives security updates, and apply the latest security updates without undue delay. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also test updates to critical software before use.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.PS-02

Nothing in the acts covered.

Human resources security

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6

  • Human resources security

    Human resources security.

    NIS2, Article 21(2)(i) · applies as in the Directive

  • Background verification

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Background checks on employees, and where applicable on direct suppliers and service providers, to the extent feasible and where the role needs it.

    NIS2 Implementing Regulation, Annex, point 10.2 · applies as in the Directive

  • Trusted staff and administrators Adds

    Staff with access to relevant systems, and system administrators, are chosen after assessing their experience, ability and reliability. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also set in contracts the security duties that continue after employment ends or changes.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure GV.RR-04

Nothing in the acts covered.

Physical and environmental security

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14

  • All-hazards approach

    The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.

    NIS2, Article 21(2) · applies as in the Directive

  • Physical and environmental security

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Supporting utilities, protection against physical and environmental threats, and perimeter and physical access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements..

    NIS2 Implementing Regulation, Annex, points 13.1 to 13.3 · applies as in the Directive

  • Physical access Adds

    Protect physical access to at least the relevant systems.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.AA-06

Nothing in the acts covered.

Detection and response

Monitoring and detection

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16

  • Monitoring and logging

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Monitoring and logging of network and information systems to detect events that could be incidents.

    NIS2 Implementing Regulation, Annex, point 3.2 · applies as in the Directive

  • Logging Adds

    Log all remote and administrator access, collect and keep security logs for relevant systems securely, and set retention periods.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.PS-04

  • Detection and endpoint protection Adds

    Tools to detect significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. on relevant systems, defined expected service levels, and endpoint protection against malicious code. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also filter inbound traffic including email, and monitor remote access, perimeter and administrative events and access attempts.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure DE.CM-01 and DE.CM-09

Nothing in the acts covered.

Incident handling

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28

  • Incident handling

    Procedures to handle incidents.

    NIS2, Article 21(2)(b) · applies as in the Directive

  • Incident management and notification plan Adds

    A plan for handling incidents and notifying CSIRTComputer Security Incident Response Team Italia, with roles, reporting procedures, contacts and communication, approved by the management bodies and reviewed at least every two years.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure RS.MA-01

  • Communicating recovery Adds

    Applies to: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. only

    Procedures to tell internal parties about recovery activities after an incident.

    NIS2 Italy, ACN Determination 379907/2025, Annex 2, measure RC.CO-03

Nothing in the acts covered.

Incident classification

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 RS.MA · ISO/IEC 27001:2022 A.5.25

  • When an incident is significant

    An incident is significant when it has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to others.

    NIS2, Article 23(3) · applies as in the Directive

  • Event assessment and classification

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Suspicious events are assessed to decide whether they are incidents and, if so, their nature and severity. Recurring incidents under Article 4 are checked quarterly.

    NIS2 Implementing Regulation, Annex, point 3.4 · applies as in the Directive

  • When an incident is significant

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Criteria that make an incident significant: general criteria for all these providers (Article 3), recurring incidents (Article 4) and criteria for each kind of provider (Articles 5 to 14).

    NIS2 Implementing Regulation, Articles 3 to 14 · applies as in the Directive

  • Basic significant incidents Adds

    An incident is significant at least when there is evidence of: loss of confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. of the entity's data to the outside (IS-1); loss of integrity with external impact (IS-2); a breach of the expected service levels set under DE.CM-01 (IS-3). Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also: unauthorised or privilege-abusing access to their data (IS-4).

    NIS2 Italy, ACN Determination 379907/2025, Annexes 3 and 4

Nothing in the acts covered.

Reporting to authorities

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

  • Notify CSIRT Italia Differs

    Notify significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. without undue delay to CSIRTComputer Security Incident Response Team Italia, with the information needed to judge any cross-border impact.

    NIS2 Italy, Article 25(1)

  • Early warning

    An early warning, saying where applicable whether the incident is suspected to be caused by unlawful or malicious acts or could have a cross-border impact.

    NIS2, Article 23(4)(a) · applies as in the Directive

  • Incident notification

    An incident notification updating the early warning with an initial assessment of severity and impact and, where available, indicators of compromise.

    NIS2, Article 23(4)(b) · applies as in the Directive

  • Intermediate report

    An intermediate report on status updates, when the CSIRTComputer Security Incident Response Team or authority asks for one.

    NIS2, Article 23(4)(c) · applies as in the Directive

  • Monthly progress reports Stricter

    A final report within one month of the incident notification. If the incident is still ongoing, a progress report every month and a final report within one month of closing it.

    NIS2 Italy, Article 25(5)(d) and (e)

  • Incident management and notification plan Adds

    A plan for handling incidents and notifying CSIRTComputer Security Incident Response Team Italia, with roles, reporting procedures, contacts and communication, approved by the management bodies and reviewed at least every two years.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure RS.MA-01

Nothing in the acts covered.

Informing customers and the public

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 RS.CO, RC.CO

  • Inform recipients after consulting CSIRT Italia Differs

    Where appropriate and possible, and after consulting CSIRTComputer Security Incident Response Team Italia, tell recipients of the services about significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. that may affect them. In the same way, tell recipients affected by a significant cyber threatA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident. what measures they can take and the nature of the threat.

    NIS2 Italy, Article 25(9) and (10)

  • Warn of significant cyber threats

    Where applicable, tell recipients potentially affected by a significant cyber threatA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident., without undue delay, what they can do about it and, where appropriate, about the threat itself.

    NIS2, Article 23(2) · applies as in the Directive

  • Procedures to inform recipients and the public Adds

    Documented procedures to inform recipients of significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. and threats, after consulting CSIRTComputer Security Incident Response Team Italia or when ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) orders it, and to inform the public when ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) orders it.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure RS.CO-02

Nothing in the acts covered.

Threat intelligence and information sharing

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.5.6, A.5.7

  • Information-sharing arrangements Optional

    Entities may exchange cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. information such as threats, vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and indicators of compromise within information-sharing arrangements. Essential and important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance. notify the competent authority when they join or withdraw.

    NIS2, Article 29 · applies as in the Directive

  • Vulnerability management plan Adds

    Monitor CSIRTComputer Security Incident Response Team Italia, sector CERTsComputer Emergency Response Team and ISACs for vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. information, fix vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. promptly or accept the risk in the treatment plan, and keep a vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. management plan approved by the management bodies. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also monitor the channels of suppliers of critical software.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure ID.RA-08

Nothing in the acts covered.

Continuity and resilience

Business continuity and crisis management

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 RC.RP, RC.CO · ISO/IEC 27001:2022 A.5.29, A.5.30

  • Business continuity and crisis management

    Business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice., such as backupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. management and disaster recoveryThe organised work of restoring IT systems and recovering information after a serious disruption, so the organisation can resume operations. It includes deciding which systems matter most, preparing backups and recovery resources, assigning responsibilities, and testing the recovery procedures. A disaster recovery environment is the technical set-up used for this restoration. A disaster recovery plan records how the work will be carried out., and crisis management.

    NIS2, Article 21(2)(c) · applies as in the Directive

  • Continuity, recovery and crisis plans Adds

    Business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice., disaster recoveryThe organised work of restoring IT systems and recovering information after a serious disruption, so the organisation can resume operations. It includes deciding which systems matter most, preparing backups and recovery resources, assigning responsibilities, and testing the recovery procedures. A disaster recovery environment is the technical set-up used for this restoration. A disaster recovery plan records how the work will be carried out. and cyber crisis management plans for relevant systems, approved by the management bodies and reviewed at least every two years.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure ID.IM-04

  • Protected emergency communications Adds

    Applies to: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. only

    Use protected emergency communication systems, in line with the risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..

    NIS2 Italy, ACN Determination 379907/2025, Annex 2, measure PR.IR-03

  • Recovery procedures Adds

    Procedures to restore normal operation of systems affected by incidents.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure RC.RP-01

Nothing in the acts covered.

Backup and recovery

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 PR.DS, RC.RP · ISO/IEC 27001:2022 A.8.13, A.8.14

  • Business continuity and crisis management

    Business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice., such as backupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. management and disaster recoveryThe organised work of restoring IT systems and recovering information after a serious disruption, so the organisation can resume operations. It includes deciding which systems matter most, preparing backups and recovery resources, assigning responsibilities, and testing the recovery procedures. A disaster recovery environment is the technical set-up used for this restoration. A disaster recovery plan records how the work will be carried out., and crisis management.

    NIS2, Article 21(2)(c) · applies as in the Directive

  • Backup and redundancy

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    BackupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. copies and sufficient redundancy, with regular integrity checks on the copies and regular testing of recovery of copies and redundancies.

    NIS2 Implementing Regulation, Annex, point 4.2 · applies as in the Directive

  • Backups, with offline copies Adds

    Regular backupsBackup of data and configurations, with offline copies for relevant systems. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also protect backupsBackup physically or by encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it., and test restores periodically.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure PR.DS-11

Nothing in the acts covered.

Security testing

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34

  • Security testing

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A policy and procedures for security testing of network and information systems.

    NIS2 Implementing Regulation, Annex, point 6.5 · applies as in the Directive

  • Find vulnerabilities Adds

    Use vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. information to identify vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition.. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. also run vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. assessments or penetration tests on relevant systems periodically and before they go live, and document the results.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure ID.RA-01

Nothing in the acts covered.

Third parties and supply chain

Supplier and third-party risk

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23

  • Supply chain security

    Supply chain security, including the security aspects of the relationship with each direct supplier and service provider.

    NIS2, Article 21(2)(d) · applies as in the Directive

  • What to weigh for each supplier and service provider

    Entities weigh the specific vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. of each direct supplier and service provider, the quality of their products and cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. practices, including secure development, and the results of EU coordinated risk assessmentsRisk Assessment of critical supply chains.

    NIS2, Article 21(3) · applies as in the Directive

  • Security in procurement Adds

    The security organisation takes part in procurement from the design of the purchase. Security requirements for each purchase follow its risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change.. Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. cover at least 17 areas in those requirements, from supplier reliability to subcontracting and the return and deletion of data.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure GV.SC-01

  • Security roles of third-party staff Adds

    Define the security roles given to third-party staff and add them to the list of people with security roles.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure GV.SC-02

  • Supplier risk assessment Adds

    Assess and document the risk of each supply: the supplier's access to systems and data, the impact of a disruption, recovery time and cost, and the supplier's role. Check compliance with the contract requirements periodically.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure GV.SC-07

Nothing in the acts covered.

Contract requirements

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.20

Nothing in the acts covered.

Register of third-party arrangements

NIS2 Italy asks more national law departs from the Directive

NIST CSF 2.0 GV.SC

  • Directory of suppliers

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A directory of direct suppliers and service providers, kept up to date.

    NIS2 Implementing Regulation, Annex, point 5.2 · applies as in the Directive

  • Inventory of suppliers Adds

    Keep an up-to-date inventory of suppliers whose supplies can affect the security of the systems, with a contact and the type of supply.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure GV.SC-04

  • Inventory of supplier services Adds

    Keep an up-to-date inventory of the ICTInformation and Communication Technology services provided by suppliers, including cloud services.

    NIS2 Italy, ACN Determination 379907/2025, Annexes 1 and 2, measure ID.AM-04

Nothing in the acts covered.

Supervision and enforcement

Registration with authorities

NIS2 Italy asks more national law departs from the Directive

  • Register and update every year Stricter

    Register or update the registration on the ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) platform every year from 1 January to 28 February, naming a point of contact. Entities on the list then add, from 15 April to 31 May, their public IP addressInternet Protocol Address space and domain names, the persons responsible under Article 38(5) and a substitute contact. Changes are reported within 14 days.

    NIS2 Italy, Article 7

  • Registry of digital providers

    DNSDomain Name System, TLDTop-Level Domain, domain name registration, cloud, data centre, content delivery, managed (security) service providers, marketplaces, search engines and social networks submit their details to the competent authority by 17 January 2025 for the ENISAEuropean Union Agency for Cybersecurity registry, and report changes without delay and within three months. The authority is that of their main establishment or EU representative (Article 26).

    NIS2, Article 27 · applies as in the Directive

  • Yearly list of activities and services Adds

    Every year from 1 May to 30 June, list the entity's activities and services on the ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) platform, describe them and give each a relevance category under the ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) model. ACNAgenzia per la Cybersicurezza Nazionale (National Cybersecurity Agency) answers within 90 days.

    NIS2 Italy, Article 30

Nothing in the acts covered.

Penalties and liability

NIS2 Italy asks more national law departs from the Directive

  • Management approves, oversees and is liable Wider scope

    The management bodies approve how the risk-management measures are implemented, oversee the obligations of the chapter and registration, and are responsible for breaches of the decree.

    NIS2 Italy, Article 23(1)

  • Fines with minimums Stricter

    Breaches of Articles 23 to 25 are fined with a minimum as well as a maximum: one twentieth of the maximum for essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. and one thirtieth for important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance.. Registration, categorisation and cooperation breaches have lower caps, of 0.1% and 0.07% of turnover. Public administrations face set ranges, such as €25,000 to €125,000 for essential ones. Repeating the same breach can double the fine; other repeat breaches can triple it.

    NIS2 Italy, Article 38(9) to (12)

Nothing in the acts covered.

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.

Subject to more than one?

We run one control set for both, without doing the work twice. Ask what that saves you.

Loading the form…