- See ISO 27002:2022 Control 8.29 for more information.
- See ISO 27001:2013 Annex A 14.2.8 for more information.
- See ISO 27001:2013 Annex A 14.2.9 for more information.
Ensuring Secure Development: ISO 27001 Annex A 8.29 Security Testing Explained
Cyber criminals are continually devising novel methods and enhancing their tactics to breach corporate networks and acquire access to confidential data.
Cyber criminals could exploit a flaw connected to the authentication process in the source code to breach networks. Additionally, they may try and persuade end-users on the client side to do things that would allow them to gain access to data, infiltrate networks, or execute ransomware attacks.
If an application, software or IT system is deployed with vulnerabilities, this would put sensitive information at risk of being compromised.
Organisations ought to set up and execute an appropriate security testing process in order to identify and address any vulnerabilities in IT systems before they are deployed into the real world.
Purpose of ISO 27001:2022 Annex A 8.29
ISO 27001:2022 Annex A Control 8.29 allows organisations to ensure that all security requirements are met when new applications, databases, software, or code are implemented. This is done by creating and following a thorough security testing process.
Organisations can identify and remove potential weaknesses in their code, networks, servers, applications, and other IT systems prior to implementation in the real world.
Ownership of Annex A 8.29
The Information Security Officer should ensure that ISO 27001:2022 Annex A Control 8.29 is met, requiring the establishment, maintenance and implementation of a security testing procedure that covers all new information systems, regardless of whether they are created internally or by third parties.
Get an 81% headstart
We've done the hard work for you, giving you an 81% Headstart from the moment you log on.
All you have to do is fill in the blanks.
General Guidance on ISO 27001:2022 Annex A 8.29 Compliance
Organisations should incorporate security testing into the testing process for all systems, guaranteeing that all new information systems, as well as their new/updated versions, satisfy information security requirements when they are in the production environment.
ISO 27001:2022 Annex A Control 8.29 outlines three elements as essential components of security testing:
- Ensure security through user authentication in accordance with ISO 27001:2022 Annex A 8.5, access restriction in accordance with ISO 27001:2022 Annex A 8.3, and cryptography as per ISO 27001:2022 Annex A 8.24.
- Ensure that code is securely written in adherence to the ISO 27001:2022 Annex A 8.28.
- Ensure configurations meet the requirements outlined in Annex A 8.9, 8.20, and 8.22, which may involve firewalls and operating systems.
What Should a Test Plan Include?
When devising security testing plans, organisations should consider the urgency and character of the information system involved.
This security testing plan should incorporate the following elements:
- Form a comprehensive agenda for the undertakings and the tests to be undertaken.
- Expected outcomes when certain conditions are met include both inputs and outputs.
- Criteria for assessing the outcomes must be established.
- Once the results have been obtained, decisions as to what action should be taken can be made.
In-House Development
The in-house development team ought to conduct the initial security testing to guarantee the IT system adheres to security specifications.
A first round of testing should be carried out, followed by independent acceptance testing in line with ISO 27001:2022 Annex A 5.8.
Regarding in-house development, the following should be taken into account:
- Conducting code reviews to identify and address security issues, encompassing anticipated inputs and situations.
- Performing vulnerability scans in order to identify insecure settings and other potential weaknesses.
- Performing penetration tests to identify weak coding and design.
Outsourcing
Organisations ought to adhere to a rigorous acquisition procedure when they delegate development or purchase IT elements from external sources.
Organisations should enter into a contract with their suppliers that meets the information security criteria laid out in ISO 27001:2022 Annex A 5.20.
Organisations should guarantee that the goods and services they acquire are in line with the security standards for information security.
Supplementary Guidance on ISO 27001:2022 Annex A 8.29
Organisations can generate several test environments to undertake a range of tests, including functional, non-functional, and performance ones. They can create virtual test environments, configure them to test IT systems in different operational settings, and refine them accordingly.
Annex A 8.29 emphasises the need for effective security testing, which necessitates organisations to test and oversee the testing environments, tools, and technologies.
Organisations should consider the level of sensitivity and importance when deciding how many layers of meta-testing to employ.
Compliance doesn't have to be complicated.
We've done the hard work for you, giving you an 81% Headstart from the moment you log on.
All you have to do is fill in the blanks.
Changes and Differences from ISO 27001:2013
ISO 27001:2022 Annex A 8.29 replaces ISO 27001:2013 Annex A 14.2.8 and 14.2.9 in the newest revision.
Structural Changes
ISO 27001:2022 consolidates secure testing into one control, as opposed to ISO 27001:2013, which referred to secure testing in two different controls; System Security Testing (Annex A 14.2.8) and System Acceptance Testing (Annex A 14.2.9).
ISO 27001:2022 Annex A 8.29 Brings More Comprehensive Requirements
In contrast to ISO 27001:2013, the ISO 27001:2022 revision contains more comprehensive requirements and advice on:
- A security testing plan that should include a variety of elements.
- Criteria for assessing security when developing IT systems in-house.
- What should be included in the security testing process.
- Utilising multiple test environments is essential. It ensures thoroughness and accuracy in the process.
ISO 27001:2013 Was More Detailed in Relation to Acceptance Testing
Contrary to ISO 27001:2022, ISO 27001:2013 was more detailed regarding system acceptance testing. It included security testing for incoming components and the utilisation of automated tools.
Table of All ISO 27001:2022 Annex A Controls
In the table below you’ll find more information on each individual ISO 27001:2022 Annex A Control.
ISO 27001:2022 Organisational Controls
| Annex A Control Type | ISO/IEC 27001:2022 Annex A Identifier | ISO/IEC 27001:2013 Annex A Identifier | Annex A Name |
|---|---|---|---|
| Organisational Controls | Annex A 5.1 | Annex A 5.1.1 Annex A 5.1.2 | Policies for Information Security |
| Organisational Controls | Annex A 5.2 | Annex A 6.1.1 | Information Security Roles and Responsibilities |
| Organisational Controls | Annex A 5.3 | Annex A 6.1.2 | Segregation of Duties |
| Organisational Controls | Annex A 5.4 | Annex A 7.2.1 | Management Responsibilities |
| Organisational Controls | Annex A 5.5 | Annex A 6.1.3 | Contact With Authorities |
| Organisational Controls | Annex A 5.6 | Annex A 6.1.4 | Contact With Special Interest Groups |
| Organisational Controls | Annex A 5.7 | NEW | Threat Intelligence |
| Organisational Controls | Annex A 5.8 | Annex A 6.1.5 Annex A 14.1.1 | Information Security in Project Management |
| Organisational Controls | Annex A 5.9 | Annex A 8.1.1 Annex A 8.1.2 | Inventory of Information and Other Associated Assets |
| Organisational Controls | Annex A 5.10 | Annex A 8.1.3 Annex A 8.2.3 | Acceptable Use of Information and Other Associated Assets |
| Organisational Controls | Annex A 5.11 | Annex A 8.1.4 | Return of Assets |
| Organisational Controls | Annex A 5.12 | Annex A 8.2.1 | Classification of Information |
| Organisational Controls | Annex A 5.13 | Annex A 8.2.2 | Labelling of Information |
| Organisational Controls | Annex A 5.14 | Annex A 13.2.1 Annex A 13.2.2 Annex A 13.2.3 | Information Transfer |
| Organisational Controls | Annex A 5.15 | Annex A 9.1.1 Annex A 9.1.2 | Access Control |
| Organisational Controls | Annex A 5.16 | Annex A 9.2.1 | Identity Management |
| Organisational Controls | Annex A 5.17 | Annex A 9.2.4 Annex A 9.3.1 Annex A 9.4.3 | Authentication Information |
| Organisational Controls | Annex A 5.18 | Annex A 9.2.2 Annex A 9.2.5 Annex A 9.2.6 | Access Rights |
| Organisational Controls | Annex A 5.19 | Annex A 15.1.1 | Information Security in Supplier Relationships |
| Organisational Controls | Annex A 5.20 | Annex A 15.1.2 | Addressing Information Security Within Supplier Agreements |
| Organisational Controls | Annex A 5.21 | Annex A 15.1.3 | Managing Information Security in the ICT Supply Chain |
| Organisational Controls | Annex A 5.22 | Annex A 15.2.1 Annex A 15.2.2 | Monitoring, Review and Change Management of Supplier Services |
| Organisational Controls | Annex A 5.23 | NEW | Information Security for Use of Cloud Services |
| Organisational Controls | Annex A 5.24 | Annex A 16.1.1 | Information Security Incident Management Planning and Preparation |
| Organisational Controls | Annex A 5.25 | Annex A 16.1.4 | Assessment and Decision on Information Security Events |
| Organisational Controls | Annex A 5.26 | Annex A 16.1.5 | Response to Information Security Incidents |
| Organisational Controls | Annex A 5.27 | Annex A 16.1.6 | Learning From Information Security Incidents |
| Organisational Controls | Annex A 5.28 | Annex A 16.1.7 | Collection of Evidence |
| Organisational Controls | Annex A 5.29 | Annex A 17.1.1 Annex A 17.1.2 Annex A 17.1.3 | Information Security During Disruption |
| Organisational Controls | Annex A 5.30 | NEW | ICT Readiness for Business Continuity |
| Organisational Controls | Annex A 5.31 | Annex A 18.1.1 Annex A 18.1.5 | Legal, Statutory, Regulatory and Contractual Requirements |
| Organisational Controls | Annex A 5.32 | Annex A 18.1.2 | Intellectual Property Rights |
| Organisational Controls | Annex A 5.33 | Annex A 18.1.3 | Protection of Records |
| Organisational Controls | Annex A 5.34 | Annex A 18.1.4 | Privacy and Protection of PII |
| Organisational Controls | Annex A 5.35 | Annex A 18.2.1 | Independent Review of Information Security |
| Organisational Controls | Annex A 5.36 | Annex A 18.2.2 Annex A 18.2.3 | Compliance With Policies, Rules and Standards for Information Security |
| Organisational Controls | Annex A 5.37 | Annex A 12.1.1 | Documented Operating Procedures |
ISO 27001:2022 People Controls
| Annex A Control Type | ISO/IEC 27001:2022 Annex A Identifier | ISO/IEC 27001:2013 Annex A Identifier | Annex A Name |
|---|---|---|---|
| People Controls | Annex A 6.1 | Annex A 7.1.1 | Screening |
| People Controls | Annex A 6.2 | Annex A 7.1.2 | Terms and Conditions of Employment |
| People Controls | Annex A 6.3 | Annex A 7.2.2 | Information Security Awareness, Education and Training |
| People Controls | Annex A 6.4 | Annex A 7.2.3 | Disciplinary Process |
| People Controls | Annex A 6.5 | Annex A 7.3.1 | Responsibilities After Termination or Change of Employment |
| People Controls | Annex A 6.6 | Annex A 13.2.4 | Confidentiality or Non-Disclosure Agreements |
| People Controls | Annex A 6.7 | Annex A 6.2.2 | Remote Working |
| People Controls | Annex A 6.8 | Annex A 16.1.2 Annex A 16.1.3 | Information Security Event Reporting |
ISO 27001:2022 Physical Controls
| Annex A Control Type | ISO/IEC 27001:2022 Annex A Identifier | ISO/IEC 27001:2013 Annex A Identifier | Annex A Name |
|---|---|---|---|
| Physical Controls | Annex A 7.1 | Annex A 11.1.1 | Physical Security Perimeters |
| Physical Controls | Annex A 7.2 | Annex A 11.1.2 Annex A 11.1.6 | Physical Entry |
| Physical Controls | Annex A 7.3 | Annex A 11.1.3 | Securing Offices, Rooms and Facilities |
| Physical Controls | Annex A 7.4 | NEW | Physical Security Monitoring |
| Physical Controls | Annex A 7.5 | Annex A 11.1.4 | Protecting Against Physical and Environmental Threats |
| Physical Controls | Annex A 7.6 | Annex A 11.1.5 | Working In Secure Areas |
| Physical Controls | Annex A 7.7 | Annex A 11.2.9 | Clear Desk and Clear Screen |
| Physical Controls | Annex A 7.8 | Annex A 11.2.1 | Equipment Siting and Protection |
| Physical Controls | Annex A 7.9 | Annex A 11.2.6 | Security of Assets Off-Premises |
| Physical Controls | Annex A 7.10 | Annex A 8.3.1 Annex A 8.3.2 Annex A 8.3.3 Annex A 11.2.5 | Storage Media |
| Physical Controls | Annex A 7.11 | Annex A 11.2.2 | Supporting Utilities |
| Physical Controls | Annex A 7.12 | Annex A 11.2.3 | Cabling Security |
| Physical Controls | Annex A 7.13 | Annex A 11.2.4 | Equipment Maintenance |
| Physical Controls | Annex A 7.14 | Annex A 11.2.7 | Secure Disposal or Re-Use of Equipment |
ISO 27001:2022 Technological Controls
| Annex A Control Type | ISO/IEC 27001:2022 Annex A Identifier | ISO/IEC 27001:2013 Annex A Identifier | Annex A Name |
|---|---|---|---|
| Technological Controls | Annex A 8.1 | Annex A 6.2.1 Annex A 11.2.8 | User Endpoint Devices |
| Technological Controls | Annex A 8.2 | Annex A 9.2.3 | Privileged Access Rights |
| Technological Controls | Annex A 8.3 | Annex A 9.4.1 | Information Access Restriction |
| Technological Controls | Annex A 8.4 | Annex A 9.4.5 | Access to Source Code |
| Technological Controls | Annex A 8.5 | Annex A 9.4.2 | Secure Authentication |
| Technological Controls | Annex A 8.6 | Annex A 12.1.3 | Capacity Management |
| Technological Controls | Annex A 8.7 | Annex A 12.2.1 | Protection Against Malware |
| Technological Controls | Annex A 8.8 | Annex A 12.6.1 Annex A 18.2.3 | Management of Technical Vulnerabilities |
| Technological Controls | Annex A 8.9 | NEW | Configuration Management |
| Technological Controls | Annex A 8.10 | NEW | Information Deletion |
| Technological Controls | Annex A 8.11 | NEW | Data Masking |
| Technological Controls | Annex A 8.12 | NEW | Data Leakage Prevention |
| Technological Controls | Annex A 8.13 | Annex A 12.3.1 | Information Backup |
| Technological Controls | Annex A 8.14 | Annex A 17.2.1 | Redundancy of Information Processing Facilities |
| Technological Controls | Annex A 8.15 | Annex A 12.4.1 Annex A 12.4.2 Annex A 12.4.3 | Logging |
| Technological Controls | Annex A 8.16 | NEW | Monitoring Activities |
| Technological Controls | Annex A 8.17 | Annex A 12.4.4 | Clock Synchronization |
| Technological Controls | Annex A 8.18 | Annex A 9.4.4 | Use of Privileged Utility Programs |
| Technological Controls | Annex A 8.19 | Annex A 12.5.1 Annex A 12.6.2 | Installation of Software on Operational Systems |
| Technological Controls | Annex A 8.20 | Annex A 13.1.1 | Networks Security |
| Technological Controls | Annex A 8.21 | Annex A 13.1.2 | Security of Network Services |
| Technological Controls | Annex A 8.22 | Annex A 13.1.3 | Segregation of Networks |
| Technological Controls | Annex A 8.23 | NEW | Web filtering |
| Technological Controls | Annex A 8.24 | Annex A 10.1.1 Annex A 10.1.2 | Use of Cryptography |
| Technological Controls | Annex A 8.25 | Annex A 14.2.1 | Secure Development Life Cycle |
| Technological Controls | Annex A 8.26 | Annex A 14.1.2 Annex A 14.1.3 | Application Security Requirements |
| Technological Controls | Annex A 8.27 | Annex A 14.2.5 | Secure System Architecture and Engineering Principles |
| Technological Controls | Annex A 8.28 | NEW | Secure Coding |
| Technological Controls | Annex A 8.29 | Annex A 14.2.8 Annex A 14.2.9 | Security Testing in Development and Acceptance |
| Technological Controls | Annex A 8.30 | Annex A 14.2.7 | Outsourced Development |
| Technological Controls | Annex A 8.31 | Annex A 12.1.4 Annex A 14.2.6 | Separation of Development, Test and Production Environments |
| Technological Controls | Annex A 8.32 | Annex A 12.1.2 Annex A 14.2.2 Annex A 14.2.3 Annex A 14.2.4 | Change Management |
| Technological Controls | Annex A 8.33 | Annex A 14.3.1 | Test Information |
| Technological Controls | Annex A 8.34 | Annex A 12.7.1 | Protection of Information Systems During Audit Testing |
How ISMS.online Help
ISMS.online simplifies the ISO 27001:2022 implementation process through a sophisticated cloud-based framework, which supplies documentation of information security management system processes and checklists to ensure compatibility with accepted standards.
Contact us to arrange a demonstration.
Jump to topic
