Understanding ISO 27001:2022 Annex A Controls (Security Measures for Data Protection)
The worldwide standard for information security is ISO 27001. Organizations must assess information security threats in accordance with their framework and choose the right measures to address them.
The Standard’s clauses 4 – 10 provide the more general specifications for an ISMS (information security management system). However, they don’t specify individual controls.
How Annex A works?
The component of the standard that provides the goals and controls for information security management systems (ISMS) is referred to as Annex A in ISO/IEC 27001: 2022. An extensive list of security measures that may be implemented by organisations to handle different information security needs and threats is provided in Annex A. These controls are divided into 14 domains, each of which focuses on a specific aspects of information security.
For organizations looking to create, implement, maintain, and continuously enhance their ISMS in compliance with ISO/IEC 27001 criteria, the controls listed in Annex A provide a framework of reference. Organizations may successfully manage information security risks, safeguard sensitive information assets, and prove compliance with relevant legal, regulatory, and contractual obligations by putting the procedures outlined in Annex A into practice.
Annex A contains a list of 93 security controls, grouped into 4 themes:
- Organizational
- People
- Physical
- Technological
What the Annex A controls are?
1. Organisational controls (37 controls)
Organizational controls are all of the formal procedures and guidelines that a company uses to manage its information security. These controls, which are described in the standard’s Annex A, cover a range of information security management topics, such as establishing roles and duties inside the company and creating policies and procedures.
Organisations may create strong frameworks for protecting their information assets, reducing risks, and maintaining the availability, confidentiality, and integrity of sensitive data by following organizational controls.
Organizational Controls based on ISO27001 : 2022 are given below:
| Annex’s | CONTROLS | DESCRIPTION |
| 5.1 | Policies for information security | Information security policy and topic-specific policies should be defined, approved by management, published, communicated to and acknowledged by relevant personnel and relevant interested parties, and reviewed at planned intervals and if significant changes occur – |
| 5.2 | Information security roles and responsibilities | Information security roles and responsibilities should be defined and allocated according to the organization needs. |
| 5.3 | Segregation of duties | Conflicting duties and conflicting areas of responsibility should be segregated. |
| 5.4 | Management responsibilities | Management should require all personnel to apply information security in accordance with the established information security policy, topic-specific policies and procedures of the organization. |
| 5.5 | Contact with authorities | The organization should establish and maintain contact with relevant authorities |
| 5.6 | Contact with special interest groups | The organization should establish and maintain contact with special interest groups or other specialist security forums and professional associations |
| 5.7 | Threat intelligence | Information relating to information security threats should be collected and analysed to produce threat intelligence. |
| 5.8 | Information security in project management | Information security should be integrated into project management |
| 5.9 | Inventory of information and other associated assets | An inventory of information and other associated assets, including owners, should be developed and maintained. |
| 5.10 | Acceptable use of information and other associated assets | Rules for the acceptable use and procedures for handling information and other associated assets should be identified, documented and implemented |
| 5.11 | Return of assets | Personnel and other interested parties as appropriate should return all the organization’s assets in their possession upon change or termination of their employment, contract or agreement |
| 5.12 | Classification of information | Information should be classified according to the information security needs of the organization based on confidentiality, integrity, availability and relevant interested party requirements |
| 5.13 | Labelling of information | An appropriate set of procedures for information labelling should be developed and implemented in accordance with the information classification scheme adopted by the organization |
| 5.14 | Information transfer | Information transfer rules, procedures, or agreements should be in place for all types of transfer facilities within the organization and between the organization and other parties |
| 5.15 | Access control | Rules to control physical and logical access to information and other associated assets should be established and implemented based on business and information security requirements |
| 5.16 | Identity management | The full life cycle of identities should be managed. |
| 5.17 | Authentication information | Allocation and management of authentication information should be controlled by a management process, including advising personnel on the appropriate handling of authentication information |
| 5.18 | Access rights | Access rights to information and other associated assets should be provisioned, reviewed, modified and removed in accordance with the organization’s topic-specific policy on and rules for access control |
| 5.19 | Information security in supplier relationships | Processes and procedures should 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 | Relevant information security requirements should be established and agreed with each supplier based on the type of supplier relationship. |
| 5.21 | Managing information security in the ICT supply chain | Processes and procedures should be defined and implemented to manage the information security risks associated with the ICT products and services supply chain |
| 5.22 | Monitoring, review and change management of supplier services | The organization should regularly monitor, review, evaluate and manage change in supplier information security practices and service delivery. |
| 5.23 | Information security for use of cloud services | Processes for acquisition, use, management and exit from cloud services should be established in accordance with the organization’s information security requirements. |
| 5.24 | Information security incident management planning and preparation | The organization should plan and prepare for managing information security incidents by defining, establishing and communicating information security incident management processes, roles and responsibilities. |
| 5.25 | Assessment and decision on information security events | The organization should assess information security events and decide if they are to be categorized as information security incidents. |
| 5.26 | Response to information security incidents | Information security incidents should be responded to in accordance with the documented procedures. |
| 5.27 | Learning from information security incidents | Knowledge gained from information security incidents should be used to strengthen and improve the information security controls |
| 5.28 | Collection of evidence | The organization should establish and implement procedures for the identification, collection, acquisition and preservation of evidence related to information security events. |
| 5.29 | Information security during disruption | The organization should plan how to maintain information security at an appropriate level during disruption. |
| 5.30 | ICT readiness for business continuity | ICT readiness should be planned, implemented, maintained and tested based on business continuity objectives and ICT continuity requirements |
| 5.31 | Legal, statutory, regulatory and contractual requirements | Legal, statutory, regulatory and contractual requirements relevant to information security and the organization’s approach to meet these requirements should be identified, documented and kept up to date. |
| 5.32 | Intellectual property rights | The organization should implement appropriate procedures to protect intellectual property rights |
| 5.33 | Protection of records | Records should be protected from loss, destruction, falsification, unauthorized access and unauthorized release. |
| 5.34 | Privacy and protection of PII | The organization should identify and meet the requirements regarding the preservation of privacy and protection of PII according to applicable laws and regulations and contractual requirements |
| 5.35 | Independent review of information security | The organization’s approach to managing information security and its implementation including people, processes and technologies should be reviewed independently at planned intervals, or when significant changes occur. |
| 5.36 | Compliance with policies, rules and standards for information security | Compliance with the organization’s information security policy, topic-specific policies, rules and standards should be regularly reviewed. |
| 5.37 | Documented operating procedures | Operating procedures for information processing facilities should be documented and made available to personnel who need them. |
2. PEOPLE CONTROL (8 CONTROLS)
| Annex’s | CONTROLS | DESCRIPTION |
| 6.1 | Screening | Background verification checks on all candidates to become personnel should 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. |
| 6.2 | Terms and conditions of employment | The employment contractual agreements should state the personnel’s and the organization’s responsibilities for information security |
| 6.3 | Information security awareness, education and training | Personnel of the organization and relevant interested parties should 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 |
| 6.4 | Disciplinary process | A disciplinary process should be formalized and communicated to take actions against personnel and other relevant interested parties who have committed an information security policy violation. |
| 6.5 | Responsibilities after termination or change of employment | Information security responsibilities and duties that remain valid after termination or change of employment should be defined, enforced and communicated to relevant personnel and other interested parties |
| 6.6 | Confidentiality or non-disclosure agreements | Confidentiality or non-disclosure agreements reflecting the organization’s needs for the protection of information should be identified, documented, regularly reviewed and signed by personnel and other relevant interested parties. |
| 6.7 | Remote working | Security measures should be implemented when personnel are working remotely to protect information accessed, processed or stored outside the organization’s premises |
| 6.8 | Information security event reporting | The organization should provide a mechanism for personnel to report observed or suspected information security events through appropriate channels in a timely manner. |
3. PHYSICAL CONTROLS
| Annex’s | CONTROLS | DESCRIPTION |
| 7.1 | Physical security perimeters | Security perimeters should be defined and used to protect areas that contain information and other associated assets |
| 7.2 | Physical entry | Secure areas should be protected by appropriate entry controls and access points |
| 7.3 | Securing offices, rooms and facilities | Physical security for offices, rooms and facilities should be designed and implemented. |
| 7.4 | Physical security monitoring | Premises should be continuously monitored for unauthorized physical access. |
| 7.5 | Protecting against physical and environmental threats | Protection against physical and environmental threats, such as natural disasters and other intentional or unintentional physical threats to infrastructure should be designed and implemented |
| 7.6 | Working in secure areas | Security measures for working in secure areas should be designed and implemented. |
| 7.7 | Clear desk and clear screen | Clear desk rules for papers and removable storage media and clear screen rules for information processing facilities should be defined and appropriately enforced |
| 7.8 | Equipment siting and protection | Equipment should be sited securely and protected |
| 7.9 | Security of assets off-premises | Off-site assets should be protected. |
| 7.10 | Storage media | Storage media should be managed through their life cycle of acquisition, use, transportation and disposal in accordance with the organization’s classification scheme and handling requirements. |
| 7.11 | Supporting utilities | Information processing facilities should be protected from power failures and other disruptions caused by failures in supporting utilities |
| 7.12 | Cabling security | Cables carrying power, data or supporting information services should be protected from interception, interference or damage. |
| 7.13 | Equipment maintenance | Equipment should be maintained correctly to ensure availability, integrity and confidentiality of information |
| 7.14 | Secure disposal or re-use of equipment | Items of equipment containing storage media should be verified to ensure that any sensitive data and licensed software has been removed or securely overwritten prior to disposal or re-use. |
4. Technological controls
| Annex’s | CONTROLS | DESCRIPTION |
| 8.1 | User endpoint devices | Information stored on, processed by or accessible via user endpoint devices should be protected. |
| 8.2 | Privileged access rights | The allocation and use of privileged access rights should be restricted and managed. |
| 8.3 | Information access restriction | Access to information and other associated assets should be restricted in accordance with the established topic-specific policy on access control. |
| 8.4 | Access to source code | Read and write access to source code, development tools and software libraries should be appropriately managed. |
| 8.5 | Secure authentication | Secure authentication technologies and procedures should be implemented based on information access restrictions and the topic-specific policy on access control. |
| 8.6 | Capacity management | The use of resources should be monitored and adjusted in line with current and expected capacity requirements. |
| 8.7 | Protection against malware | Protection against malware should be implemented and supported by appropriate user awareness. |
| 8.8 | Management of technical vulnerabilities | Information about technical vulnerabilities of information systems in use should be obtained, the organization’s exposure to such vulnerabilities should be evaluated and appropriate measures should be taken. |
| 8.9 | Configuration management | Configurations, including security configurations, of hardware, software, services and networks shall be established, documented, implemented, monitored and reviewed. |
| 8.10 | Information deletion | Information stored in information systems, devices or in any other storage media should be deleted when no longer required |
| 8.11 | Data masking | 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. |
| 8.12 | Data leakage prevention | Data leakage prevention measures shall be applied to systems, networks and any other devices that process, store or transmit sensitive information |
| 8.13 | Information Backup | Backup copies of information, software and systems shall be maintained and regularly tested in accordance with the agreed topic-specific policy on backup. |
| 8.14 | Redundancy of information processing facilities | Information processing facilities shall be implemented with redundancy sufficient to meet availability requirements. |
| 8.15 | Logging | Logs that record activities, exceptions, faults and other relevant events shall be produced, stored, protected and analyzed. |
| 8.16 | Monitoring activities | Networks, systems and applications shall be monitors for anomalous behavior and appropriate actions taken to evaluate potential information security incidents. |
| 8.17 | Clock synchronization | The clocks of information processing systems used by the organization should be synchronized to approved time sources. |
| 8.18 | Use of privileged utility programs | The use of utility programs that can be capable of overriding system and application controls should be restricted and tightly controlled. |
| 8.19 | Installation of software on operational systems | Procedures and measures should be implemented to securely manage software installation on operational systems. |
| 8.20 | Networks security | Networks and network devices should be secured, managed and controlled to protect information in systems and applications |
| 8.21 | Security of network services | Security mechanisms, service levels and service requirements of network services should be identified, implemented and monitored. |
| 8.22 | Segregation of networks | Groups of information services, users and information systems should be segregated in the organization’s networks |
| 8.23 | Web filtering | Access to external websites should be managed to reduce exposure to malicious content |
| 8.24 | Use of cryptography | Rules for the effective use of cryptography, including cryptographic key management, should be defined and implemented. |
| 8.25 | Secure development life cycle | Rules for the secure development of software and systems should be established and applied. |
| 8.26 | Application security requirements | Information security requirements should be identified, specified and approved when developing or acquiring applications. |
| 8.27 | Secure system architecture and engineering principles | Principles for engineering secure systems should be established, documented, maintained and applied to any information system development activities |
| 8.28 | Secure coding | Secure coding principles should be applied to software development. |
| 8.29 | Security testing in development and acceptance | Security testing processes should be defined and implemented in the development life cycle |
| 8.30 | Outsourced development | The organization should direct, monitor and review the activities related to outsourced system development |
| 8.31 | Separation of development, test and production environments | Development, testing and production environments should be separated and secured. |
| 8.32 | Change management | Changes to information processing facilities and information systems should be subject to change management procedures. |
| 8.33 | Test information | Test information should be appropriately selected, protected and managed |
| 8.34 | Protection of information systems during audit testing | Audit tests and other assurance activities involving assessment of operational systems should be planned and agreed between the tester and appropriate management |
How to select controls from Annex A?
Although they serve as a foundation for an efficient ISMS, the restrictions in Annex A should not be taken literally.
Your risk assessment informs the information security controls you choose. After that, you check them against Annex A to make sure all of your risks are handled.
Annex A controls that are not relevant to your company might be left out. Nonetheless, any exclusions in your SoA (Statement of Applicability) must be justified.
What is the Statement of Applicability?
An important document that describes the information security controls chosen by an organization to manage risks found in its Information Security Management System (ISMS) is the Statement of Applicability (SoA) in ISO/IEC 27001.
It outlines the ISMS’s scope, lists the controls selected from Annex A of the standard, explains why those controls were chosen, and links those controls to certain information security threats.
The statement of assurance (SoA) functions as a thorough guide for interested parties, showcasing the company’s dedication to efficient information security management and guaranteeing adherence to ISO/IEC 27001 regulations.
For more such informtion on ISO 27001 related topics follow us on –
Leave a Reply