ISO 27001 Annex A Controls

ISO 27001:2022 includes 93 controls across 4 themes. Here is what each control requires, with implementation priority guidance.

Updated 26 March 2026

93

Total controls in Annex A

37

Organisational controls (A.5)

8

People controls (A.6)

34

Technological controls (A.8)

Not all controls are mandatory

ISO 27001 does not require every Annex A control to be implemented. You must assess which controls are applicable to your organisation based on your risk assessment and document your justification in the Statement of Applicability (SoA). Controls that are not applicable must still be listed in the SoA with a justification for exclusion.

A5

Organisational Controls

37 controls

Policies, procedures, roles, and governance that define how the organisation manages information security.

5.1

Policies for information security

Mandatory

A set of topic-specific information security policies must be defined, approved by management, published, communicated, and reviewed regularly.

5.2

Information security roles and responsibilities

Mandatory

Roles and responsibilities for information security must be allocated and communicated.

5.3

Segregation of duties

High

Conflicting duties and areas of responsibility must be segregated to reduce opportunities for unauthorised or unintentional modification or misuse of assets.

5.4

Management responsibilities

Mandatory

Management must require all personnel to apply information security in accordance with the established policies and procedures.

5.5

Contact with authorities

High

Appropriate contacts with relevant authorities (regulators, law enforcement, fire, NCSC) must be maintained.

5.6

Contact with special interest groups

Medium

Appropriate contacts with special interest groups or specialist security forums must be maintained.

5.7

Threat intelligence

High

Information relating to information security threats must be collected and analysed to produce threat intelligence.

5.8

Information security in project management

High

Information security must be integrated into project management throughout the project lifecycle.

5.9

Inventory of information and other associated assets

Mandatory

An inventory of information and other associated assets, including owners, must be developed and maintained.

5.10

Acceptable use of information and associated assets

Mandatory

Rules for acceptable use and procedures for handling information and associated assets must be identified, documented, and implemented.

5.11

Return of assets

High

Personnel and external party users must return all organisational assets in their possession upon change or termination of employment, contract, or agreement.

5.12

Classification of information

Mandatory

Information must be classified according to the information security needs of the organisation based on confidentiality, integrity, availability, and relevant stakeholder requirements.

5.13

Labelling of information

High

An appropriate set of procedures for information labelling must be developed and implemented in accordance with the information classification scheme.

5.14

Information transfer

High

Information transfer rules, procedures, or agreements must be in place for all transfer facilities within the organisation and between the organisation and other parties.

5.15

Access control

Mandatory

Rules to control physical and logical access to information and other associated assets must be established and implemented based on business and information security requirements.

5.16

Identity management

Mandatory

The full lifecycle of identities must be managed.

5.17

Authentication information

Mandatory

Allocation and management of authentication information must be controlled by a management process, including advising personnel on appropriate handling of authentication information.

5.18

Access rights

Mandatory

Access rights to information and other associated assets must be provisioned, reviewed, modified, and removed in accordance with the organisation's topic-specific policy on and rules for access control.

5.19

Information security in supplier relationships

High

Processes and procedures must be defined and implemented to manage the information security risks associated with the use of supplier's products or services.

5.20

Addressing information security within supplier agreements

High

Relevant information security requirements must be established and agreed with each supplier based on the type of supplier relationship.

5.21

Managing information security in the ICT supply chain

High

Processes and procedures must be defined and implemented to manage information security risks associated with the ICT products and services supply chain.

5.22

Monitoring, review and change management of supplier services

High

The organisation must regularly monitor, review, evaluate, and manage change in supplier information security practices and service delivery.

5.23

Information security for use of cloud services

High

Processes for acquisition, use, management, and exit from cloud services must be established in accordance with the organisation's information security requirements.

5.24

Information security incident management planning and preparation

Mandatory

The organisation must plan and prepare for managing information security incidents by defining, establishing, and communicating processes, roles, and responsibilities.

5.25

Assessment and decision on information security events

High

The organisation must assess information security events and decide if they are to be categorised as information security incidents.

5.26

Response to information security incidents

Mandatory

Information security incidents must be responded to in accordance with the documented procedures.

5.27

Learning from information security incidents

High

Knowledge gained from information security incidents must be used to strengthen and improve the information security controls.

5.28

Collection of evidence

High

The organisation must establish and implement procedures for the identification, collection, acquisition, and preservation of evidence related to information security events.

5.29

Information security during disruption

High

The organisation must plan how to maintain information security at an appropriate level during disruption.

5.30

ICT readiness for business continuity

High

ICT readiness must be planned, implemented, maintained, and tested based on business continuity objectives and ICT continuity requirements.

5.31

Legal, statutory, regulatory and contractual requirements

Mandatory

Legal, statutory, regulatory, and contractual requirements relevant to information security and the organisation's approach to meet these requirements must be explicitly identified, documented, and kept up to date.

5.32

Intellectual property rights

High

The organisation must implement appropriate procedures to protect intellectual property rights.

5.33

Protection of records

High

Records must be protected from loss, destruction, falsification, unauthorised access, and unauthorised release.

5.34

Privacy and protection of PII

High

The organisation must identify and meet the requirements regarding the preservation of privacy and protection of PII according to applicable laws and regulations.

5.35

Independent review of information security

High

The organisation's approach to managing information security and its implementation must be reviewed independently at planned intervals or when significant changes occur.

5.36

Compliance with policies, rules and standards for information security

Mandatory

Compliance with the organisation's information security policy, topic-specific policies, rules, and standards must be regularly reviewed.

5.37

Documented operating procedures

High

Operating procedures for information processing facilities must be documented and made available to personnel who need them.

A6

People Controls

8 controls

Controls relating to human resources, from pre-employment screening through to off-boarding.

6.1

Screening

High

Background verification checks on all candidates for employment must be carried out prior to joining the organisation and on an ongoing basis.

6.2

Terms and conditions of employment

Mandatory

Employment contracts must state responsibilities for information security, including the employee's and the organisation's responsibilities.

6.3

Information security awareness, education and training

Mandatory

All personnel and, where relevant, contractors must receive appropriate information security awareness education and training, and regular updates of the organisation's policies and procedures.

6.4

Disciplinary process

High

A disciplinary process must be formalised and communicated to take action against personnel and other interested parties who have committed an information security violation.

6.5

Responsibilities after termination or change of employment

High

Information security responsibilities and duties that remain valid after termination or change of employment must be defined, enforced, and communicated to relevant personnel and other interested parties.

6.6

Confidentiality or non-disclosure agreements

High

Confidentiality or non-disclosure agreements reflecting the organisation's needs for the protection of information must be identified, regularly reviewed, documented, and signed by personnel and other relevant interested parties.

6.7

Remote working

High

Security measures must be implemented when personnel are working remotely to protect information accessed, processed, or stored outside the organisation's premises.

6.8

Information security event reporting

Mandatory

The organisation must provide a mechanism for personnel to report observed or suspected information security events through appropriate channels in a timely manner.

A7

Physical Controls

14 controls

Controls to protect physical spaces, equipment, and infrastructure from unauthorised access, damage, and interference.

7.1

Physical security perimeters

High

Security perimeters must be defined and used to protect areas that contain information and other associated assets.

7.2

Physical entry

High

Secure areas must be protected by appropriate entry controls and access points.

7.3

Securing offices, rooms and facilities

High

Physical security for offices, rooms, and facilities must be designed and implemented.

7.4

Physical security monitoring

Medium

Premises must be continuously monitored for unauthorised physical access.

7.5

Protecting against physical and environmental threats

High

Protection against physical and environmental threats, such as natural disasters, must be designed and implemented.

7.6

Working in secure areas

Medium

Security measures for working in secure areas must be designed and implemented.

7.7

Clear desk and clear screen

Medium

Clear desk rules for papers and removable storage media and clear screen rules for information processing facilities must be defined and appropriately enforced.

7.8

Equipment siting and protection

High

Equipment must be sited securely and protected.

7.9

Security of assets off-premises

High

Off-site assets must be protected.

7.10

Storage media

High

Storage media must be managed through their lifecycle of acquisition, use, transportation, and disposal in accordance with the organisation's classification scheme and handling requirements.

7.11

Supporting utilities

High

Information processing facilities must be protected from power failures and other disruptions caused by failures in supporting utilities.

7.12

Cabling security

Medium

Cables carrying power, data, or supporting information services must be protected from interception, interference, or damage.

7.13

Equipment maintenance

Medium

Equipment must be maintained correctly to ensure availability, integrity, and confidentiality of information.

7.14

Secure disposal or re-use of equipment

High

Items of equipment containing storage media must be verified to ensure that any sensitive data and licensed software has been removed or securely overwritten prior to disposal or re-use.

A8

Technological Controls

34 controls

Technical controls covering endpoint security, access management, encryption, vulnerability management, and logging.

8.1

User endpoint devices

Mandatory

Information stored on, processed by, or accessible via user endpoint devices must be protected.

8.2

Privileged access rights

Mandatory

The allocation and use of privileged access rights must be restricted and managed.

8.3

Information access restriction

Mandatory

Access to information and other associated assets must be restricted in accordance with the established topic-specific policy on access control.

8.4

Access to source code

High

Read and write access to source code, development tools, and software libraries must be appropriately managed.

8.5

Secure authentication

Mandatory

Secure authentication technologies and procedures must be implemented based on information access restrictions and the topic-specific policy on access control.

8.6

Capacity management

Medium

The use of resources must be monitored and adjusted in line with current and expected capacity requirements.

8.7

Protection against malware

Mandatory

Protection against malware must be implemented and supported by appropriate user awareness.

8.8

Management of technical vulnerabilities

Mandatory

Information about technical vulnerabilities of information systems in use must be obtained, the organisation's exposure to such vulnerabilities must be evaluated, and appropriate measures must be taken.

8.9

Configuration management

High

Configurations, including security configurations, of hardware, software, services, and networks must be established, documented, implemented, monitored, and reviewed.

8.10

Information deletion

High

Information stored in information systems, devices, or in any other storage media must be deleted when no longer required.

8.11

Data masking

Medium

Data masking must be used in accordance with the organisation's topic-specific policy on access control and other related topic-specific policies, and business requirements, taking applicable legislation into consideration.

8.12

Data leakage prevention

High

Data leakage prevention measures must be applied to systems, networks, and any other devices that process, store, or transmit sensitive information.

8.13

Information backup

Mandatory

Backup copies of information, software, and systems must be maintained and regularly tested in accordance with the agreed topic-specific policy on backup.

8.14

Redundancy of information processing facilities

High

Information processing facilities must be implemented with redundancy sufficient to meet availability requirements.

8.15

Logging

Mandatory

Logs that record activities, exceptions, faults, and other relevant events must be produced, stored, protected, and analysed.

8.16

Monitoring activities

High

Networks, systems, and applications must be monitored for anomalous behaviour and appropriate actions taken to evaluate potential information security incidents.

8.17

Clock synchronisation

Medium

The clocks of information processing systems used by the organisation must be synchronised to approved time sources.

8.18

Use of privileged utility programs

High

The use of utility programs that might be capable of overriding system and application controls must be restricted and tightly controlled.

8.19

Installation of software on operational systems

High

Procedures and measures must be implemented to securely manage software installation on operational systems.

8.20

Networks security

Mandatory

Networks and network devices must be secured, managed, and controlled to protect information in systems and applications.

8.21

Security of network services

High

Security mechanisms, service levels, and service requirements of network services must be identified, implemented, and monitored.

8.22

Segregation of networks

High

Groups of information services, users, and information systems must be segregated in the organisation's networks.

8.23

Web filtering

Medium

Access to external websites must be managed to reduce exposure to malicious content.

8.24

Use of cryptography

Mandatory

Rules for the effective use of cryptography, including cryptographic key management, must be defined and implemented.

8.25

Secure development lifecycle

High

Rules for the secure development of software and systems must be established and applied.

8.26

Application security requirements

High

Information security requirements must be identified, specified, and approved when developing or acquiring applications.

8.27

Secure system architecture and engineering principles

High

Principles for engineering secure systems must be established, documented, maintained, and applied to any information system development or integration activities.

8.28

Secure coding

High

Secure coding principles must be applied to software development.

8.29

Security testing in development and acceptance

High

Security testing processes must be defined and implemented in the development lifecycle.

8.30

Outsourced development

High

The organisation must direct, monitor, and review the activities related to outsourced system development.

8.31

Separation of development, test and production environments

High

Development, testing, and production environments must be separated and secured.

8.32

Change management

Mandatory

Changes to information processing facilities and information systems must be subject to change management procedures.

8.33

Test information

High

Test information must be appropriately selected, protected, and managed.

8.34

Protection of information systems during audit testing

Medium

Audit tests and other assurance activities involving assessment of operational systems must be planned and agreed between the tester and appropriate management.

What Changed in ISO 27001:2022?

ISO 27001:2022 (published October 2022) replaced the 2013 version. The main changes to Annex A controls:

New controls (11 added)

  • 5.7 Threat intelligence
  • 5.23 Information security for use of cloud services
  • 5.30 ICT readiness for business continuity
  • 7.4 Physical security monitoring
  • 8.9 Configuration management
  • 8.10 Information deletion
  • 8.11 Data masking
  • 8.12 Data leakage prevention
  • 8.16 Monitoring activities
  • 8.23 Web filtering
  • 8.28 Secure coding

Structural changes

  • Control count reduced from 114 to 93 (merging and consolidation)
  • 14 control clauses collapsed into 4 themes
  • New attributes added to each control (security concept, operational capability, etc.)
  • Transition deadline for existing 2013 certificates: October 2025
  • New certifications must use ISO 27001:2022 standard

Ready to implement these controls?

Calculate your implementation cost or book a free scoping call to assess which controls apply to your organisation.