CyFun® 2025 Measures
Every measure of the CyFun® 2025 framework, plus every CyFun® 2023 measure removed in 2025
Reviewed September 2026
How to read this. The level pill is the assurance level at which a measure first applies: a BASIC measure
also applies at IMPORTANT and ESSENTIAL, and an IMPORTANT measure also applies at ESSENTIAL. Requirement texts are the
CCB's own, quoted verbatim from the templates. "from …" under an identifier is the CyFun 2023 measure it comes
from, using the mapping published by the CCB.
The requirement shown is the text of the current template, taken at the level where the measure first applies. "description changed since 2025-10-21" means the CCB reworded it in the February 2026 release at one or more levels; the wording of a measure can differ between levels, which is why that table on the descriptions page lists 28 rows for these 20 measures.
The requirement shown is the text of the current template, taken at the level where the measure first applies. "description changed since 2025-10-21" means the CCB reworded it in the February 2026 release at one or more levels; the wording of a measure can differ between levels, which is why that table on the descriptions page lists 28 rows for these 20 measures.
| Level | Function / category | Measure | Requirement |
|---|---|---|---|
| IMPORTANT | GOVERN Organisational Context (GV.OC) | GV.OC-01.1 from ID.BE-2.1 | The organisation's mission shall be established, communicated and shall form the basis for information and cybersecurity risk management. |
| ESSENTIAL | GOVERN | GV.OC-02.1 | The organisation shall demonstrate it understands and considers the needs and expectations of both internal and external stakeholders regarding information and cybersecurity risk management. |
| BASIC | GOVERN Organisational Context (GV.OC) | GV.OC-03.1 from ID.GV-3.1 | Legal and regulatory requirements regarding information and cybersecurity shall be identified and implemented. |
| IMPORTANT | GOVERN | GV.OC-03.2 from ID.GV-3.2 | Legal and regulatory obligations related to information and cybersecurity shall be continuously managed to ensure they remain accurate, up to date, and effectively applied. |
| IMPORTANT | GOVERN | GV.OC-04.1 from ID.BE-4.1 | The organisation shall identify, document, and communicate the critical objectives, capabilities, and services relied upon by external stakeholders, prioritise them based on criticality, and integrate this prioritisation into the risk assessment process. |
| IMPORTANT | GOVERN | GV.OC-04.2 from ID.BE-5.1 | The organisation shall define and document cybersecurity requirements for essential operations, validate them through testing and audits, keep records of results and corrective actions, and regularly update requirements based on evolving risks. |
| ESSENTIAL | GOVERN | GV.OC-04.3 from ID.BE-5.2 | Redundancy shall be implemented to meet availability requirements as defined by the organisation, legislation and/or regulations. |
| ESSENTIAL | GOVERN | GV.OC-04.4 from ID.BE-5.3 | Recovery time and recovery point objectives for the resumption of essential ICT/OT system processes shall be defined and monitored. |
| IMPORTANT | GOVERN | GV.OC-05.1 from ID.BE-1.1 | The organisation shall identify, document, and communicate its role in the supply chain, including the external capabilities, services, and dependencies it relies on (upstream), as well as its interactions with downstream stakeholders.. |
| ESSENTIAL | GOVERN Oversight (GV.OV) | GV.OV-02.1 | The information and cybersecurity risk management strategy shall be reviewed and adjusted to ensure coverage of organisational requirements and risks. |
| ESSENTIAL | GOVERN | GV.OV-03.1 | The organisation's cybersecurity risk management performance shall be evaluated, reviewed and adjusted when necessary. |
| BASIC | GOVERN Policy (GV.PO) | GV.PO-01.1 from ID.GV-1.1 | Policies and procedures for managing information and cybersecurity shall be established, documented, reviewed, approved, updated when changes occur, communicated and enforced. |
| IMPORTANT | GOVERN | GV.PO-01.2 from ID.GV-1.2 | Organisational-wide information and cybersecurity policies and procedures shall include the use of cryptography and, where appropriate, encryption, reflect changes in requirements, threats, technology and organisational roles, and be approved by senior management, who oversee implementation. |
| IMPORTANT | GOVERN Risk Management Strategy (GV.RM) | GV.RM-01.1 from ID.RM-1.1 | Information and cybersecurity objectives shall be coherently established throughout the organisation and approved by senior management. |
| IMPORTANT | GOVERN | GV.RM-02.1 from ID.RM-2.1 | Risk appetite and risk tolerance statements shall be defined, documented, approved by senior management, communicated, and maintained. |
| BASIC | GOVERN Risk Management Strategy (GV.RM) | GV.RM-03.1 from ID.GV-4.1 | As part of the organisation-wide risk management strategy, a comprehensive strategy to manage information and cybersecurity risks shall be developed and updated when changes occur. |
| IMPORTANT | GOVERN | GV.RM-03.2 from ID.GV-4.2 | Information and cybersecurity risks shall be documented, as part of the enterprise risk management processes, formally approved by senior management, and updated when changes occur. |
| IMPORTANT | GOVERN | GV.RM-04.1 | A high-level plan or vision shall be formally established and clearly communicated to everyone involved on how to manage risks, including the different strategies the organisation can employ to deal with identified risks based on risk appetite or risk tolerance level. |
| IMPORTANT | GOVERN | GV.RM-05.1 | To support the high-level risk management vision, the organisation shall establish clear lines of communication for cybersecurity risks, including those arising from suppliers and third parties. |
| ESSENTIAL | GOVERN Roles, Responsibilities and Authorities (GV.RR) | GV.RR-01.1 | The organisation's top management shall be responsible and accountable for cybersecurity risk and shall foster a culture that is risk-aware, ethical, and continually improving. |
| IMPORTANT | GOVERN Roles, Responsibilities and Authorities (GV.RR) | GV.RR-02.1 from ID.AM-6.1 | Information security and cyber security roles, responsibilities and authorities for employees, suppliers, customers, and partners shall be documented, reviewed, authorised, kept up-to-date, communicated, and coordinated internally and externally. |
| ESSENTIAL | GOVERN | GV.RR-02.2 from ID.AM-6.2 | The organisation shall appoint a senior-level executive information security officer. |
| IMPORTANT | GOVERN | GV.RR-03.1 | Sufficient resources shall be allocated in line with the cybersecurity risk strategy, roles, responsibilities and policies. |
| IMPORTANT | GOVERN | GV.RR-03.2 from RS.IM-2.1 | The organisation shall assign roles and responsibilities for reviewing and updating response and recovery plans, ensuring they reflect changes in the risk environment and remain effective. |
| BASIC | GOVERN Roles, Responsibilities and Authorities (GV.RR) | GV.RR-04.1 from PR.IP-11.1 | Personnel with access to the organisation’s most critical information or technology shall be authenticated. |
| IMPORTANT | GOVERN | GV.RR-04.2 from PR.IP-11.2 | A cybersecurity process for human resources shall be developed and maintained applicable at recruitment, during employment and at termination of employment. |
| ESSENTIAL | GOVERN Cybersecurity Supply Chain Risk Management (GV.SC) | GV.SC-01.1 from ID.BE-1.2 | A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes shall be documented, reviewed, updated when changes occur, and approved by organisational stakeholders. |
| ESSENTIAL | GOVERN | GV.SC-10.1 | Cybersecurity supply chain risk management plans shall include actions and responsibilities for managing risks that may arise after a supplier relationship or service agreement has ended. |
| IMPORTANT | GOVERN Cybersecurity Supply Chain Risk Management (GV.SC) | GV.SC-02.1 from PR.AT-3.2 | Third-party providers shall notify any transfer, termination or transition of personnel with physical or logical access to business-critical system elements of the organisation. |
| ESSENTIAL | GOVERN | GV.SC-03.1 | Information- and Cybersecurity supply chain risk management shall be integrated into information/cybersecurity and enterprise risk management, risk assessment, and improvement processes. |
| IMPORTANT | GOVERN | GV.SC-05.1 from ID.SC-3.1 | Requirements for addressing cybersecurity risks and the sharing of sensitive information in supply chains shall be established, prioritised, integrated into contracts and other types of formal agreements, and enforced. |
| ESSENTIAL | GOVERN | GV.SC-05.2 from ID.SC-3.2 | Contractual information/cybersecurity requirements for suppliers and external partners shall be implemented to ensure a verifiable flaw resolution process and to ensure that deficiencies identified during information/cybersecurity testing and evaluation are remedied. |
| ESSENTIAL | GOVERN | GV.SC-05.3 from ID.SC-3.3 | The organisation shall establish contractual requirements permitting the organisation to review the information/cybersecurity programmes implemented by suppliers and third-party partners. |
| ESSENTIAL | GOVERN | GV.SC-06.1 | Planning and due diligence shall be carried out to reduce risks before entering into formal relationships with suppliers or other third parties. |
| IMPORTANT | GOVERN | GV.SC-07.1 from ID.SC-2.1 | The risks posed by a supplier, its products and services and other third parties shall be identified, documented, prioritised, mitigated and assessed at least annually and when changes occur during the relationship. |
| ESSENTIAL | GOVERN | GV.SC-07.2 from ID.SC-2.2 | A documented list of all critical suppliers, vendors and partners of the organisation that may be involved in a major incident shall be established, kept up-to-date and made available online and off-line with due regard to confidentiality and security. |
| ESSENTIAL | GOVERN | GV.SC-07.3 from PR.AT-3.4 | The organisation shall audit business-critical third-party service providers for security compliance. |
| ESSENTIAL | GOVERN | GV.SC-07.4 from ID.SC-4.2 | The organisation shall ensure conformity with information/cybersecurity contractual obligations by suppliers and third-party partners through regular reviews of independent audits, assessments, and third party evaluations. |
| IMPORTANT | GOVERN | GV.SC-08.1 from ID.SC-5.1 | The organisation shall identify and document key personnel from relevant suppliers and other third parties to include them in incident planning, response, and recovery activities. |
| ESSENTIAL | GOVERN | GV.SC-09.1 | Supply chain security practices shall be integrated into information/cybersecurity and enterprise risk management programs, and their performance shall be monitored throughout the product and service life cycle. |
| BASIC | IDENTIFY Asset Management (ID.AM) | ID.AM-01.1 from ID.AM-1.1 | An inventory of physical and virtual infrastructure assets—such as hardware, network devices, and cloud-hosted environments—that support information processing shall be documented, reviewed, and updated as changes occur. |
| IMPORTANT | IDENTIFY | ID.AM-01.2 from ID.AM-1.2 | The inventory of enterprise assets associated with information and information processing facilities shall reflect changes in the organisation’s context and include all information necessary for effective accountability. |
| IMPORTANT | IDENTIFY | ID.AM-01.3 from ID.AM-1.3 | When unauthorised hardware is detected, it shall be quarantined for possible exception handling, removed, or replaced, and the inventory shall be updated accordingly. |
| ESSENTIAL | IDENTIFY | ID.AM-01.4 from ID.AM-1.4 | Mechanisms for detecting the presence of unauthorised hardware and firmware components within the organisation’s ICT/OT environment shall be identified. |
| BASIC | IDENTIFY | ID.AM-02.1 from ID.AM-2.1 | An inventory of software, digital services, and business systems used within the organisation shall be documented, reviewed, and updated as changes occur. |
| IMPORTANT | IDENTIFY | ID.AM-02.2 from ID.AM-2.2 | The inventory reflecting which software, services and systems are used in the organisation shall reflect changes in the organisation’s context and include all information necessary for effective accountability. |
| IMPORTANT | IDENTIFY | ID.AM-02.3 from ID.AM-2.3 | The people responsible and accountable for managing software platforms and applications within the organisation shall be formally identified. |
| IMPORTANT | IDENTIFY | ID.AM-02.4 from ID.AM-2.4 | When unauthorised software is detected, it shall be quarantined for possible exception handling, removed, or replaced, and the inventory shall be updated accordingly. |
| ESSENTIAL | IDENTIFY | ID.AM-02.5 from ID.AM-2.5 | Mechanisms for detecting the presence of unauthorised software within the organisation’s ICT/OT environment shall be identified. |
| IMPORTANT | IDENTIFY | ID.AM-03-2 from ID.AM-3.2 | The organisation's network communication and internal data flows shall be mapped, documented, authorised, and updated when changes occur. |
| ESSENTIAL | IDENTIFY | ID.AM-03.3 from ID.AM-3.3 | The organisation's network communication and external data flows shall be mapped, documented , authorised, and updated when changes occur. |
| IMPORTANT | IDENTIFY | ID.AM-04.1 from ID.AM-4.1 | Organisations shall keep a clear and up-to-date list of all external services it uses, including how they connect to their systems. These services shall be reviewed and approved before use, and the list shall be updated whenever changes happen. |
| ESSENTIAL | IDENTIFY | ID.AM-04.2 from ID.AM-4.2 | The organisation shall map, document and authorise the flow of information to/from external systems and update the flow when changes occur. |
| BASIC | IDENTIFY | ID.AM-5.1 from ID.AM-5.1 | The organisation’s assets shall be prioritised based on classification, criticality, and business value. |
| BASIC | IDENTIFY | ID.AM-07.1 from ID.AM-3.1 | Data that the organisation stores and uses shall be identified. |
| IMPORTANT | IDENTIFY | ID.AM-07.2 | Inventories of data and associated metadata shall be maintained for designated data types. |
| ESSENTIAL | IDENTIFY | ID.AM-08.10 from PR.MA-1.7 | The organisation shall verify security controls following maintenance or repairs/patching, and take action as appropriate. |
| IMPORTANT | IDENTIFY | ID.AM-08.11 from PR.MA-2.1 | Remote maintenance and diagnostic activities of organisational assets shall be pre-approved and the performance logged. |
| IMPORTANT | IDENTIFY | ID.AM-08.12 from PR.MA-2.2 | Setting up non-local maintenance and diagnostic sessions over remote network connections shall require strong authenticators and these connections shall be terminated when non-local maintenance is completed. |
| ESSENTIAL | IDENTIFY | ID.AM-08.13 from PR.MA-2.3 | The organisation shall require remote maintenance diagnostic services to be performed from a system that implements security features similar to the security features implemented on the equivalent organisation's critical system. |
| BASIC | IDENTIFY | ID.AM-08.2 from PR.MA-1.1 | Patches and security updates for operating systems and critical system components shall be installed. |
| IMPORTANT | IDENTIFY | ID.AM-08.3 from PR.DS-3.2 | The organisation shall enforce accountability for all its business-critical assets throughout the system lifecycle, including removal, transfers, and disposal. |
| IMPORTANT | IDENTIFY | ID.AM-08.4 from PR.DS-3.3 | The organisation shall ensure that the necessary measures are taken to deal with loss, misuse, damage, or theft of assets. |
| ESSENTIAL | IDENTIFY | ID.AM-08.5 from PR.DS-3.4 | The organisation shall ensure that disposal actions are approved, tracked, documented, and verified. |
| IMPORTANT | IDENTIFY | ID.AM-08.6 from PR.MA-1.2 | The organisation shall plan, perform and document preventive maintenance and repairs on its critical system components according to approved processes and tools. |
| ESSENTIAL | IDENTIFY | ID.AM-08.7 from PR.MA-1.5 | The organisation shall prevent unauthorised removal of maintenance equipment which contains critical system information of the organisation. |
| IMPORTANT | IDENTIFY | ID.AM-08.8 from PR.MA-1.3 | The organisation shall pre-approve, monitor and enforce maintenance tools for use on its critical systems. |
| ESSENTIAL | IDENTIFY | ID.AM-08.9 from PR.MA-1.6 | Maintenance tools and portable storage devices shall be inspected as they enter the facility and shall be protected by anti-malware solutions that scan them for malicious code before they are used on the organisation's systems. |
| IMPORTANT | IDENTIFY Improvement (ID.IM) | ID.IM-02.1 | Security tests and exercises, including those conducted with suppliers and relevant third parties, shall be used to identify areas for improvement. |
| BASIC | IDENTIFY Improvement (ID.IM) | ID.IM-03.1 from RS.IM-1.1 | The organisation shall conduct post-incident evaluations to analyse lessons learned from incident response and recovery, and consequently improve processes / procedures / technologies to enhance its cyber-resilience. |
| IMPORTANT | IDENTIFY | ID.IM-03.2 from RC.IM-1.1 | The organisation shall incorporate lessons learned from incident handling activities into updated or new incident handling processes and/or procedures that are framed by appropriate training after review, approval and testing. |
| IMPORTANT | IDENTIFY | ID.IM-03.3 from PR.IP-7.1 | The organisation shall identify improvements derived from the monitoring, measurements, assessments, and lessons learned and consequently translate this into improved processes / procedures / technologies to enhance its cyber resilience (continuous improvement). |
| IMPORTANT | IDENTIFY | ID.IM-03.4 from PR.IP-8.1 | The organisation shall collaborate and share information about its critical system's related security incidents and mitigation measures with designated partners. |
| IMPORTANT | IDENTIFY | ID.IM-03.5 from PR.IP-8.2 | Communication of effectiveness of protection technologies shall be shared with relevant stakeholders. |
| IMPORTANT | IDENTIFY | ID.IM-03.6 from PR.IP-8.3 | The organisation shall implement, where feasible, automated mechanisms to facilitate the process of information sharing and collaboration. |
| ESSENTIAL | IDENTIFY | ID.IM-03.7 from PR.IP-7.2 | The organisation shall implement independent teams to assess its processes, best practices, and technology solutions to safeguard critical systems and assets. |
| ESSENTIAL | IDENTIFY | ID.IM-03.8 from PR.IP-7.3 | The organisation shall ensure that the security plan for its critical systems facilitates the review, testing, and continual improvement of the security protection processes. |
| ESSENTIAL | IDENTIFY | ID.IM-03.9 from DE.DP-5.2 | The organisation shall conduct specialised assessments including in-depth monitoring, vulnerability scanning, malicious user testing, insider threat assessment, performance/load testing, and verification and validation testing on the organisation's critical systems. |
| IMPORTANT | IDENTIFY | ID.IM-04.1 from PR.IP-9.1 | Contingency and continuity plans shall be established, communicated, maintained, tested, validated, and improved. |
| ESSENTIAL | IDENTIFY | ID.IM-04.2 from PR.IP-9.2 | The organisation shall coordinate the development and testing of Incident Response Plans and other cybersecurity plans that affect operations with stakeholders to ensure that these plans align with overall organisational goals and enhance resilience. |
| BASIC | IDENTIFY Risk Assessment (ID.RA) | ID.RA-01.1 from ID.RA-1.1 | Threats and vulnerabilities shall be identified in all relevant assets, including software, network and system architectures, and facilities that house critical computing assets. |
| IMPORTANT | IDENTIFY | ID.RA-01.2 from ID.RA-1.2 | A process shall be established to continuously monitor, identify, and document vulnerabilities of the organisation's business critical systems. |
| IMPORTANT | IDENTIFY | ID.RA-01.3 from PR.IP-12.1 | The organisation shall establish and maintain a documented process that enables continuous review, analysis and remediation of vulnerabilities and provides for information sharing where applicable. |
| ESSENTIAL | IDENTIFY | ID.RA-01.4 from ID.RA-1.3 | To ensure that organisation's operations are not adversely affected by the testing process, performance/load testing and penetration testing on the organisation’s systems shall be carried out with care. |
| IMPORTANT | IDENTIFY | ID.RA-01.5 from DE.CM-8.1 | Vulnerability scanning shall not adversely impact system functions. |
| IMPORTANT | IDENTIFY | ID.RA-01.6 | Vulnerabilities shall be identified and managed in all relevant assets, including software, network and system architectures, and facilities. |
| IMPORTANT | IDENTIFY | ID.RA-02.1 from ID.RA-2.1 | A threat and vulnerability awareness programme that includes a cross-organisation information-sharing capability shall be implemented. |
| ESSENTIAL | IDENTIFY | ID.RA-02.2 from ID.RA-2.2 | Automated mechanisms shall be implemented to disseminate security alerts and advisories to relevant organisation stakeholders. |
| IMPORTANT | IDENTIFY | ID.RA-03.1 | Threats shall be identified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities. |
| BASIC | IDENTIFY | ID.RA-05.1 from ID.RA-5.1 | The organisation shall conduct risk assessments in which risk is determined by threats, vulnerabilities and the impact on business processes and assets. |
| IMPORTANT | IDENTIFY | ID.RA-05.2 from ID.RA-5.2 | The organisation shall conduct and document risk assessments in which risk is determined by threats, vulnerabilities, impact on business processes and assets, and likelihood of their occurrence. |
| ESSENTIAL | IDENTIFY | ID.RA-05.3 from ID.RA-5.3 | Risk assessment results shall be disseminated to relevant stakeholders. |
| IMPORTANT | IDENTIFY | ID.RA-06.1 from ID.RA-6.1 | Risk responses shall be identified, prioritised, planned, tracked and communicated. |
| IMPORTANT | IDENTIFY | ID.RA-08.1 from RS.AN-5.1 | The organisation shall establish and implement a vulnerability management plan to identify, analyse, assess, mitigate and communicate all types of vulnerabilities including in the form of a Coordinated Vulnerability Disclosure (CVD) according to applicable legal modalities. |
| ESSENTIAL | IDENTIFY | ID.RA-08.2 from RS.AN-5.2 | The organisation shall implement automated mechanisms for disseminating and tracking remedial measures related to vulnerability information that automatically handles vulnerability data collection, disseminates information, tracks remedial measures, includes reporting and accountability, and enables continuous monitoring. |
| BASIC | PROTECT Identity Management, Authentication, and Access Control (PR.AA) | PR.AA-01.1 from PR.AC-1.1 | Identities and credentials for authorised users, services, and hardware shall be managed. |
| IMPORTANT | PROTECT | PR.AA-01.2 from PR.AC-1.2 | Identities and credentials for authorised users, services and hardware shall be managed through automated mechanisms whenever feasible. |
| ESSENTIAL | PROTECT | PR.AA-01.3 from PR.AC-1.3 | System credentials shall be deactivated after a specified period of inactivity unless it would compromise the safe operation of (critical) processes. |
| ESSENTIAL | PROTECT | PR.AA-01.4 from PR.AC-1.4 | For transactions within the organisation's critical systems, the organisation shall implement Multi Factor Authentication (MFA), cryptographic certificates, identity tokens, cryptographic keys and other credentials as appropriate and where feasible. |
| ESSENTIAL | PROTECT | PR.AA-01.5 from PR.AC-1.5 | The organisation’s critical systems shall be monitored for atypical use of system credentials. Credentials associated with significant risk shall be disabled. |
| IMPORTANT | PROTECT | PR.AA-02.1 from PR.AC-6.1 | The organisation shall implement documented procedures for verifying the identity of individuals before issuing credentials that provide access to the organisation's systems. |
| ESSENTIAL | PROTECT | PR.AA-02.2 from PR.AC-6.2 | The organisation shall ensure that unique credentials are used for each authenticated user, device, and process interacting with the organisation's critical systems. These credentials shall be verified, and the unique identifiers shall be captured during system interactions. Exceptions may be made for emergency access ("break-glass" procedures), provided such access is strictly controlled, logged, and reviewed. |
| BASIC | PROTECT | PR.AA-03.1 from PR.AC-3.1 | All wireless access points used by the organisation, including those providing guest access, shall be securely configured, managed, and monitored to prevent unauthorised access and ensure network integrity. |
| BASIC | PROTECT | PR.AA-03.2 from PR.AC-3.2 | Multi-Factor Authentication (MFA) shall be required to access the organisation's networks remotely. |
| IMPORTANT | PROTECT | PR.AA-03.3 from PR.AC-3.3 | The organisation shall define, document, and implement usage restrictions, connection requirements, and authorisation procedures for remote access to its critical systems. These controls shall ensure that only approved users can connect, using secure methods, with access limited to what is necessary for their role. |
| ESSENTIAL | PROTECT | PR.AA-03.4 from R.AC-3.4 | Remote access to the organisation’s critical systems shall be monitored and cryptographic mechanisms shall be implemented where determined necessary. |
| ESSENTIAL | PROTECT | PR.AA-03.5 from R.AC-3.5 | The security for connections with external systems shall be verified and framed by documented agreements. |
| ESSENTIAL | PROTECT | PR.AA-04.1 | Identity assertions shall be protected, conveyed, and verified. |
| BASIC | PROTECT | PR.AA-05.1 from PR.AC-4.1 | Access permissions, rights, and authorisations shall be defined, managed, enforced and reviewed. |
| BASIC | PROTECT | PR.AA-05.2 from PR.AC-4.2 | It shall be determined who needs access to the organisation's business-critical information and technology and the means to gain access. |
| BASIC | PROTECT | PR.AA-05.3 from PR.AC-4.3 | Access rights, privileges and authorisations shall be restricted to the systems and specific information needed to perform the tasks (the principle of Least Privilege). |
| BASIC | PROTECT | PR.AA-05.4 from PR.AC-4.4 | No-one shall have administrative privileges for routine day-to-day tasks. |
| IMPORTANT | PROTECT | PR.AA-05.5 from PR.AC-4.5 | Where technically, operationally, and economically feasible—without compromising system integrity, safety, or compliance—automated mechanisms shall be implemented to manage user accounts on critical ICT and OT systems. Feasibility shall be determined based on system capabilities, integration potential, risk assessment, and business impact. |
| IMPORTANT | PROTECT | PR.AA-05.6 from PR.AC-4.6 | Separation of duties (SoD) shall be ensured in the management of access rights. |
| IMPORTANT | PROTECT | PR.AA-05.7 from PR.AC-4.7 | Privileged users shall be managed and monitored. |
| ESSENTIAL | PROTECT | PR.AA-05.8 from PR.AC-4.8 | Account usage restrictions for specific time periods and locations shall be taken into account in the organisation's security access policy and applied accordingly. |
| ESSENTIAL | PROTECT | PR.AA-05.9 from PR.AC-4.9 | Privileged users shall be managed, monitored and audited. |
| BASIC | PROTECT | PR.AA-06.1 from PR.AC-2.1 | Physical access to all organisational assets, including critical zones, shall be managed, monitored, and enforced based on risk. |
| IMPORTANT | PROTECT | PR.AA-06.2 from PR.AC-2.2 | Physical access controls shall include specific procedures for emergency situations, ensuring continued protection of critical and non-critical assets during such events. |
| ESSENTIAL | PROTECT | PR.AA-06.3 from PR.AC-2.3 | Critical zones shall have additional physical access controls beyond those applied to general facilities. |
| ESSENTIAL | PROTECT | PR.AA-06.4 from PR.AC-2.4 | Assets located within critical zones shall be physically protected against unauthorised access, damage, or interference. |
| BASIC | PROTECT Awareness and Training (PR.AT) | PR.AT-01.1 from PR.AT-1.1 | The organisation shall establish and maintain a cybersecurity awareness and training programme to ensure that all personnel understand how to perform their tasks securely and responsibly. |
| IMPORTANT | PROTECT | PR.AT-01.2 from PR.AT-1.2 | The organisation shall include insider threat awareness and reporting in its cybersecurity training to help personnel recognise and respond to potential internal risks. |
| IMPORTANT | PROTECT | PR.AT-01.3 from RS.CO-1.1 | Personnel shall receive training to understand their specific roles, responsibilities, and priorities during a cybersecurity or information security incident, including the steps they need to follow to respond effectively. |
| ESSENTIAL | PROTECT | PR.AT-01.4 from PR.AT-1.3 | The organisation shall evaluate whether its cybersecurity awareness training is effective in improving knowledge, behaviour, and readiness across the organisation. |
| IMPORTANT | PROTECT | PR.AT-02.1 from PR.AT-4.1 | Members of management bodies shall be able to demonstrate that they have completed training that gives them a solid understanding of information and cybersecurity and risk management so that they can assess information and cyber security risks and their consequences and propose the necessary risk mitigation, considering their roles, responsibilities and authorities. |
| IMPORTANT | PROTECT | PR.AT-02.2 from PR.AT-5.1 | Individuals in specialised roles shall be provided with awareness and training before privileges are granted, so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind. |
| IMPORTANT | PROTECT | PR.AT-02.3 from PR.AT-2.1 | Privileged users shall be qualified before privileges are granted, and these users shall be able to demonstrate the understanding of their roles, responsibilities, and authorities. |
| IMPORTANT | PROTECT Data Security (PR.DS) | PR.DS-01.1 from PR.DS-6.1 | The organisation shall implement software, firmware, and information integrity checks to detect unauthorised changes to its critical system components during storage, transport, start-up and when determined necessary. |
| ESSENTIAL | PROTECT | PR.DS-01.2 from PR.DS-6.2 | The organisation shall implement automated tools where feasible to provide notification upon discovering discrepancies during integrity verification. |
| ESSENTIAL | PROTECT | PR.DS-01.3 from PR.DS-6.3 | The organisation shall define and implement automated responses to detected integrity violations, using predefined safeguards that are proportionate to the severity and impact of the violation. |
| IMPORTANT | PROTECT | PR.DS-01.4 from PR.PT-2.1 | The organisation shall define and enforce clear policies and practical safeguards to manage and restrict the use of portable storage media, in order to reduce the risk of data leakage, unauthorised access, and malware introduction. |
| IMPORTANT | PROTECT | PR.DS-01.5 from PR.PT-2.2 | The organisation shall only allow the use of removable media when absolutely necessary, and shall put technical measures in place to block automatic execution of files from these devices. |
| ESSENTIAL | PROTECT | PR.DS-01.6 from PR.DS-1.1 | The organisation shall protect the confidentiality of its critical assets while at rest. |
| BASIC | PROTECT Data Security (PR.DS) | PR.DS-01.9 from PR.DS-3.1 | Enterprise assets shall be disposed of safely. |
| ESSENTIAL | PROTECT | PR.DS-10.1 from PR.DS-4.3 | The organisation’s critical systems shall be protected against denial-of-service attacks or at least the effect of such attacks shall be limited. |
| BASIC | PROTECT | PR.DS-11.1 from PR.IP-4.1 | Backups for the organisation's business-critical data shall be performed and stored on a different system from the device on which the original data resides. |
| IMPORTANT | PROTECT | PR.DS-11.2 from PR.IP-4.2 | The reliability and integrity of backups shall be verified and tested regularly. |
| IMPORTANT | PROTECT | PR.DS-11.3 from PR.IP-4.3 | The organisation shall maintain secure backups of business-critical data in a separate storage location to ensure data availability in case of system failure or data loss. Backup storage shall apply equivalent security controls as the primary environment. |
| ESSENTIAL | PROTECT | PR.DS-11.4 from PR.IP-4.4 | The organisation shall regularly verify the integrity and recoverability of backups through coordinated testing with all relevant continuity and incident response functions. Backup testing shall be integrated into broader resilience planning, including business continuity, disaster recovery, and cyber incident response. |
| ESSENTIAL | PROTECT | PR.DS-11.5 from PR.IP-4.5 | Backups of critical systems (such as operating systems, configurations, and applications) shall be kept separate from backups of critical information (such as business data, documents, and databases) to support faster and more reliable recovery. |
| ESSENTIAL | PROTECT | PR.DS-02.1 from PR.PT-2.3 | Portable storage devices containing system data shall be controlled and protected while in transit and in storage. |
| ESSENTIAL | PROTECT | PR.DS-02.2 from PR.DS-2.1 | The organisation shall protect its critical and sensitive information while in transit. |
| BASIC | PROTECT Technology Infrastructure Resilience (PR.IR) | PR.IR-01.1 from PR.AC-5.1 | Firewalls shall be installed, configured, and actively maintained on all networks used by the organisation to protect against unauthorised access and cyber threats. |
| BASIC | PROTECT | PR.IR-01.2 from PR.AC-5.2 | To safeguard critical systems, organisations shall implement network segmentation and segregation aligned with trust boundaries and asset criticality, thereby limiting threat propagation and enforcing strict access control. |
| IMPORTANT | PROTECT | PR.IR-01.3 from PR.AC-5.3 | To ensure operational stability and security, the organisation shall, without exception, identify, document, and control connections between components of its critical systems. |
| IMPORTANT | PROTECT | PR.IR-01.4 from PR.AC-5.4 | The organisation shall implement appropriate boundary protection measures to monitor and control communications at external and key internal boundaries of its critical systems, across both IT and OT environments, to ensure secure and reliable operations. |
| ESSENTIAL | PROTECT | PR.IR-01.5 from PR.AC-5.5 | The organisation shall implement, where feasible, authenticated proxy servers or firewalls with URL filtering and threat intelligence capabilities for defined communications traffic between its critical systems and external networks. |
| ESSENTIAL | PROTECT | PR.IR-01.6 from PR.AC-5.6 | The organisation shall ensure that its critical systems are designed to fail securely and remain protected in the event of an operational failure of a border protection device. |
| ESSENTIAL | PROTECT | PR.IR-01.7 from PR.DS-7.1 | The organisation shall ensure that development and test environments are strictly separated from the production environment, particularly in ICS/OT systems where any crossover could compromise safety, endanger health, or disrupt essential operations. |
| ESSENTIAL | PROTECT | PR.IR-01.8 from PR.PT-4.2 | The organisation shall define, monitor, and control the flow of information and data within and between its critical systems to ensure that only authorised and secure exchanges occur, regardless of network boundaries or system architecture. |
| ESSENTIAL | PROTECT | PR.IR-01.9 from PR.PT-4.3 | The organisation shall manage interfaces with external telecommunications services as part of its broader network security policy, by defining how traffic is controlled, ensuring the confidentiality and integrity of transmitted information, and reviewing and documenting any exceptions to established rules. |
| IMPORTANT | PROTECT | PR.IR-02.1 from PR.IP-5.1 | The organisation shall define, implement and maintain policies and procedures related to emergency and safety systems, fire protection systems and environmental controls for its critical systems. |
| ESSENTIAL | PROTECT | PR.IR-02.2 from PR.IP-5.2 | The organisation shall implement fire detection devices that activate and notify key personnel automatically in the event of a fire. |
| ESSENTIAL | PROTECT | PR.IR-03.1 | The organisation shall implement mechanisms to ensure that critical systems and services remain operational or can be quickly restored during both normal operations and adverse conditions. |
| IMPORTANT | PROTECT | PR.IR-04.1 from PR.DS-4.1 | Adequate resource capacity planning shall ensure that availability of organisation's critical system information processing, networking, telecommunications, and data storage is maintained. |
| IMPORTANT | PROTECT Platform Security (PR.PS) | PR.PS-01.1 from PR.IP-1.1 | The organisation shall develop, document, and maintain a baseline configuration for its business-critical systems. |
| ESSENTIAL | PROTECT | PR.PS-01.2 from PR.IP-1.2 | The organisation shall configure its business-critical systems to operate with only the essential functions needed for the intended purpose. This includes reviewing and updating baseline configurations to disable any non-essential capabilities. |
| ESSENTIAL | PROTECT | PR.PS-01.3 from PR.PT-3.2 | The organisation shall identify and disable specific functions, ports, protocols, and services within its critical systems that are not required for business operations. |
| ESSENTIAL | PROTECT | PR.PS-01.4 from PR.PT-3.3 | The organisation shall implement technical safeguards to enforce a policy of ‘deny-all’ and ‘permit-by-exception’ so that only authorised software programmes are executed. |
| ESSENTIAL | PROTECT | PR.PS-01.5 from DE.CM-7.2 | Unauthorised configuration changes to organisation's systems shall be monitored and addressed with the appropriate mitigation actions. |
| IMPORTANT | PROTECT | PR.PS-02.1 from DE.CM-3.3 | The organisation shall enforce restrictions on software usage and installation, and ensure that software is maintained, replaced, or removed based on its associated risk. |
| IMPORTANT | PROTECT | PR.PS-03.1 from PR.MA-1.4 | Hardware used in business-critical environments shall be maintained, replaced, or removed based on its associated security and operational risk. |
| BASIC | PROTECT Platform Security (PR.PS) | PR.PS-04.1 from PR.PT-1.1 | Logs shall be maintained, documented, and monitored. |
| IMPORTANT | PROTECT | PR.PS-04.2 from PR.PT-1.2 | The organisation shall ensure that logbook records contain an authoritative time source or internal clock time stamp that is compared and synchronised with an authoritative time source. |
| IMPORTANT | PROTECT | PR.PS-04.3 from PR.DS-4.2 | Audit data from the organisation's critical systems shall be moved to an alternative system. |
| ESSENTIAL | PROTECT | PR.PS-04.4 from PR.PT-1.3 | The organisation shall ensure that audit processing failures on the organisation's systems generate alerts and trigger defined responses. |
| ESSENTIAL | PROTECT | PR.PS-04.5 from PR.PT-1.4 | The organisation shall ensure that authorised personnel can extend or enhance audit logging and monitoring capabilities when needed to support investigations or incident response. |
| BASIC | PROTECT | PR.PS-05.1 from PR.PT-4.1 | Web and e-mail filters shall be installed and used. |
| IMPORTANT | PROTECT | PR.PS-05.2 | Installation and execution of unauthorised software shall be prevented. |
| IMPORTANT | PROTECT | PR.PS-06.1 from PR.IP-2.1 | Security shall be considered throughout the lifecycle of systems and applications, whether developed internally or acquired externally. |
| IMPORTANT | PROTECT | PR.PS-06.2 from PR.IP-3.1 | Changes and exceptions shall be tested and validated before being implemented into operational systems. |
| ESSENTIAL | PROTECT | PR.PS-06.3 from PR.IP-2.2 | Secure software development practices shall be integrated into all phases of the software development lifecycle, and their effectiveness shall be regularly monitored and improved. |
| ESSENTIAL | PROTECT | PR.PS-06.4 from PR.IP-3.2 | For planned changes to the organisation's critical systems, a security impact analysis shall be performed in a separate test environment before implementation in an operational environment. |
| IMPORTANT | DETECT Adverse Event Analysis (DE.AE) | DE.AE-02.1 from DE.AE-2.1 | Cybersecurity and information security events shall be reviewed and analysed to identify potential attack targets and methods, in accordance with applicable laws, regulations, standards, and policies. |
| ESSENTIAL | DETECT | DE.AE-02.2 from DE.AE-2.2 | The organisation shall implement automated mechanisms where feasible to review and analyse detected events. |
| BASIC | DETECT Adverse Event Analysis (DE.AE) | DE.AE-03.1 from DE.AE-3.1 | The logging functionality of protection and detection tools shall be enabled. Logs shall be backed up and kept for a predefined period, and regularly reviewed to identify unusual or potentially harmful activity. |
| IMPORTANT | DETECT | DE.AE-03.2 from DE.AE-3.2 | The organisation shall ensure that event data from critical systems is collected and correlated using information from multiple relevant sources. |
| ESSENTIAL | DETECT | DE.AE-03.3 from DE.AE-3.3 | The organisation shall combine event analysis with information from vulnerability scans, system performance data, monitoring of critical systems, and facility monitoring, where feasible. |
| ESSENTIAL | DETECT | DE.AE-04.1 from DE.AE-4.1 | The organisation shall assess the negative impacts of detected events on its operations, assets, and individuals, and shall link these impacts to the results of its risk assessments. |
| IMPORTANT | DETECT | DE.AE-06.1 from DE.DP-4.1 | Information about adverse events shall be promptly delivered to authorised personnel and systems to enable timely detection, investigation, and response. |
| IMPORTANT | DETECT | DE.AE-08.1 from DE.AE-5.1 | Incidents shall be reported when adverse events meet defined and documented incident criteria. |
| BASIC | DETECT Continuous Monitoring (DE.CM) | DE.CM-01.1 from DE.CM-1.1 | Firewalls shall be installed and operated at the network boundaries, including endpoint firewalls. |
| BASIC | DETECT | DE.CM-01.2 from DE.CM-4.1 | Anti-virus, -spyware, and other -malware programs shall be installed and updated. |
| IMPORTANT | DETECT | DE.CM-01.3 from DE.CM-1.2 | The organisation shall monitor and identify unauthorised use of its business-critical systems through the detection of unauthorised local connections, network connections and remote connections. |
| ESSENTIAL | DETECT | DE.CM-01.4 from DE.CM-1.3 | The organisation shall continuously monitor its network to spot signs of cyber threats or unusual activity, using clearly defined rules for what counts as a potential security incident. |
| IMPORTANT | DETECT | DE.CM-02.1 from DE.CM-2.1 | The physical environment shall be monitored to find potentially adverse events. |
| ESSENTIAL | DETECT | DE.CM-02.2 from DE.CM-2.2 | Physical access to the organisation's critical systems and devices, in addition to physical access monitoring to the facility, shall be supplemented by physical intrusion alarms, surveillance equipment, and independent monitoring teams. |
| BASIC | DETECT | DE.CM-03-1 from DE.CM-3.1 | End point and network protection tools to monitor end-user behaviour for dangerous activity shall be implemented. |
| IMPORTANT | DETECT | DE.CM-03.2 from DE.CM-3.2 | End point and network protection tools that monitor end-user behaviour for dangerous activity shall be managed. |
| IMPORTANT | DETECT | DE.CM-06.1 from DE.CM-6.1 | External service provider activities and services shall be secured and monitored to find potentially adverse events. |
| IMPORTANT | DETECT | DE.CM-06.2 from DE.CM-6.2 | External service providers' conformance with personnel security policies and procedures and contract security requirements shall be monitored relative to their cybersecurity risks. |
| IMPORTANT | DETECT | DE.CM-09.1 from DE.CM-5.1 | The organisation shall monitor computing hardware, software, runtime environments, and their data to detect potentially adverse events. |
| ESSENTIAL | DETECT | DE.CM-09.2 from PR.DS-8.1 | The organisation shall implement hardware integrity checks to detect unauthorised tampering of critical system hardware. Controls shall be proportionate to the organisation’s risk profile and operational capacity. |
| ESSENTIAL | DETECT | DE.CM-09.3 from PR.DS-8.2 | The organisation's incident response plan shall include measures to detect unauthorised tampering with the hardware of critical systems. |
| ESSENTIAL | DETECT | DE.CM-09.4 from DE.CM-4.2 | The organisation shall establish a system to accurately distinguish between legitimate alerts and false positives, ensuring effective detection and removal of malicious code. |
| ESSENTIAL | RESPOND Incident Analysis (RS.AN) | RS.AN-03.1 from RS.AN-3.2 | Each incident shall be analysed to determine what occurred and to identify its root cause. |
| ESSENTIAL | RESPOND | RS.AN-06.1 from RS.AN-3.1 | Actions performed during an investigation shall be recorded, and the records' integrity and provenance shall be preserved. |
| ESSENTIAL | RESPOND | RS.AN-07.1 | Incident data and metadata shall be collected and protected to ensure their accuracy, authenticity, and traceability. |
| ESSENTIAL | RESPOND | RS.AN-08.1 | An incident’s magnitude shall be estimated and validated. |
| BASIC | RESPOND Incident Response Reporting and Communication (RS.CO) | RS.CO-02.1 from RS.CO-3.1 | Information about cybersecurity incidents shall be communicated to employees in a way that is clear and easy to understand. |
| IMPORTANT | RESPOND | RS.CO-02.2 from RS.CO-3.2 | Cybersecurity incidents shall be shared with relevant external stakeholders within the timeframes defined in the Incident Response Plan, including reporting significant incidents to authorities as required by law. |
| BASIC | RESPOND Incident Management (RS.MA) | RS.MA-01.1 from RS.RP-1.1 | An incident response plan, including defined roles, responsibilities, and authorities, shall be executed during or after a cybersecurity event affecting the organisation's critical systems. |
| IMPORTANT | RESPOND | RS.MA-01.2 from RS.CO-4.1 | The organisation shall coordinate information/cybersecurity incident response actions with all predefined stakeholders. |
| IMPORTANT | RESPOND | RS.MA-02.1 from RS.AN-1.1 | Information/cybersecurity incident reports shall be triaged and validated in accordance with the organisation’s incident response procedures. |
| ESSENTIAL | RESPOND | RS.MA-02.2 from RS.AN-1.2 | Automated tools shall be used to support the investigation and impact assessment of validated cybersecurity incidents. |
| IMPORTANT | RESPOND | RS.MA-03.1 from RS.AN-2.1 | Information/cybersecurity incidents shall be categorised, prioritised and escalated as specified in the incident response plan. |
| IMPORTANT | RESPOND | RS.MA-05.1 | Clear criteria shall be defined and applied to determine when incident recovery processes need to be initiated. |
| IMPORTANT | RESPOND Incident Mitigation (RS.MI) | RS.MI-01.1 from RS.MI-1.1 | Cybersecurity incidents shall be contained and eliminated. Any decision to accept and retain certain cybersecurity risks shall be formally documented. |
| IMPORTANT | RESPOND | RS.MI-01.2 from PR.DS-5.1 | The organisation shall detect unauthorised access or data leakage and take appropriate mitigation actions, including monitoring of critical systems at external boundaries and key internal points. |
| IMPORTANT | RECOVER Incident Recovery Communication (RC.CO) | RC.CO-03.1 from RC.CO-3.1 | Recovery activities and progress in restoring operational capabilities shall be communicated to designated internal and external stakeholders in accordance with established communication procedures. |
| IMPORTANT | RECOVER | RC.CO-04.1 from RC.CO-1.1 | Public updates on incident recovery shall be shared using approved communication methods and messaging, in accordance with established procedures. |
| ESSENTIAL | RECOVER | RC.CO-04.2 from RC.CO-1.2 | The organisation shall assign a Public Relations Officer (PRO) to manage public communications during information/cybersecurity incident recovery, ensuring that public updates are shared while maintaining the confidentiality, integrity, and accuracy of the information. |
| ESSENTIAL | RECOVER | RC.CO-04.3 from RC.CO-2.1 | The organisation shall implement a crisis communication strategy to mitigate negative impacts during a crisis and help restore its reputation afterward. |
| BASIC | RECOVER Incident Recovery Plan Execution (RC.RP) | RC.RP-01.1 from RC.RP-1.1 | A recovery process for disasters and information/cybersecurity incidents shall be developed and executed. |
| ESSENTIAL | RECOVER | RC.RP-02.1 from RC.RP-1.2 | The organisation's essential functions and services shall be continued with little or no loss of operational continuity, and continuity shall be maintained until full system recovery. |
| IMPORTANT | RECOVER | RC.RP-05.1 | The integrity of restored systems and assets shall be verified before they are returned to service. Systems and services shall be fully restored, and normal operations shall be confirmed. |
| IMPORTANT | RECOVER | RC.RP-06.1 | The end of incident recovery shall be formally declared based on predefined criteria, and all incident-related documentation shall be completed and reviewed. |
| IMPORTANT | — ID.BE | ID.BE-3.1 | Priorities for organisational mission, objectives, and activities are established and communicated. |
| IMPORTANT | — ID.RM | ID.RM-3.1 | The organisation’s role in critical infrastructure and its sector shall determine the organisation’s risk appetite. |
| IMPORTANT | — ID.SC | ID.SC-4.1 | The organisation shall review assessments of suppliers’ and third-party partners’ compliance with contractual obligations by routinely reviewing audits, test results, and other evaluations. |
| IMPORTANT | — PR.AC | PR.AC-7.1 | The organisation shall perform a documented risk assessment on its critical system transactions and authenticate users, devices, and other assets (e.g. single-factor, multi-factor) commensurate with the risk of the transaction (e.g. individuals’ security and privacy risks and other organisational risks). |
| IMPORTANT | — Awareness and Training (PR.AT) | PR.AT-3.1 | The organisation shall establish and enforce security requirements for business-critical third-party providers and users. |
| IMPORTANT | — Awareness and Training (PR.AT) | PR.AT-3.3 | The organisation shall monitor business-critical service providers and users in relation to security compliance. |
| IMPORTANT | — PR.IP | PR.IP-6.1 | The organisation shall ensure that data from its critical systems are destroyed in accordance with policy. |
| IMPORTANT | — PR.PT | PR.PT-3.1 | The organisation shall configure the business-critical systems to provide only essential capabilities |
| IMPORTANT | — Adverse Event Analysis (DE.AE) | DE.AE-5.2 | The organisation shall define incident alert thresholds. |
| IMPORTANT | — Continuous Monitoring (DE.CM) | DE.CM-7.1 | The organisation's business-critical systems shall be monitored to detect access by unauthorised personnel, and unauthorised connections, devices, access points, and software. |
| IMPORTANT | — Continuous Monitoring (DE.CM) | DE.CM-8.2 | The vulnerability scanning process shall include analysis, remediation, and information sharing. |
| IMPORTANT | — DE.DP | DE.DP-2.1 | The organisation shall conduct detection activities in accordance with applicable federal and regional laws, industry regulations and standards, policies, and other applicable requirements. |
| IMPORTANT | — DE.DP | DE.DP-3.1 | The organisation shall validate that event detection processes are operating as intended. |
| IMPORTANT | — DE.DP | DE.DP-5.1 | Improvements derived from the monitoring, measurement, assessment, testing, review, and lessons learned shall be incorporated into detection process revisions. |
| IMPORTANT | — Incident Response Reporting and Communication (RS.CO) | RS.CO-2.1 | The organisation shall implement reporting on information/cybersecurity incidents in its critical systems within an organisation-defined timeframe to organisation-defined personnel or roles. |
| IMPORTANT | — Incident Response Reporting and Communication (RS.CO) | RS.CO-5.1 | The organisation shall share information/cybersecurity event information voluntarily, as appropriate, with external stakeholders, industry security groups… to achieve broader situational awareness with regard to information security and cybersecurity. |
| IMPORTANT | — Incident Analysis (RS.AN) | RS.AN-4.1 | Information/cybersecurity incidents shall be categorised according to the level of severity and impact consistent with the evaluation criteria included the incident response plan. |
| IMPORTANT | — RS.IM | RS.IM-1.2 | Lessons learned from incident-handling shall be translated into updated or new incident handling procedures that shall be tested, approved, and trained. |
| ESSENTIAL | — ID.SC | ID.SC-1.1 | The organisation shall document, review, approve, update when changes occur, and implement a cyber supply chain risk management process that supports the identification, assessment, and mitigation of the risks associated with the distributed and interconnected nature of ICT/OT product and service supply chains. |
| ESSENTIAL | — ID.SC | ID.SC-5.2 | The organisation shall identify and document key personnel from suppliers and third-party partners to include them as stakeholders in testing and execution of the response and recovery plans. |
| ESSENTIAL | — PR.IP | PR.IP-6.2 | Sanitisation processes shall be documented and tested. |
| ESSENTIAL | — Adverse Event Analysis (DE.AE) | DE.AE-1.1 | The organisation shall ensure that a baseline of network operations and expected data flows for its critical systems is developed, documented, and maintained to track events. |
| ESSENTIAL | — Incident Analysis (RS.AN) | RS.AN-2.2 | The organisation shall implement automated mechanisms to support incident impact analysis. |
| ESSENTIAL | — Incident Response Reporting and Communication (RS.CO) | RS.CO-2.2 | Events shall be reported in a manner consistent with established criteria. |
Sources
- CyFun® 2025 self-assessment tools, current release — BASIC v2026-02-20 · IMPORTANT v2026-02-20 · ESSENTIAL v3.1 (2026-02-25)
- CyFun® 2025 self-assessment tools, previous release — BASIC, IMPORTANT and ESSENTIAL v2025-10-21.
- CyFun® 2023 self-assessment tool v2025-10-21. All published on cyfun.eu.
- Mapping_CyFun2023-CyFun2025_v2026-02-25.xlsx — the CCB mapping used to link a 2025 measure to the 2023 measure it comes from, and to identify the measures deleted in 2025.
Every requirement text that changed is shown word by word on the measure descriptions page.