ISO/IEC 27001:2022 Controls

A.5.1 Policies for information security
Organizational Controls

Information security policy and topic-specific policies shall be defined, approved by management, published, communicated to and acknowledged by relevant personnel and relevant interested parties, and reviewed at planned intervals or when significant changes occur.

A.5.2 Information security roles and responsibilities
Organizational Controls

Information security roles and responsibilities shall be defined and allocated according to the organization needs.

A.5.3 Segregation of duties
Organizational Controls

Conflicting duties and conflicting areas of responsibility shall be segregated.

A.5.4 Management responsibilities
Organizational Controls

Management shall require all personnel to apply information security in accordance with the established information security policy, topic-specific policies and procedures of the organization.

A.5.5 Contact with authorities
Organizational Controls

The organization shall establish and maintain contact with relevant authorities.

A.5.6 Contact with special interest groups
Organizational Controls

The organization shall establish and maintain contact with special interest groups or other specialist security forums and professional associations.

A.5.7 Threat intelligence
Organizational Controls

Information relating to information security threats shall be collected and analyzed to produce threat intelligence.

A.5.8 Information security in project management
Organizational Controls

Information security shall be integrated into project management.

A.5.9 Inventory of information and other associated assets
Organizational Controls

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

A.5.10 Acceptable use of information and other associated assets
Organizational Controls

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

A.5.11 Return of assets
Organizational Controls

Personnel and other interested parties as appropriate shall return all the organization's assets in their possession upon change or termination of their employment, contract or agreement.

A.5.12 Classification of information
Organizational Controls

Information shall be classified according to the information security needs of the organization based on confidentiality, integrity, availability and relevant interested party requirements.

A.5.13 Labelling of information
Organizational Controls

An appropriate set of procedures for information labelling shall be developed and implemented in accordance with the information classification scheme adopted by the organization.

A.5.14 Information transfer
Organizational Controls

Information transfer rules, procedures, or agreements shall be in place for all types of transfer facilities within the organization and between the organization and other parties.

A.5.15 Access control
Organizational Controls

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

A.5.16 Identity management
Organizational Controls

The full life cycle of identities shall be managed.

A.5.17 Authentication information
Organizational Controls

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

A.5.18 Access rights
Organizational Controls

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

A.5.19 Information security in supplier relationships
Organizational Controls

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

A.5.20 Addressing information security within supplier agreements
Organizational Controls

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

A.5.21 Managing information security in the ICT supply chain
Organizational Controls

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

A.5.22 Monitoring, review and change management of supplier services
Organizational Controls

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

A.5.23 Information security for use of cloud services
Organizational Controls

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

A.5.24 Information security incident management planning and preparation
Organizational Controls

The organization shall plan and prepare for managing information security incidents by defining, establishing and communicating information security incident management processes, roles and responsibilities.

A.5.25 Assessment and decision on information security events
Organizational Controls

The organization shall assess information security events and decide if they are to be categorized as information security incidents.

A.5.26 Response to information security incidents
Organizational Controls

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

A.5.27 Learning from information security incidents
Organizational Controls

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

A.5.28 Collection of evidence
Organizational Controls

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

A.5.29 Information security during disruption
Organizational Controls

The organization shall plan how to maintain information security at an appropriate level during disruption.

A.5.30 ICT readiness for business continuity
Organizational Controls

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

A.5.31 Legal, statutory, regulatory and contractual requirements
Organizational Controls

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

A.5.32 Intellectual property rights
Organizational Controls

The organization shall implement appropriate procedures to protect intellectual property rights.

A.5.33 Protection of records
Organizational Controls

Records shall be protected from loss, destruction, falsification, unauthorized access and unauthorized release.

A.5.34 Privacy and protection of personal identifiable information (PII)
Organizational Controls

The organization shall identify and meet the requirements regarding the preservation of privacy and protection of PII according to applicable laws and regulations and contractual requirements.

A.5.35 Independent review of information security
Organizational Controls

The organization's approach to managing information security and its implementation including people, processes and technologies shall be reviewed independently at planned intervals, or when significant changes occur.

A.5.36 Compliance with policies, rules and standards for information security
Organizational Controls

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

A.5.37 Documented operating procedures
Organizational Controls

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

A.6.1 Screening
People Controls

Background verification checks on all candidates to become personnel shall be carried out prior to joining the organization and on an ongoing basis taking into consideration applicable laws, regulations and ethics and be proportional to the business requirements, the classification of the information to be accessed and the perceived risks.

A.6.2 Terms and conditions of employment
People Controls

The employment contractual agreements shall state the personnel's and the organization's responsibilities for information security.

A.6.3 Information security awareness, education and training
People Controls

Personnel of the organization and relevant interested parties shall receive appropriate information security awareness, education and training and regular updates of the organization's information security policy, topic-specific policies and procedures, as relevant for their job function.

A.6.4 Disciplinary process
People Controls

A disciplinary process shall be formalized and communicated to take actions against personnel and other relevant interested parties who have committed an information security policy violation.

A.6.5 Responsibilities after termination or change of employment
People Controls

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

A.6.6 Confidentiality or non-disclosure agreements
People Controls

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

A.6.7 Remote working
People Controls

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

A.6.8 Information security event reporting
People Controls

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

A.7.1 Physical security perimeters
Physical Controls

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

A.7.2 Physical entry
Physical Controls

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

A.7.3 Securing offices, rooms and facilities
Physical Controls

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

A.7.4 Physical security monitoring
Physical Controls

Premises shall be continuously monitored for unauthorized physical access.

A.7.5 Protecting against physical and environmental threats
Physical Controls

Protection against physical and environmental threats, such as natural disasters and other intentional or unintentional physical threats to infrastructure shall be designed and implemented.

A.7.6 Working in secure areas
Physical Controls

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

A.7.7 Clear desk and clear screen
Physical Controls

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

A.7.8 Equipment siting and protection
Physical Controls

Equipment shall be sited securely and protected.

A.7.9 Security of assets off-premises
Physical Controls

Off-site assets shall be protected.

A.7.10 Storage media
Physical Controls

Storage media shall be managed through their life cycle of acquisition, use, transportation and disposal in accordance with the organization's classification scheme and handling requirements.

A.7.11 Supporting utilities
Physical Controls

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

A.7.12 Cabling security
Physical Controls

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

A.7.13 Equipment maintenance
Physical Controls

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

A.7.14 Secure disposal or re-use of equipment
Physical Controls

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

A.8.1 User endpoint devices
Technological Controls

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

A.8.2 Privileged access rights
Technological Controls

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

A.8.3 Information access restriction
Technological Controls

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

A.8.4 Access to source code
Technological Controls

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

A.8.5 Secure authentication
Technological Controls

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

A.8.6 Capacity management
Technological Controls

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

A.8.7 Protection against malware
Technological Controls

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

A.8.8 Management of technical vulnerabilities
Technological Controls

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

A.8.9 Configuration management
Technological Controls

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

A.8.10 Information deletion
Technological Controls

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

A.8.11 Data masking
Technological Controls

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

A.8.12 Data leakage prevention
Technological Controls

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

A.8.13 Information backup
Technological Controls

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

A.8.14 Redundancy of information processing facilities
Technological Controls

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

A.8.15 Logging
Technological Controls

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

A.8.16 Monitoring activities
Technological Controls

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

A.8.17 Clock synchronization
Technological Controls

The clocks of information processing systems used by the organization shall be synchronized to approved time sources.

A.8.18 Use of privileged utility programs
Technological Controls

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

A.8.19 Installation of software on operational systems
Technological Controls

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

A.8.20 Networks security
Technological Controls

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

A.8.21 Security of network services
Technological Controls

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

A.8.22 Segregation of networks
Technological Controls

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

A.8.23 Web filtering
Technological Controls

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

A.8.24 Use of cryptography
Technological Controls

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

A.8.25 Secure development life cycle
Technological Controls

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

A.8.26 Application security requirements
Technological Controls

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

A.8.27 Secure system architecture and engineering principles
Technological Controls

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

A.8.28 Secure coding
Technological Controls

Secure coding principles shall be applied to software development.

A.8.29 Security testing in development and acceptance
Technological Controls

Security testing processes shall be defined and implemented in the development life cycle.

A.8.30 Outsourced development
Technological Controls

The organization shall direct, monitor and review the activities related to outsourced system development.

A.8.31 Separation of development, test and production environments
Technological Controls

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

A.8.32 Change management
Technological Controls

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

A.8.33 Test information
Technological Controls

Test information shall be appropriately selected, protected and managed.

A.8.34 Protection of information systems during audit testing
Technological Controls

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

A.10.1 Policy on the use of cryptographic controls
Cryptography (ISO 27001:2013)

A policy on the use of cryptographic controls for protection of information shall be developed and implemented. (ISO 27001:2013 reference; see A.8.24 in ISO 27001:2022)

A.10.4 Protection against malware (legacy reference)
Cryptography (ISO 27001:2013)

Detection, prevention and recovery controls to protect against malware shall be implemented, combined with appropriate user awareness. (Legacy policy reference; see A.8.7 in ISO 27001:2022)

A.11.1 Secure areas
Physical and Environmental Security (ISO 27001:2013)

Security perimeters shall be defined and used to protect areas that contain sensitive or critical information and information processing facilities. (ISO 27001:2013 reference; see A.7.1 in ISO 27001:2022)

A.11.2 Equipment
Physical and Environmental Security (ISO 27001:2013)

Equipment shall be sited and protected to reduce the risks from environmental threats and hazards, and opportunities for unauthorized access. (ISO 27001:2013 reference; see A.7.8 in ISO 27001:2022)

A.12.1 Operational procedures and responsibilities
Operations Security (ISO 27001:2013)

Operating procedures shall be documented and made available to all users who need them. (ISO 27001:2013 reference; see A.5.37 in ISO 27001:2022)

A.12.2 Protection from malware
Operations Security (ISO 27001:2013)

Detection, prevention and recovery controls to protect against malware shall be implemented, combined with appropriate user awareness. (ISO 27001:2013 reference; see A.8.7 in ISO 27001:2022)

A.12.6 Management of technical vulnerabilities
Operations Security (ISO 27001:2013)

Information about technical vulnerabilities of information systems being used shall be obtained in a timely fashion, the organization's exposure to such vulnerabilities evaluated and appropriate measures taken. (ISO 27001:2013 reference; see A.8.8 in ISO 27001:2022)

A.12.7 Information systems audit controls
Operations Security (ISO 27001:2013)

Audit requirements and activities involving verification of operational systems shall be carefully planned and agreed to minimize disruptions to business processes. (ISO 27001:2013 reference; see A.8.34 in ISO 27001:2022)

A.16.1 Management of information security incidents and improvements
Information Security Incident Management (ISO 27001:2013)

Management responsibilities and procedures shall be established to ensure a quick, effective and orderly response to information security incidents. (ISO 27001:2013 reference; see A.5.24–A.5.28 in ISO 27001:2022)

A.18.1 Compliance with legal and contractual requirements
Compliance (ISO 27001:2013)

All relevant legislative statutory, regulatory, contractual requirements and the organization's approach to meet these requirements shall be explicitly identified, documented and kept up to date for each information system and the organization. (ISO 27001:2013 reference; see A.5.31 in ISO 27001:2022)

A.18.2 Information security reviews
Compliance (ISO 27001:2013)

The organization's approach to managing information security and its implementation (e.g. control objectives, controls, policies, processes and procedures for information security) shall be reviewed independently at planned intervals or when significant changes occur. (ISO 27001:2013 reference; see A.5.35 in ISO 27001:2022)