ISO 27002:2022, Control 8.34 – Protection of Information Systems During Audit Testing

ISO 27002:2022 Revised Controls

Book a demo

data,center,programmer,using,digital,laptop,computer,,maintenance,it,specialist.

Audit tests play a critical role in detecting and eliminating security risks and vulnerabilities in the information systems.

However, the audit process, whether performed in operational, testing, or development environments, can expose sensitive information to the risks of unauthorised disclosure, or loss of integrity and availability.

Control 8.34 deals with how organisations can maintain the security of information assets during audit tests.

Purpose of Control 8.34

Control 8.34 enables organisations to eliminate and mitigate risks to the security of information systems and to the continuity of business operations by establishing and applying suitable measures and controls such as access restrictions and read-only access limitations.

Attributes Table

Control 8.34 is preventive in nature as it requires the upper management and the auditor to plan and agree on audit testing procedures, restrictions, and controls prior to carrying out audits.

Control Type Information Security PropertiesCybersecurity ConceptsOperational CapabilitiesSecurity Domains
#Preventive #Confidentiality
#Integrity
#Availability
#Protect#System and Network Security
#Information Protection
#Governance and Ecosystem
#Protection
Get a Headstart on ISO 27001
  • All updated with the 2022 control set
  • Make 81% progress from the minute you log in
  • Simple and easy to use
Book your demo
img

Ownership of Control 8.34

The IT management team should be responsible to plan and agree on audit procedures and to create and apply necessary measures.

General Guidance on Compliance

Control 8.34 lists eight specific requirements organisations should consider:

  1. Appropriate management and the auditor should agree on access to systems and information assets.
  2. Agreement on the scope of technical audit tests to be performed.
  3. Organisations can only provide read-only access to information and software. If it is not possible to use the read-only technique, an administrator with necessary access rights can gain access to systems or data on behalf of the auditor.
  4. If an access request is authorised, organisations should first verify that devices used to access systems meet the security requirements before they provide access.
  5. Access should only be provided for isolated copies of files extracted from the system. These copies should be permanently deleted once the audit is complete unless there is an obligation to retain those files. If read-only access is possible, this control does not apply.
  6. Requests by auditors to perform special processing such as deploying audit tools should be agreed upon by the management.
  7. If an audit runs the risk of impacting system availability, the audit should be carried out outside of business hours to maintain the availability of information.
  8. Access requests made for audits should be logged for the audit trail.

Supplementary Guidance on Control 8.34

When audits are performed on testing or development environments, organisations should be cautious against the following risks:

  • Compromise of the integrity of code.
  • Loss of confidentiality of sensitive information.

Get a Headstart
on ISO 27002

The only compliance
solution you need
Book your demo

Updated for ISO 27001 2022
  • 81% of the work done for you
  • Assured Results Method for certification success
  • Save time, money and hassle
Book your demo
img

Changes and Differences from ISO 27002:2013

27002:2022/8.34 replace 27002:2013/(12.7.1)

Although the 2022 version is similar to the 2013 version to great extent, there are two key differences.

ISO 27002:2022 Version Introduces a New Requirement

2022 version introduces the following requirement that was not referred to in the 2013 version:

If an access request is authorised, organisations should first verify that devices used to access systems meet the security requirements before they provide access.

2022 Version Addresses Testing and Development Environments

In the Supplementary Guidance, the 2022 version cautions organisations against the security risks due to audits performed on testing and development environments. The 2013 version, on the contrary, did not refer to the testing and development environments.

How ISMS.online Helps

ISO 27002 implementation is simpler with our step-by-step checklist that guides you through the whole process, from defining the scope of your ISMS through risk identification and control implementation.

Our platform is intuitive and easy-to-use. It’s not just for highly technical people; it’s for everyone in your organisation. We encourage you to involve staff at all levels of your business in the process of building your ISMS, because that helps you to build a truly sustainable system.

Get in touch today to book a demo.

Are you ready for
the new ISO 27002

We’ll give you an 81% headstart
from the moment you log in
Book your demo

New Controls

Organisational Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
5.105.1.1, 05.1.2Policies for information security
5.206.1.1Information security roles and responsibilities
5.306.1.2Segregation of duties
5.407.2.1Management responsibilities
5.506.1.3Contact with authorities
5.606.1.4Contact with special interest groups
5.7NewThreat intelligence
5.806.1.5, 14.1.1Information security in project management
5.908.1.1, 08.1.2Inventory of information and other associated assets
5.1008.1.3, 08.2.3Acceptable use of information and other associated assets
5.1108.1.4Return of assets
5.12 08.2.1Classification of information
5.1308.2.2Labelling of information
5.1413.2.1, 13.2.2, 13.2.3Information transfer
5.1509.1.1, 09.1.2Access control
5.1609.2.1Identity management
5.17 09.2.4, 09.3.1, 09.4.3Authentication information
5.1809.2.2, 09.2.5, 09.2.6Access rights
5.1915.1.1Information security in supplier relationships
5.2015.1.2Addressing information security within supplier agreements
5.2115.1.3Managing information security in the ICT supply chain
5.2215.2.1, 15.2.2Monitoring, review and change management of supplier services
5.23NewInformation security for use of cloud services
5.2416.1.1Information security incident management planning and preparation
5.2516.1.4Assessment and decision on information security events
5.2616.1.5Response to information security incidents
5.2716.1.6Learning from information security incidents
5.2816.1.7Collection of evidence
5.2917.1.1, 17.1.2, 17.1.3Information security during disruption
5.30NewICT readiness for business continuity
5.3118.1.1, 18.1.5Legal, statutory, regulatory and contractual requirements
5.3218.1.2Intellectual property rights
5.3318.1.3Protection of records
5.3418.1.4Privacy and protection of PII
5.3518.2.1Independent review of information security
5.3618.2.2, 18.2.3Compliance with policies, rules and standards for information security
5.3712.1.1Documented operating procedures

People Controls

Physical Controls

Trusted by companies everywhere
  • Simple and easy to use
  • Designed for ISO 27001 success
  • Saves you time and money
Book your demo
img

ISMS.online now supports ISO 42001 - the world's first AI Management System. Click to find out more