NL-P-02 requirements

This page lists every requirement of NL-P-02 (Essential Entity Requirements, version RC1.0) as published on 6 November 2026. The PDF is authoritative: each requirement links to the page it is on. You can also read the full text or search all requirements.

218 entries: 218 controls. Obligation: 218 mandatory.

Legal basis of the document: NIS2 Art. 21, NIS2 Art. 20, NIS2 Art. 23, CIR 2024/2690.

4.1.1 GV.OC-01 The organisational mission is understood and informs cybersecurity risk management

Read section 4.1.1 in the full text

GV.OC-01.1

The organisation's mission shall be established, communicated and shall form the basis for information and cybersecurity risk management.

Control · obligation: mandatory · PDF page 12

• Group: GV.OC-01 The organisational mission is understood and informs cybersecurity risk management

4.1.2 GV.OC-02 Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered

Read section 4.1.2 in the full text

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.

Control · obligation: mandatory · PDF page 12

• Group: GV.OC-02 Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered

4.1.3 GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity are understood and managed

Read section 4.1.3 in the full text

GV.OC-03.1 — Legal and regulatory requirements regarding information and cybersecurity shall be identified and implemented.

Legal and regulatory requirements regarding information and cybersecurity shall be identified and implemented.

Control · obligation: mandatory · PDF page 13

• Group: GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity are understood and managed

GV.OC-03.2

Legal, regulatory, and contractual obligations related to information and cybersecurity shall be continuously managed to ensure they remain accurate, up to date, and effectively applied.

Control · obligation: mandatory · PDF page 13

• Group: GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity are understood and managed

4.1.4 GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organisation are understood and communicated

Read section 4.1.4 in the full text

GV.OC-04.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

Control · obligation: mandatory · PDF page 14

• Group: GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organisation are understood and communicated

GV.OC-04.2

The organisation shall define and document cybersecurity requirements for essential operations, validate them through testing and audits, maintain records of results and corrective actions, and regularly update requirements based on evolving risks

Control · obligation: mandatory · PDF page 14

• Group: GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organisation are understood and communicated

GV.OC-04.3

Redundancy shall be implemented to meet availability requirements as defined by the organisation, legislation and/or regulations

Control · obligation: mandatory · PDF page 15

• Group: GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organisation are understood and communicated

GV.OC-04.4

Recovery time and recovery point objectives for the resumption of essential ICT/ OT system processes shall be defined and monitored.

Control · obligation: mandatory · PDF page 16

• Group: GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organisation are understood and communicated

4.1.5 GV.OC-05 Outcomes, capabilities, and services that the organisation depends on are understood and communicated

Read section 4.1.5 in the full text

GV.OC-05.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.

Control · obligation: mandatory · PDF page 17

• Group: GV.OC-05 Outcomes, capabilities, and services that the organisation depends on are understood and communicated

4.2.1 GV.RM-01 Risk management objectives are established and agreed to by organisational stakeholders

Read section 4.2.1 in the full text

GV.RM-01.1

Information/cybersecurity objectives shall be identified, agreed to by organisational stakeholders and approved by senior management

Control · obligation: mandatory · PDF page 18

• Group: GV.RM-01 Risk management objectives are established and agreed to by organisational stakeholders

4.2.2 GV.RM-02 Risk appetite and risk tolerance statements are established, communicated, and maintained

Read section 4.2.2 in the full text

GV.RM-02.1

Risk appetite and risk tolerance statements shall be defined, documented, approved by senior management, communicated, and maintained.

Control · obligation: mandatory · PDF page 18

• Group: GV.RM-02 Risk appetite and risk tolerance statements are established, communicated, and maintained

4.2.3 GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes

Read section 4.2.3 in the full text

GV.RM-03.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.

Control · obligation: mandatory · PDF page 19

• Group: GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes

GV.RM-03.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.

Control · obligation: mandatory · PDF page 19

• Group: GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes

4.2.4 GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated

Read section 4.2.4 in the full text

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.

Control · obligation: mandatory · PDF page 21

• Group: GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated

4.2.5 GV.RM-05 Lines of communication across the organisation are established for cybersecurity risks, including risks from suppliers and other third parties

Read section 4.2.5 in the full text

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.

Control · obligation: mandatory · PDF page 22

• Group: GV.RM-05 Lines of communication across the organisation are established for cybersecurity risks, including risks from suppliers and other third parties

4.3.1 GV.RR-01 Organisational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving

Read section 4.3.1 in the full text

GV.RR-01.1

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.

Control · obligation: mandatory · PDF page 23

• Group: GV.RR-01 Organisational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving

4.3.2 GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced

Read section 4.3.2 in the full text

GV.RR-02.1

Information security and cybersecurity 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.

Control · obligation: mandatory · PDF page 23

• Group: GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced

4.3.3 GV.RR-03 Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies

Read section 4.3.3 in the full text

GV.RR-03.1

Sufficient resources shall be allocated in line with the cybersecurity risk strategy, roles, responsibilities and policies.

Control · obligation: mandatory · PDF page 25

• Group: GV.RR-03 Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies

GV.RR-03.2

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.

Control · obligation: mandatory · PDF page 25

• Group: GV.RR-03 Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies

4.3.4 GV.RR-04 Cybersecurity is included in human resources practices

Read section 4.3.4 in the full text

GV.RR-04.1 — Personnel with access to the organisation’s most critical information or technology shall be authenticated.

Personnel with access to the organisation’s most critical information or technology shall be authenticated.

Control · obligation: mandatory · PDF page 26

• Group: GV.RR-04 Cybersecurity is included in human resources practices

GV.RR-04.2

A cybersecurity process for human resources shall be developed and maintained applicable at recruitment, during employment and at termination of employment.

Control · obligation: mandatory · PDF page 26

• Group: GV.RR-04 Cybersecurity is included in human resources practices

4.4.1 GV.PO-01 Policy for managing cybersecurity risks is established based on organisational context, cybersecurity strategy, and priorities and is communicated and enforced

Read section 4.4.1 in the full text

GV.PO-01.1

Policies and procedures for managing information and cybersecurity shall be established, documented, reviewed, approved, updated when changes occur, communicated and enforced.

Control · obligation: mandatory · PDF page 28

• Group: GV.PO-01 Policy for managing cybersecurity risks is established based on organisational context, cybersecurity strategy, and priorities and is communicated and enforced

GV.PO-01.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 its implementation.

Control · obligation: mandatory · PDF page 28

• Group: GV.PO-01 Policy for managing cybersecurity risks is established based on organisational context, cybersecurity strategy, and priorities and is communicated and enforced

4.5.1 GV.OV-02 The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organisational requirements and risks

Read section 4.5.1 in the full text

GV.OV-02.1

The information and cybersecurity risk management strategy shall be reviewed and adjusted to ensure coverage of organisational requirements and risks.

Control · obligation: mandatory · PDF page 30

• Group: GV.OV-02 The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organisational requirements and risks

4.5.2 GV.OV-03 Organisational cybersecurity risk management performance is evaluated and reviewed for adjustments needed

Read section 4.5.2 in the full text

GV.OV-03.1 — The organisation's cybersecurity risk management performance shall be evaluated, reviewed and adjusted when necessary

The organisation's cybersecurity risk management performance shall be evaluated, reviewed and adjusted when necessary

Control · obligation: mandatory · PDF page 30

• Group: GV.OV-03 Organisational cybersecurity risk management performance is evaluated and reviewed for adjustments needed

4.6.1 GV.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organisational stakeholders

Read section 4.6.1 in the full text

GV.SC-01.1

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.

Control · obligation: mandatory · PDF page 32

• Group: GV.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organisational stakeholders

4.6.2 GV.SC-02 Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally

Read section 4.6.2 in the full text

GV.SC-02.1

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.

Control · obligation: mandatory · PDF page 33

• Group: GV.SC-02 Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally

4.6.3 GV.SC-03 Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes

Read section 4.6.3 in the full text

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.

Control · obligation: mandatory · PDF page 33

• Group: GV.SC-03 Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes

4.6.4 GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritised, and integrated into contracts and other types of agreements with suppliers and other relevant third parties

Read section 4.6.4 in the full text

GV.SC-05.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.

Control · obligation: mandatory · PDF page 35

• Group: GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritised, and integrated into contracts and other types of agreements with suppliers and other relevant third parties

GV.SC-05.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.

Control · obligation: mandatory · PDF page 35

• Group: GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritised, and integrated into contracts and other types of agreements with suppliers and other relevant third parties

GV.SC-05.3

The organisation shall establish contractual requirements permitting the organisation to review the information/cybersecurity programs implemented by suppliers and third-party partners.

Control · obligation: mandatory · PDF page 36

• Group: GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritised, and integrated into contracts and other types of agreements with suppliers and other relevant third parties

4.6.5 GV.SC-06 Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships

Read section 4.6.5 in the full text

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.

Control · obligation: mandatory · PDF page 37

• Group: GV.SC-06 Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships

4.6.6 GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritised, assessed, responded to, and monitored over the course of the relationship

Read section 4.6.6 in the full text

GV.SC-07.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.

Control · obligation: mandatory · PDF page 37

• Group: GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritised, assessed, responded to, and monitored over the course of the relationship

GV.SC-07.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.

Control · obligation: mandatory · PDF page 38

• Group: GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritised, assessed, responded to, and monitored over the course of the relationship

GV.SC-07.4

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.

Control · obligation: mandatory · PDF page 39

• Group: GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritised, assessed, responded to, and monitored over the course of the relationship

4.6.7 GV.SC-08 Relevant suppliers and other third parties are included in incident planning, response, and recovery activities

Read section 4.6.7 in the full text

GV.SC-08.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.

Control · obligation: mandatory · PDF page 40

• Group: GV.SC-08 Relevant suppliers and other third parties are included in incident planning, response, and recovery activities

4.6.8 GV.SC-09 Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle

Read section 4.6.8 in the full text

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.

Control · obligation: mandatory · PDF page 40

• Group: GV.SC-09 Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle

4.6.9 GV.SC-010 Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement

Read section 4.6.9 in the full text

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.

Control · obligation: mandatory · PDF page 41

• Group: GV.SC-010 Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement

5.1.1 ID.AM-01 Inventories of hardware managed by the organisation are maintained

Read section 5.1.1 in the full text

ID.AM-01.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.

Control · obligation: mandatory · PDF page 43

• Group: ID.AM-01 Inventories of hardware managed by the organisation are maintained

ID.AM-01.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.

Control · obligation: mandatory · PDF page 43

• Group: ID.AM-01 Inventories of hardware managed by the organisation are maintained

ID.AM-01.3

When unauthorised hardware is detected, it shall be quarantined for possible exception handling, removed, or replaced, and the inventory shall be updated accordingly.

Control · obligation: mandatory · PDF page 44

• Group: ID.AM-01 Inventories of hardware managed by the organisation are maintained

ID.AM-01.4

Mechanisms for detecting the presence of unauthorised hardware and firmware components within the organisation’s ICT/OT environment shall be identified.

Control · obligation: mandatory · PDF page 45

• Group: ID.AM-01 Inventories of hardware managed by the organisation are maintained

5.1.2 ID.AM-02 Inventories of software, services, and systems managed by the organisation are maintained

Read section 5.1.2 in the full text

ID.AM-02.1

An inventory of software, digital services, and business systems used within the organisation shall be documented, reviewed, and updated as changes occur.

Control · obligation: mandatory · PDF page 45

• Group: ID.AM-02 Inventories of software, services, and systems managed by the organisation are maintained

ID.AM-02.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.

Control · obligation: mandatory · PDF page 46

• Group: ID.AM-02 Inventories of software, services, and systems managed by the organisation are maintained

ID.AM-02.3

The people responsible and accountable for managing software platforms and applications within the organisation shall be formally identified.

Control · obligation: mandatory · PDF page 47

• Group: ID.AM-02 Inventories of software, services, and systems managed by the organisation are maintained

ID.AM-02.4

When unauthorised software is detected, it shall be quarantined for possible exception handling, removed, or replaced, and the inventory shall be updated accordingly.

Control · obligation: mandatory · PDF page 47

• Group: ID.AM-02 Inventories of software, services, and systems managed by the organisation are maintained

ID.AM-02.5

Mechanisms for detecting the presence of unauthorised software within the organisation’s ICT/OT environment shall be identified.

Control · obligation: mandatory · PDF page 48

• Group: ID.AM-02 Inventories of software, services, and systems managed by the organisation are maintained

5.1.3 ID.AM-03 Representations of the organisation's authorised network communication and internal and external network data flows are maintained

Read section 5.1.3 in the full text

ID.AM-03.2

The organisation's network communication and internal data flows shall be mapped, documented, authorised, and updated when changes occur.

Control · obligation: mandatory · PDF page 48

• Group: ID.AM-03 Representations of the organisation's authorised network communication and internal and external network data flows are maintained

ID.AM-03.3

The organisation's network communication and external data flows shall be mapped, documented, authorised, and updated when changes occur.

Control · obligation: mandatory · PDF page 49

• Group: ID.AM-03 Representations of the organisation's authorised network communication and internal and external network data flows are maintained

5.1.4 ID.AM-04 Inventories of services provided by suppliers are maintained

Read section 5.1.4 in the full text

ID.AM-04.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.

Control · obligation: mandatory · PDF page 50

• Group: ID.AM-04 Inventories of services provided by suppliers are maintained

ID.AM-04.2

The organisation shall map, document and authorise the flow of information to/from external systems and update the flow when changes occur.

Control · obligation: mandatory · PDF page 50

• Group: ID.AM-04 Inventories of services provided by suppliers are maintained

5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

Read section 5.1.7 in the full text

ID.AM-08.2 — Patches and security updates for Operating Systems and critical system components shall be installed.

Patches and security updates for Operating Systems and critical system components shall be installed.

Control · obligation: mandatory · PDF page 53

• Group: ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

ID.AM-08.3

The organisation shall enforce accountability for all its business-critical assets throughout the system lifecycle, including removal, transfers, and disposition.

Control · obligation: mandatory · PDF page 54

• Group: ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

ID.AM-08.4

The organisation shall ensure that the necessary measures are taken to deal with loss, misuse, damage, or theft of assets.

Control · obligation: mandatory · PDF page 55

• Group: ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

ID.AM-08.5 — The organisation shall ensure that disposal actions are approved, tracked, documented, and verified.

The organisation shall ensure that disposal actions are approved, tracked, documented, and verified.

Control · obligation: mandatory · PDF page 56

• Group: ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

ID.AM-08.6

The organisation shall plan, perform and document preventive maintenance and repairs on its critical system components according to approved processes and tools.

Control · obligation: mandatory · PDF page 56

• Group: ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

ID.AM-08.7

The organisation shall prevent unauthorised removal of maintenance equipment containing critical system information of the organisation.

Control · obligation: mandatory · PDF page 57

• Group: ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

ID.AM-08.9

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.

Control · obligation: mandatory · PDF page 58

• Group: ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

ID.AM-08.10

The organisation shall verify security controls following maintenance or repairs/ patching, and take action as appropriate.

Control · obligation: mandatory · PDF page 58

• Group: ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

ID.AM-08.11 — Remote maintenance and diagnostic activities of organisational assets shall be pre-approved and the performance logged.

Remote maintenance and diagnostic activities of organisational assets shall be pre-approved and the performance logged.

Control · obligation: mandatory · PDF page 59

• Group: ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

ID.AM-08.12

Setting up non-local maintenance and diagnostic sessions over remote network connections shall require strong authenticators and such connections shall be terminated when non-local maintenance is completed.

Control · obligation: mandatory · PDF page 59

• Group: ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

ID.AM-08.13

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.

Control · obligation: mandatory · PDF page 60

• Group: ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

5.2.1 ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded

Read section 5.2.1 in the full text

ID.RA-01.1

Threats and vulnerabilities shall be identified in all relevant assets, including software, network and system architectures, and facilities that house critical computing assets.

Control · obligation: mandatory · PDF page 61

• Group: ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded

ID.RA-01.2

A process shall be established to continuously monitor, identify, and document vulnerabilities of the organisation's business critical systems.

Control · obligation: mandatory · PDF page 61

• Group: ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded

ID.RA-01.3

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.

Control · obligation: mandatory · PDF page 62

• Group: ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded

ID.RA-01.4

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.

Control · obligation: mandatory · PDF page 63

• Group: ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded

ID.RA-01.5 — Vulnerability scanning shall not adversely impact system functions.

Vulnerability scanning shall not adversely impact system functions.

Control · obligation: mandatory · PDF page 63

• Group: ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded

ID.RA-01.6

Vulnerabilities shall be identified and managed in all relevant assets, including software, network and system architectures, and facilities.

Control · obligation: mandatory · PDF page 64

• Group: ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded

5.2.2 ID.RA-02 Cyber threat intelligence is received from information-sharing forums and sources

Read section 5.2.2 in the full text

ID.RA-02.1

A threat and vulnerability awareness program that includes a cross-organisation information-sharing capability shall be implemented.

Control · obligation: mandatory · PDF page 65

• Group: ID.RA-02 Cyber threat intelligence is received from information-sharing forums and sources

ID.RA-02.2

Automated mechanisms shall be implemented to disseminate security alerts and advisories to relevant organisation stakeholders.

Control · obligation: mandatory · PDF page 65

• Group: ID.RA-02 Cyber threat intelligence is received from information-sharing forums and sources

5.2.3 ID.RA-03 Internal and external threats to the organisation are identified and recorded

Read section 5.2.3 in the full text

ID.RA-03.1

Threats shall be identified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities.

Control · obligation: mandatory · PDF page 66

• Group: ID.RA-03 Internal and external threats to the organisation are identified and recorded

5.2.4 ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritisation

Read section 5.2.4 in the full text

ID.RA-05.1

The organisation shall conduct risk assessments in which risk is determined by threats, vulnerabilities and the impact on business processes and assets.

Control · obligation: mandatory · PDF page 67

• Group: ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritisation

ID.RA-05.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.

Control · obligation: mandatory · PDF page 67

• Group: ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritisation

5.2.5 ID.RA-06 Risk responses are selected, prioritised, planned, tracked, and communicated

Read section 5.2.5 in the full text

ID.RA-06.1 — Risk responses shall be identified, prioritised, planned, tracked and communicated.

Risk responses shall be identified, prioritised, planned, tracked and communicated.

Control · obligation: mandatory · PDF page 68

• Group: ID.RA-06 Risk responses are selected, prioritised, planned, tracked, and communicated

5.2.6 ID.RA-08 Processes for receiving, analysing, and responding to vulnerability disclosures are established important

Read section 5.2.6 in the full text

ID.RA-08.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.

Control · obligation: mandatory · PDF page 69

• Group: ID.RA-08 Processes for receiving, analysing, and responding to vulnerability disclosures are established important

ID.RA-08.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.

Control · obligation: mandatory · PDF page 70

• Group: ID.RA-08 Processes for receiving, analysing, and responding to vulnerability disclosures are established important

5.3.1 ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties

Read section 5.3.1 in the full text

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.

Control · obligation: mandatory · PDF page 71

• Group: ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties

5.3.2 ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities

Read section 5.3.2 in the full text

ID.IM-03.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.

Control · obligation: mandatory · PDF page 71

• Group: ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities

ID.IM-03.2

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.

Control · obligation: mandatory · PDF page 72

• Group: ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities

ID.IM-03.3

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).

Control · obligation: mandatory · PDF page 72

• Group: ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities

ID.IM-03.4

The organisation shall collaborate and share information about its critical system's related security incidents and mitigation measures with designated partners.

Control · obligation: mandatory · PDF page 73

• Group: ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities

ID.IM-03.6

The organisation shall implement, where feasible, automated mechanisms to facilitate the process of information sharing and collaboration.

Control · obligation: mandatory · PDF page 74

• Group: ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities

ID.IM-03.7

The organisation shall implement independent teams to assess its processes, best practices, and technology solutions to safeguard critical systems and assets.

Control · obligation: mandatory · PDF page 75

• Group: ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities

ID.IM-03.8

The organisation shall ensure that the security plan for its critical systems facilitates the review, testing, and continual improvement of the security protection processes.

Control · obligation: mandatory · PDF page 75

• Group: ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities

ID.IM-03.9

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.

Control · obligation: mandatory · PDF page 76

• Group: ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities

5.3.3 ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved

Read section 5.3.3 in the full text

ID.IM-04.1 — Contingency and continuity plans shall be established, communicated, maintained, tested, validated, and improved.

Contingency and continuity plans shall be established, communicated, maintained, tested, validated, and improved.

Control · obligation: mandatory · PDF page 77

• Group: ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved

ID.IM-04.2

The organisation shall coordinate the development and the 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.

Control · obligation: mandatory · PDF page 78

• Group: ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved

6.1.1 PR.AA-01 Identities and credentials for authorised users, services, and hardware are managed by the organisation

Read section 6.1.1 in the full text

PR.AA-01.1 — Identities and credentials for authorised users, services, and hardware shall be managed.

Identities and credentials for authorised users, services, and hardware shall be managed.

Control · obligation: mandatory · PDF page 79

• Group: PR.AA-01 Identities and credentials for authorised users, services, and hardware are managed by the organisation

PR.AA-01.2

Identities and credentials for authorised users, services and hardware shall be managed through automated mechanisms whenever feasible.

Control · obligation: mandatory · PDF page 80

• Group: PR.AA-01 Identities and credentials for authorised users, services, and hardware are managed by the organisation

PR.AA-01.3

System credentials shall be deactivated after a specified period of inactivity unless it would compromise the safe operation of (critical) processes.

Control · obligation: mandatory · PDF page 80

• Group: PR.AA-01 Identities and credentials for authorised users, services, and hardware are managed by the organisation

PR.AA-01.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.

Control · obligation: mandatory · PDF page 81

• Group: PR.AA-01 Identities and credentials for authorised users, services, and hardware are managed by the organisation

PR.AA-01.5

The organisation’s critical systems shall be monitored for atypical use of system credentials. Credentials associated with significant risk shall be disabled.

Control · obligation: mandatory · PDF page 82

• Group: PR.AA-01 Identities and credentials for authorised users, services, and hardware are managed by the organisation

6.1.2 PR.AA-02 Identities are proofed and bound to credentials based on the context of interactions

Read section 6.1.2 in the full text

PR.AA-02.1

The organisation shall implement documented procedures for verifying the identity of individuals before issuing credentials that provide access to the organisation's systems.

Control · obligation: mandatory · PDF page 83

• Group: PR.AA-02 Identities are proofed and bound to credentials based on the context of interactions

PR.AA-02.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.

Control · obligation: mandatory · PDF page 83

• Group: PR.AA-02 Identities are proofed and bound to credentials based on the context of interactions

6.1.3 PR.AA-03 Users, services, and hardware are authenticated

Read section 6.1.3 in the full text

PR.AA-03.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.

Control · obligation: mandatory · PDF page 84

• Group: PR.AA-03 Users, services, and hardware are authenticated

PR.AA-03.2 — Multi-Factor Authentication (MFA) shall be required to access the organisation's networks remotely.

Multi-Factor Authentication (MFA) shall be required to access the organisation's networks remotely.

Control · obligation: mandatory · PDF page 85

• Group: PR.AA-03 Users, services, and hardware are authenticated

PR.AA-03.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.

Control · obligation: mandatory · PDF page 86

• Group: PR.AA-03 Users, services, and hardware are authenticated

PR.AA-03.4

Remote access to the organisation’s critical systems shall be monitored and cryptographic mechanisms shall be implemented where determined necessary.

Control · obligation: mandatory · PDF page 87

• Group: PR.AA-03 Users, services, and hardware are authenticated

PR.AA-03.5 — The security for connections with external systems shall be verified and framed by documented agreements.

The security for connections with external systems shall be verified and framed by documented agreements.

Control · obligation: mandatory · PDF page 87

• Group: PR.AA-03 Users, services, and hardware are authenticated

6.1.5 PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

Read section 6.1.5 in the full text

PR.AA-05.1 — Access permissions, rights, and authorisations shall be defined, managed, enforced and reviewed.

Access permissions, rights, and authorisations shall be defined, managed, enforced and reviewed.

Control · obligation: mandatory · PDF page 89

• Group: PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

PR.AA-05.2

It shall be determined who needs access to the organisation's business-critical information and technology and the means to gain access.

Control · obligation: mandatory · PDF page 90

• Group: PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

PR.AA-05.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).

Control · obligation: mandatory · PDF page 91

• Group: PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

PR.AA-05.4 — No one shall have administrative privileges for routine day-to-day tasks.

No one shall have administrative privileges for routine day-to-day tasks.

Control · obligation: mandatory · PDF page 92

• Group: PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

PR.AA-05.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.

Control · obligation: mandatory · PDF page 92

• Group: PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

PR.AA-05.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.

Control · obligation: mandatory · PDF page 95

• Group: PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

6.1.6 PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk

Read section 6.1.6 in the full text

PR.AA-06.1

Physical access to all organisational assets, including critical zones, shall be managed, monitored, and enforced based on risk.

Control · obligation: mandatory · PDF page 97

• Group: PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk

PR.AA-06.2

Physical access controls shall include specific procedures for emergency situations, ensuring continued protection of critical and non-critical assets during such events.

Control · obligation: mandatory · PDF page 98

• Group: PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk

PR.AA-06.3 — Critical zones shall have additional physical access controls beyond those applied to general facilities.

Critical zones shall have additional physical access controls beyond those applied to general facilities.

Control · obligation: mandatory · PDF page 99

• Group: PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk

PR.AA-06.4 — Assets located within critical zones shall be physically protected against unauthorised access, damage, or interference.

Assets located within critical zones shall be physically protected against unauthorised access, damage, or interference.

Control · obligation: mandatory · PDF page 99

• Group: PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk

6.2.1 PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind

Read section 6.2.1 in the full text

PR.AT-01.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.

Control · obligation: mandatory · PDF page 101

• Group: PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind

PR.AT-01.2

The organisation shall include insider threat awareness and reporting in its cybersecurity training to help personnel recognise and respond to potential internal risks.

Control · obligation: mandatory · PDF page 102

• Group: PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind

PR.AT-01.3

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.

Control · obligation: mandatory · PDF page 102

• Group: PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind

PR.AT-01.4

The organisation shall evaluate whether its cybersecurity awareness training is effective in improving knowledge, behaviour, and readiness across the organisation.

Control · obligation: mandatory · PDF page 103

• Group: PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind

6.2.2 PR.AT-02 Individuals in specialised roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind

Read section 6.2.2 in the full text

PR.AT-02.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 cybersecurity risks and their consequences and propose the necessary risk mitigation, considering their roles, responsibilities and authorities.

Control · obligation: mandatory · PDF page 103

• Group: PR.AT-02 Individuals in specialised roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind

PR.AT-02.2

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.

Control · obligation: mandatory · PDF page 104

• Group: PR.AT-02 Individuals in specialised roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind

PR.AT-02.3

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.

Control · obligation: mandatory · PDF page 104

• Group: PR.AT-02 Individuals in specialised roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind

6.3.1 PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

Read section 6.3.1 in the full text

PR.DS-01.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.

Control · obligation: mandatory · PDF page 106

• Group: PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

PR.DS-01.2

The organisation shall implement automated tools where feasible to provide notification upon discovering discrepancies during integrity verification.

Control · obligation: mandatory · PDF page 107

• Group: PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

PR.DS-01.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.

Control · obligation: mandatory · PDF page 107

• Group: PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

PR.DS-01.4

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.

Control · obligation: mandatory · PDF page 108

• Group: PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

PR.DS-01.5

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.

Control · obligation: mandatory · PDF page 109

• Group: PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

6.3.2 PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected

Read section 6.3.2 in the full text

PR.DS-02.1 — Portable storage devices containing system data shall be controlled and protected while in transit and in storage.

Portable storage devices containing system data shall be controlled and protected while in transit and in storage.

Control · obligation: mandatory · PDF page 111

• Group: PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected

6.3.3 PR.DS-10 The confidentiality, integrity, and availability of data-in-use are protected

Read section 6.3.3 in the full text

PR.DS-10.1

The organisation’s critical systems shall be protected against denial-of-service attacks or at least the effect of such attacks shall be limited.

Control · obligation: mandatory · PDF page 112

• Group: PR.DS-10 The confidentiality, integrity, and availability of data-in-use are protected

6.3.4 PR.DS-11 Backups of data are created, protected, maintained, and tested

Read section 6.3.4 in the full text

PR.DS-11.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.

Control · obligation: mandatory · PDF page 112

• Group: PR.DS-11 Backups of data are created, protected, maintained, and tested

PR.DS-11.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.

Control · obligation: mandatory · PDF page 114

• Group: PR.DS-11 Backups of data are created, protected, maintained, and tested

PR.DS-11.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.

Control · obligation: mandatory · PDF page 115

• Group: PR.DS-11 Backups of data are created, protected, maintained, and tested

PR.DS-11.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.

Control · obligation: mandatory · PDF page 115

• Group: PR.DS-11 Backups of data are created, protected, maintained, and tested

6.4.1 PR.PS-01 Configuration management practices are established and applied

Read section 6.4.1 in the full text

PR.PS-01.1 — The organisation shall develop, document, and maintain a baseline configuration for its business critical systems.

The organisation shall develop, document, and maintain a baseline configuration for its business critical systems.

Control · obligation: mandatory · PDF page 117

• Group: PR.PS-01 Configuration management practices are established and applied

PR.PS-01.2

The organisation shall configure its business-critical systems to operate with only the essential functions needed for their intended purpose. This includes reviewing and updating baseline configurations to disable any non-essential capabilities.

Control · obligation: mandatory · PDF page 118

• Group: PR.PS-01 Configuration management practices are established and applied

PR.PS-01.3

The organisation shall identify and disable specific functions, ports, protocols, and services within its critical systems that are not required for business operations.

Control · obligation: mandatory · PDF page 118

• Group: PR.PS-01 Configuration management practices are established and applied

PR.PS-01.4

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.

Control · obligation: mandatory · PDF page 119

• Group: PR.PS-01 Configuration management practices are established and applied

PR.PS-01.5

Unauthorised configuration changes to organisation's systems shall be monitored and addressed with the appropriate mitigation actions.

Control · obligation: mandatory · PDF page 119

• Group: PR.PS-01 Configuration management practices are established and applied

6.4.2 PR.PS-02 Software is maintained, replaced, and removed commensurate with risk

Read section 6.4.2 in the full text

PR.PS-02.1

The organisation shall enforce restrictions on software usage and installation, and ensure that software is maintained, replaced, or removed based on its associated risk.

Control · obligation: mandatory · PDF page 119

• Group: PR.PS-02 Software is maintained, replaced, and removed commensurate with risk

6.4.3 PR.PS-03 Hardware is maintained, replaced, and removed commensurate with risk

Read section 6.4.3 in the full text

PR.PS-03.1

Hardware used in business-critical environments shall be maintained, replaced, or removed based on its associated security and operational risk.

Control · obligation: mandatory · PDF page 120

• Group: PR.PS-03 Hardware is maintained, replaced, and removed commensurate with risk

6.4.4 PR.PS-04 Log records are generated and made available for continuous monitoring

Read section 6.4.4 in the full text

PR.PS-04.1 — Logs shall be maintained, documented, and monitored.

Logs shall be maintained, documented, and monitored.

Control · obligation: mandatory · PDF page 120

• Group: PR.PS-04 Log records are generated and made available for continuous monitoring

PR.PS-04.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.

Control · obligation: mandatory · PDF page 121

• Group: PR.PS-04 Log records are generated and made available for continuous monitoring

PR.PS-04.5

The organisation shall ensure that authorised personnel can extend or enhance audit logging and monitoring capabilities when needed to support investigations or incident response.

Control · obligation: mandatory · PDF page 122

• Group: PR.PS-04 Log records are generated and made available for continuous monitoring

6.4.6 PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

Read section 6.4.6 in the full text

PR.PS-06.1

Security shall be considered throughout the lifecycle of systems and applications, whether developed internally or acquired externally.

Control · obligation: mandatory · PDF page 124

• Group: PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

PR.PS-06.3

Secure software development practices shall be integrated into all phases of the software development lifecycle, and their effectiveness should be regularly monitored and improved.

Control · obligation: mandatory · PDF page 125

• Group: PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

PR.PS-06.4

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.

Control · obligation: mandatory · PDF page 126

• Group: PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

6.5.1 PR.IR-01 Networks and environments are protected from unauthorised logical access and usage

Read section 6.5.1 in the full text

PR.IR-01.1

Firewalls shall be installed, configured, and actively maintained on all networks used by the organisation to protect against unauthorised access and cyber threats.

Control · obligation: mandatory · PDF page 127

• Group: PR.IR-01 Networks and environments are protected from unauthorised logical access and usage

PR.IR-01.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

Control · obligation: mandatory · PDF page 128

• Group: PR.IR-01 Networks and environments are protected from unauthorised logical access and usage

PR.IR-01.3

To ensure operational stability and security, the organisation shall, without exception, identify, document, and control connections between components of its critical systems.

Control · obligation: mandatory · PDF page 128

• Group: PR.IR-01 Networks and environments are protected from unauthorised logical access and usage

PR.IR-01.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.

Control · obligation: mandatory · PDF page 129

• Group: PR.IR-01 Networks and environments are protected from unauthorised logical access and usage

PR.IR-01.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.

Control · obligation: mandatory · PDF page 130

• Group: PR.IR-01 Networks and environments are protected from unauthorised logical access and usage

PR.IR-01.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.

Control · obligation: mandatory · PDF page 131

• Group: PR.IR-01 Networks and environments are protected from unauthorised logical access and usage

PR.IR-01.7

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.

Control · obligation: mandatory · PDF page 132

• Group: PR.IR-01 Networks and environments are protected from unauthorised logical access and usage

PR.IR-01.8

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.

Control · obligation: mandatory · PDF page 133

• Group: PR.IR-01 Networks and environments are protected from unauthorised logical access and usage

PR.IR-01.9

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.

Control · obligation: mandatory · PDF page 134

• Group: PR.IR-01 Networks and environments are protected from unauthorised logical access and usage

6.5.2 PR.IR-02 The organisation's technology assets are protected from environmental threats

Read section 6.5.2 in the full text

PR.IR-02.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.

Control · obligation: mandatory · PDF page 135

• Group: PR.IR-02 The organisation's technology assets are protected from environmental threats

PR.IR-02.2

The organisation shall implement fire detection devices that activate and notify key personnel automatically in the event of a fire.

Control · obligation: mandatory · PDF page 135

• Group: PR.IR-02 The organisation's technology assets are protected from environmental threats

6.5.3 PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations

Read section 6.5.3 in the full text

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.

Control · obligation: mandatory · PDF page 136

• Group: PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations

6.5.4 PR.IR-04 Adequate resource capacity to ensure availability is maintained

Read section 6.5.4 in the full text

PR.IR-04.1

Adequate resource capacity planning shall ensure that availability of organisation's critical system information processing, networking, telecommunications, and data storage is maintained.

Control · obligation: mandatory · PDF page 137

• Group: PR.IR-04 Adequate resource capacity to ensure availability is maintained

7.1.1 DE.CM-01 Networks and network services are monitored to find potentially adverse events

Read section 7.1.1 in the full text

DE.CM-01.1 — Firewalls shall be installed and operated at the network boundaries, including endpoint firewalls.

Firewalls shall be installed and operated at the network boundaries, including endpoint firewalls.

Control · obligation: mandatory · PDF page 138

• Group: DE.CM-01 Networks and network services are monitored to find potentially adverse events

DE.CM-01.3

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.

Control · obligation: mandatory · PDF page 139

• Group: DE.CM-01 Networks and network services are monitored to find potentially adverse events

DE.CM-01.4

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.

Control · obligation: mandatory · PDF page 140

• Group: DE.CM-01 Networks and network services are monitored to find potentially adverse events

7.1.2 DE.CM-02 The physical environment is monitored to find potentially adverse events

Read section 7.1.2 in the full text

DE.CM-02.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.

Control · obligation: mandatory · PDF page 141

• Group: DE.CM-02 The physical environment is monitored to find potentially adverse events

7.1.3 DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events

Read section 7.1.3 in the full text

DE.CM-03.1 — End point and network protection tools to monitor end-user behaviour for dangerous activity shall be implemented.

End point and network protection tools to monitor end-user behaviour for dangerous activity shall be implemented.

Control · obligation: mandatory · PDF page 141

• Group: DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events

7.1.4 DE.CM-06 External service provider activities and services are monitored to find potentially adverse events

Read section 7.1.4 in the full text

DE.CM-06.1 — External service provider activities and services shall be secured and monitored to find potentially adverse events.

External service provider activities and services shall be secured and monitored to find potentially adverse events.

Control · obligation: mandatory · PDF page 143

• Group: DE.CM-06 External service provider activities and services are monitored to find potentially adverse events

DE.CM-06.2

External service providers' conformance with personnel security policies and procedures and contract security requirements shall be monitored relative to their cybersecurity risks.

Control · obligation: mandatory · PDF page 143

• Group: DE.CM-06 External service provider activities and services are monitored to find potentially adverse events

7.1.5 DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events

Read section 7.1.5 in the full text

DE.CM-09.1

The organisation shall monitor computing hardware, software, runtime environments, and their data to detect potentially adverse events.

Control · obligation: mandatory · PDF page 144

• Group: DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events

DE.CM-09.2

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.

Control · obligation: mandatory · PDF page 144

• Group: DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events

DE.CM-09.3

The organisation's incident response plan shall include measures to detect unauthorised tampering with the hardware of critical systems.

Control · obligation: mandatory · PDF page 145

• Group: DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events

DE.CM-09.4

The organisation shall establish a system to accurately distinguish between legitimate alerts and false positives, ensuring effective detection and removal of malicious code.

Control · obligation: mandatory · PDF page 146

• Group: DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events

7.2.1 DE.AE-02 Potentially adverse events are analysed to better understand associated activities

Read section 7.2.1 in the full text

DE.AE-02.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.

Control · obligation: mandatory · PDF page 148

• Group: DE.AE-02 Potentially adverse events are analysed to better understand associated activities

7.2.2 DE.AE-03 Information is correlated from multiple sources

Read section 7.2.2 in the full text

DE.AE-03.1

The logging functionality of protection and detection tools shall be enabled. Logs shall be backed up and retained for a predefined period and regularly reviewed to identify unusual or potentially harmful activity.

Control · obligation: mandatory · PDF page 149

• Group: DE.AE-03 Information is correlated from multiple sources

DE.AE-03.2

The organisation shall ensure that event data from critical systems is collected and correlated using information from multiple relevant sources.

Control · obligation: mandatory · PDF page 149

• Group: DE.AE-03 Information is correlated from multiple sources

DE.AE-03.3

The organisation shall combine event analysis with information from vulnerability scans, system performance data, monitoring of critical systems, and facility monitoring, where feasible.

Control · obligation: mandatory · PDF page 150

• Group: DE.AE-03 Information is correlated from multiple sources

7.2.3 DE.AE-04 The estimated impact and scope of adverse events are understood

Read section 7.2.3 in the full text

DE.AE-04.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.

Control · obligation: mandatory · PDF page 150

• Group: DE.AE-04 The estimated impact and scope of adverse events are understood

7.2.4 DE.AE-06 Information on adverse events is provided to authorised staff and tools

Read section 7.2.4 in the full text

DE.AE-06.1

Information about adverse events shall be promptly delivered to authorised personnel and systems to enable timely detection, investigation, and response.

Control · obligation: mandatory · PDF page 151

• Group: DE.AE-06 Information on adverse events is provided to authorised staff and tools

7.2.5 DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria

Read section 7.2.5 in the full text

DE.AE-08.1 — Incidents shall be reported when adverse events meet defined and documented incident criteria.

Incidents shall be reported when adverse events meet defined and documented incident criteria.

Control · obligation: mandatory · PDF page 152

• Group: DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria

8.1.1 RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared

Read section 8.1.1 in the full text

RS.MA-01.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.

Control · obligation: mandatory · PDF page 153

• Group: RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared

RS.MA-01.2 — The organisation shall coordinate information/cybersecurity incident response actions with all predefined stakeholders.

The organisation shall coordinate information/cybersecurity incident response actions with all predefined stakeholders.

Control · obligation: mandatory · PDF page 154

• Group: RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared

8.1.2 RS.MA-02 Incident reports are triaged and validated

Read section 8.1.2 in the full text

RS.MA-02.1

Information/cybersecurity incident reports shall be triaged and validated in accordance with the organisation’s incident response procedures.

Control · obligation: mandatory · PDF page 154

• Group: RS.MA-02 Incident reports are triaged and validated

8.1.3 RS.MA-03 Incidents are categorised and prioritised

Read section 8.1.3 in the full text

RS.MA-03.1

Information/cybersecurity incidents shall be categorised, prioritised and escalated as determined in the incident response plan.

Control · obligation: mandatory · PDF page 155

• Group: RS.MA-03 Incidents are categorised and prioritised

8.1.4 RS.MA-05 The criteria for initiating incident recovery are applied

Read section 8.1.4 in the full text

RS.MA-05.1 — Clear criteria shall be defined and applied to determine when incident recovery processes need to be initiated.

Clear criteria shall be defined and applied to determine when incident recovery processes need to be initiated.

Control · obligation: mandatory · PDF page 156

• Group: RS.MA-05 The criteria for initiating incident recovery are applied

8.2.2 RS.AN-06 Actions performed during an investigation are recorded, and the records’ integrity and provenance are preserved

Read section 8.2.2 in the full text

RS.AN-06.1

Actions performed during an investigation shall be recorded, and the records' integrity and provenance shall be preserved.

Control · obligation: mandatory · PDF page 157

• Group: RS.AN-06 Actions performed during an investigation are recorded, and the records’ integrity and provenance are preserved

8.2.3 RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved

Read section 8.2.3 in the full text

RS.AN-07.1 — Incident data and metadata shall be collected and protected to ensure their accuracy, authenticity, and traceability.

Incident data and metadata shall be collected and protected to ensure their accuracy, authenticity, and traceability.

Control · obligation: mandatory · PDF page 158

• Group: RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved

8.2.4 RS.AN-08 An incident's magnitude is estimated and validated

Read section 8.2.4 in the full text

RS.AN-08.1 — An incident’s magnitude shall be estimated and validated.

An incident’s magnitude shall be estimated and validated.

Control · obligation: mandatory · PDF page 158

• Group: RS.AN-08 An incident's magnitude is estimated and validated

8.3.1 RS.CO-02 Internal and external stakeholders are notified of incidents

Read section 8.3.1 in the full text

RS.CO-02.1

Information about cybersecurity incidents shall be communicated to employees in a way that is clear and easy to understand.

Control · obligation: mandatory · PDF page 159

• Group: RS.CO-02 Internal and external stakeholders are notified of incidents

RS.CO-02.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.

Control · obligation: mandatory · PDF page 159

• Group: RS.CO-02 Internal and external stakeholders are notified of incidents

8.4.1 RS.MI-01 Incidents are contained

Read section 8.4.1 in the full text

RS.MI-01.1

Cybersecurity incidents shall be contained and eliminated. Any decision to accept and retain certain cybersecurity risks shall be formally documented.

Control · obligation: mandatory · PDF page 161

• Group: RS.MI-01 Incidents are contained

RS.MI-01.2

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.

Control · obligation: mandatory · PDF page 161

• Group: RS.MI-01 Incidents are contained

9.1.1 RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process

Read section 9.1.1 in the full text

RC.RP-01.1 — A recovery process for disasters and information/cybersecurity incidents shall be developed and executed.

A recovery process for disasters and information/cybersecurity incidents shall be developed and executed.

Control · obligation: mandatory · PDF page 163

• Group: RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process

9.1.2 RC.RP-02 Recovery actions are selected, scoped, prioritised, and performed

Read section 9.1.2 in the full text

RC.RP-02.1

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.

Control · obligation: mandatory · PDF page 164

• Group: RC.RP-02 Recovery actions are selected, scoped, prioritised, and performed

9.1.3 RC.RP-05 The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed

Read section 9.1.3 in the full text

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.

Control · obligation: mandatory · PDF page 164

• Group: RC.RP-05 The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed

9.1.4 RC.RP-06 The end of incident recovery is declared based on criteria, and incident-related documentation is completed

Read section 9.1.4 in the full text

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.

Control · obligation: mandatory · PDF page 165

• Group: RC.RP-06 The end of incident recovery is declared based on criteria, and incident-related documentation is completed

9.2.1 RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders

Read section 9.2.1 in the full text

RC.CO-03.1

Recovery activities and progress in restoring operational capabilities shall be communicated to designated internal and external stakeholders in accordance with established communication procedures.

Control · obligation: mandatory · PDF page 166

• Group: RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders

9.2.2 RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging

Read section 9.2.2 in the full text

RC.CO-04.1

Public updates on incident recovery shall be shared using approved communication methods and messaging, in accordance with established procedures.

Control · obligation: mandatory · PDF page 166

• Group: RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging

RC.CO-04.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.

Control · obligation: mandatory · PDF page 167

• Group: RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging

RC.CO-04.3

The organisation shall implement a crisis communication strategy to mitigate negative impacts during a crisis and help restore its reputation afterward.

Control · obligation: mandatory · PDF page 167

• Group: RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging

7.1.1 DE.CM-01 Networks and network services are monitored to find potentially adverse events

Read section 7.1.1 in the full text

DE.CM-01.2 — Anti-virus, -spyware, and other -malware programs shall be installed and updated.

Anti-virus, -spyware, and other -malware programs shall be installed and updated.

Control · obligation: mandatory · PDF page 138

• Group: DE.CM-01 Networks and network services are monitored to find potentially adverse events

4.3.2 GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced

Read section 4.3.2 in the full text

GV.RR-02.2 — The organisation shall appoint a senior-level executive information security officer.

The organisation shall appoint a senior-level executive information security officer.

Control · obligation: mandatory · PDF page 24

• Group: GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced

5.2.4 ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritisation

Read section 5.2.4 in the full text

ID.RA-05.3 — Risk assessment results shall be disseminated to relevant stakeholders.

Risk assessment results shall be disseminated to relevant stakeholders.

Control · obligation: mandatory · PDF page 68

• Group: ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritisation

4.6.6 GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritised, assessed, responded to, and monitored over the course of the relationship

Read section 4.6.6 in the full text

GV.SC-07.3 — The organisation shall audit business-critical third-party service providers for security compliance.

The organisation shall audit business-critical third-party service providers for security compliance.

Control · obligation: mandatory · PDF page 39

• Group: GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritised, assessed, responded to, and monitored over the course of the relationship

5.1.5 ID.AM-05 Assets are prioritised based on classification, criticality, resources, and impact on the mission

Read section 5.1.5 in the full text

ID.AM-05.1 — The organisation’s assets shall be prioritised based on classification, criticality, and business value.

The organisation’s assets shall be prioritised based on classification, criticality, and business value.

Control · obligation: mandatory · PDF page 51

• Group: ID.AM-05 Assets are prioritised based on classification, criticality, resources, and impact on the mission

5.1.6 ID.AM-07 Inventories of data and corresponding metadata for designated data types are maintained

Read section 5.1.6 in the full text

ID.AM-07.1 — Data that the organisation stores and uses shall be identified.

Data that the organisation stores and uses shall be identified.

Control · obligation: mandatory · PDF page 52

• Group: ID.AM-07 Inventories of data and corresponding metadata for designated data types are maintained

ID.AM-07.2 — Inventories of data and associated metadata shall be maintained for designated data types.

Inventories of data and associated metadata shall be maintained for designated data types.

Control · obligation: mandatory · PDF page 52

• Group: ID.AM-07 Inventories of data and corresponding metadata for designated data types are maintained

5.1.7 ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

Read section 5.1.7 in the full text

ID.AM-08.8 — The organisation shall pre-approve, monitor and enforce maintenance tools for use on its critical systems.

The organisation shall pre-approve, monitor and enforce maintenance tools for use on its critical systems.

Control · obligation: mandatory · PDF page 57

• Group: ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles

5.3.2 ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities

Read section 5.3.2 in the full text

ID.IM-03.5 — Communication of effectiveness of protection technologies shall be shared with relevant stakeholders.

Communication of effectiveness of protection technologies shall be shared with relevant stakeholders.

Control · obligation: mandatory · PDF page 74

• Group: ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities

6.1.4 PR.AA-04 Identity assertions are protected, conveyed, and verified

Read section 6.1.4 in the full text

PR.AA-04.1 — Identity assertions shall be protected, conveyed, and verified

Identity assertions shall be protected, conveyed, and verified

Control · obligation: mandatory · PDF page 88

• Group: PR.AA-04 Identity assertions are protected, conveyed, and verified

6.1.5 PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

Read section 6.1.5 in the full text

PR.AA-05.6 — Separation of duties (SoD) shall be ensured in the management of access rights.

Separation of duties (SoD) shall be ensured in the management of access rights.

Control · obligation: mandatory · PDF page 93

• Group: PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

PR.AA-05.7 — Privileged users shall be managed and monitored.

Privileged users shall be managed and monitored.

Control · obligation: mandatory · PDF page 94

• Group: PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

PR.AA-05.9 — Privileged users shall be managed, monitored and audited.

Privileged users shall be managed, monitored and audited.

Control · obligation: mandatory · PDF page 96

• Group: PR.AA-05 Access permissions, entitlements, and authorisations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

6.3.1 PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

Read section 6.3.1 in the full text

PR.DS-01.6 — The organisation shall protect the confidentiality of its critical assets while at rest.

The organisation shall protect the confidentiality of its critical assets while at rest.

Control · obligation: mandatory · PDF page 109

• Group: PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

PR.DS-01.9 — Enterprise assets shall be disposed of safely.

Enterprise assets shall be disposed of safely.

Control · obligation: mandatory · PDF page 110

• Group: PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

6.3.2 PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected

Read section 6.3.2 in the full text

PR.DS-02.2 — The organisation shall protect its critical and sensitive information while in transit.

The organisation shall protect its critical and sensitive information while in transit.

Control · obligation: mandatory · PDF page 111

• Group: PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected

6.3.4 PR.DS-11 Backups of data are created, protected, maintained, and tested

Read section 6.3.4 in the full text

PR.DS-11.2 — The reliability and integrity of backups shall be verified and tested regularly.

The reliability and integrity of backups shall be verified and tested regularly.

Control · obligation: mandatory · PDF page 113

• Group: PR.DS-11 Backups of data are created, protected, maintained, and tested

6.4.4 PR.PS-04 Log records are generated and made available for continuous monitoring

Read section 6.4.4 in the full text

PR.PS-04.3 — Audit data from the organisation's critical systems shall be moved to an alternative system.

Audit data from the organisation's critical systems shall be moved to an alternative system.

Control · obligation: mandatory · PDF page 122

• Group: PR.PS-04 Log records are generated and made available for continuous monitoring

PR.PS-04.4

The organisation shall ensure that audit processing failures on the organisation's systems generate alerts and trigger defined responses.

Control · obligation: mandatory · PDF page 122

• Group: PR.PS-04 Log records are generated and made available for continuous monitoring

6.4.5 PR.PS-05 Installation and execution of unauthorised software are prevented

Read section 6.4.5 in the full text

PR.PS-05.1 — Web and e-mail filters shall be installed and used.

Web and e-mail filters shall be installed and used.

Control · obligation: mandatory · PDF page 123

• Group: PR.PS-05 Installation and execution of unauthorised software are prevented

PR.PS-05.2 — Installation and execution of unauthorised software shall be prevented.

Installation and execution of unauthorised software shall be prevented.

Control · obligation: mandatory · PDF page 123

• Group: PR.PS-05 Installation and execution of unauthorised software are prevented

6.4.6 PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

Read section 6.4.6 in the full text

PR.PS-06.2 — Changes and exceptions shall be tested and validated before being implemented into operational systems.

Changes and exceptions shall be tested and validated before being implemented into operational systems.

Control · obligation: mandatory · PDF page 124

• Group: PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

7.1.2 DE.CM-02 The physical environment is monitored to find potentially adverse events

Read section 7.1.2 in the full text

DE.CM-02.1 — The physical environment shall be monitored to find potentially adverse events.

The physical environment shall be monitored to find potentially adverse events.

Control · obligation: mandatory · PDF page 140

• Group: DE.CM-02 The physical environment is monitored to find potentially adverse events

7.1.3 DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events

Read section 7.1.3 in the full text

DE.CM-03.2 — End point and network protection tools that monitor end-user behaviour for dangerous activity shall be managed.

End point and network protection tools that monitor end-user behaviour for dangerous activity shall be managed.

Control · obligation: mandatory · PDF page 142

• Group: DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events

7.2.1 DE.AE-02 Potentially adverse events are analysed to better understand associated activities

Read section 7.2.1 in the full text

DE.AE-02.2 — The organisation shall implement automated mechanisms where feasible to review and analyse detected events.

The organisation shall implement automated mechanisms where feasible to review and analyse detected events.

Control · obligation: mandatory · PDF page 148

• Group: DE.AE-02 Potentially adverse events are analysed to better understand associated activities

8.1.2 RS.MA-02 Incident reports are triaged and validated

Read section 8.1.2 in the full text

RS.MA-02.2 — Automated tools shall be used to support the investigation and impact assessment of validated cybersecurity incidents.

Automated tools shall be used to support the investigation and impact assessment of validated cybersecurity incidents.

Control · obligation: mandatory · PDF page 155

• Group: RS.MA-02 Incident reports are triaged and validated

8.2.1 RS.AN-03 Analysis is performed to establish what has taken place during an incident and the root cause of the incident

Read section 8.2.1 in the full text

RS.AN-03.1 — Each incident shall be analysed to determine what occurred and to identify its root cause.

Each incident shall be analysed to determine what occurred and to identify its root cause.

Control · obligation: mandatory · PDF page 157

• Group: RS.AN-03 Analysis is performed to establish what has taken place during an incident and the root cause of the incident