ISO/IEC 27001:2022
Information security management systems standard. Specifies requirements for establishing, implementing, maintaining and continually improving an ISMS.
| Clause | Title | SP 800-53 Controls |
|---|---|---|
| 4.1 | Organisational context: internal and external issues | |
| 4.2 | Identifying interested parties and their requirements | |
| 4.3 | Defining the ISMS scope and boundaries | |
| 4.4 | Establishing and continually improving the ISMS | |
| 5.1 | Top management's leadership and commitment to the ISMS | |
| 5.2 | Information security policy set by top management | |
| 5.3 | Assigning ISMS roles with their responsibilities and authority | |
| 6.1 | Planning for risks and opportunities, including risk assessment | |
| 6.1.3 | Risk treatment planning and the Statement of Applicability | |
| 6.2 | Setting information security objectives with plans to reach them | |
| 6.3 | Planning changes to the ISMS | |
| 7.1 | Providing the resources the ISMS needs | |
| 7.2 | Competence of people whose work affects security | |
| 7.3 | Staff awareness of security policy and their role | |
| 7.4 | Planning ISMS communication inside and outside the organisation | |
| 7.5 | Creating and controlling documented information for the ISMS | |
| 8.1 | Planning and controlling ISMS operations, including outsourced processes | |
| 8.2 | Carrying out risk assessments regularly and for major changes | |
| 8.3 | Carrying out the risk treatment plan | |
| 9.1 | Monitoring ISMS performance and evaluating its effectiveness | |
| 9.2 | Planned internal audits of the ISMS | |
| 9.3 | Regular top management review of the ISMS | |
| 10.1 | Continual improvement of the ISMS | |
| 10.2 | Corrective action on nonconformities and their root causes | |
| A.5.1 | Setting information security policies, including topic-specific ones | |
| A.5.2 | Defining and assigning information security roles | |
| A.5.3 | Segregation of duties between conflicting roles | |
| A.5.4 | Management responsibilities: requiring staff to follow security policies | |
| A.5.5 | Staying in contact with authorities such as regulators | |
| A.5.6 | Joining special interest groups and security forums | |
| A.5.7 | Gathering and analysing threat intelligence | |
| A.5.8 | Building security into project management | |
| A.5.9 | Inventory and ownership of information and related assets | |
| A.5.10 | Acceptable use rules for information and related assets | |
| A.5.11 | Return of assets when people leave or change roles | |
| A.5.12 | Classification of information by security needs | |
| A.5.13 | Labelling of information to show its classification | |
| A.5.14 | Rules and agreements for information transfer | |
| A.5.15 | Access control policy and rules | |
| A.5.16 | Identity management from creation to removal | |
| A.5.17 | Issuing and managing authentication information such as passwords | |
| A.5.18 | Managing access rights, including regular reviews | |
| A.5.19 | Managing security risks in supplier relationships | |
| A.5.20 | Security requirements in supplier agreements | |
| A.5.21 | Managing ICT supply chain security risks | |
| A.5.22 | Monitoring supplier services and managing their changes | |
| A.5.23 | Security of cloud services from adoption to exit | |
| A.5.24 | Setting up incident management plans and roles | |
| A.5.25 | Assessing whether security events are incidents | |
| A.5.26 | Incident response following documented procedures | |
| A.5.27 | Lessons learned from security incidents | |
| A.5.28 | Collecting and preserving evidence of security events | |
| A.5.29 | Keeping security in place during disruption | |
| A.5.30 | ICT readiness to support business continuity | |
| A.5.31 | Identifying legal and regulatory requirements, including contractual ones | |
| A.5.32 | Intellectual property rights and software licence compliance | |
| A.5.33 | Protection of records against loss and misuse | |
| A.5.34 | Protecting PII and meeting privacy requirements | |
| A.5.35 | Independent review of how security is managed | |
| A.5.36 | Regularly checking compliance with security policies and standards | |
| A.5.37 | Documented operating procedures for IT systems | |
| A.6.1 | Background screening before joining and during employment | |
| A.6.2 | Security responsibilities in employment contracts | |
| A.6.3 | Security awareness training and education for staff | |
| A.6.4 | Disciplinary process for security policy breaches | |
| A.6.5 | Security duties that continue after termination or role change | |
| A.6.6 | Non-disclosure agreements to protect confidential information | |
| A.6.7 | Protecting information during remote working | |
| A.6.8 | Security event reporting by staff through agreed channels | |
| A.7.1 | Physical security perimeters around sensitive areas | |
| A.7.2 | Controlling physical entry to secure areas | |
| A.7.3 | Physical security of offices and other facilities | |
| A.7.4 | Physical security monitoring of premises, such as CCTV | |
| A.7.5 | Protecting sites from physical and environmental hazards | |
| A.7.6 | Rules for work inside secure areas | |
| A.7.7 | Rules for a clear desk and a clear screen | |
| A.7.8 | Siting equipment securely and protecting it from hazards | |
| A.7.9 | Protecting assets used off-premises, such as laptops | |
| A.7.10 | Managing storage media from acquisition to disposal | |
| A.7.11 | Reliable supporting utilities, such as power and cooling | |
| A.7.12 | Security of power and data cabling | |
| A.7.13 | Secure and timely equipment maintenance | |
| A.7.14 | Removing data and software before equipment disposal or reuse | |
| A.8.1 | Protecting information on user endpoint devices | |
| A.8.2 | Limiting and controlling privileged access rights | |
| A.8.3 | Restricting access to information under access control rules | |
| A.8.4 | Controlling who can read and change source code | |
| A.8.5 | Secure authentication methods, such as multi-factor sign-in | |
| A.8.6 | Capacity management to meet current and future demand | |
| A.8.7 | Malware protection backed by user awareness | |
| A.8.8 | Technical vulnerability management, including patching | |
| A.8.9 | Secure configuration management for systems and networks | |
| A.8.10 | Deleting information once the need for it ends | |
| A.8.11 | Data masking, such as pseudonymisation and anonymisation | |
| A.8.12 | Data leakage prevention for sensitive information | |
| A.8.13 | Information backup with regular restore tests | |
| A.8.14 | Redundancy in IT systems to keep services available | |
| A.8.15 | Event logging, with logs kept safe and reviewed | |
| A.8.16 | Monitoring networks and systems for unusual behaviour | |
| A.8.17 | Clock synchronisation to a trusted time source | |
| A.8.18 | Restricting privileged utility programs able to bypass controls | |
| A.8.19 | Controlling what software is installed on operational systems | |
| A.8.20 | Network security and management of network devices | |
| A.8.21 | Security features and service levels for network services | |
| A.8.22 | Network segregation into separate security zones | |
| A.8.23 | Web filtering to block harmful websites | |
| A.8.24 | Using cryptography, including encryption and key management | |
| A.8.25 | Security built into the development life cycle | |
| A.8.26 | Application security requirements when building or buying software | |
| A.8.27 | Applying secure engineering principles to system architecture | |
| A.8.28 | Secure coding practices in software development | |
| A.8.29 | Security and acceptance testing of new or changed systems | |
| A.8.30 | Overseeing outsourced development from contract to acceptance | |
| A.8.31 | Separating development and test environments from production | |
| A.8.32 | Change management for IT systems and services | |
| A.8.33 | Choosing and protecting test data | |
| A.8.34 | Planning audit testing to protect live systems | |