Control A.8.34Protection of information systems during audit testing
Audit tests and other assurance activities involving assessment of operational systems must be planned and agreed between the tester and appropriate management.
The control protects the systems from the assessment. Audit and assurance activity touches live systems — scanning, querying, extracting, sometimes testing controls actively — and each carries a risk of disruption or of exposing information to the assessor.
Planning and agreement means scope, timing, methods, the access the assessor needs, what may be extracted, how any data obtained is protected and returned or destroyed, and who is available if something goes wrong.
It applies to internal audit under clause 9.2, to independent review under A.5.35, to certification assessments, to penetration tests and to customer audits performed under a contractual right.
The read-only assumption is the one to examine. Assurance activity described as read-only routinely involves queries heavy enough to affect a production system, and agreeing a window and a rollback beforehand costs nothing compared with the outage that makes the assessment memorable for the wrong reason.
How to put this in place
Audits and technical tests touch live systems and can disrupt them or leave access behind. Your ISMS needs these activities planned and limited, so testing does not become a source of harm.
- Agree scope, timing and method with the tester or auditor in advance, keeping away from peak hours.
- Give read-only access where possible, take a backup before risky tests, and approve any testing on live systems.
- Monitor testers' activity while access is open.
- Remove access when the work ends and confirm it.
- Record the plan, approvals and access changes.
Evidence an auditor usually looks for: test and audit plans with agreed scope, records of access granted and removed, and approval for any testing on live systems.
What is in the packs for this
From ISO 27001 Implementation & Certification Readiness. Each one helps with this requirement.
Annex A Control Implementation LibraryExcel
Its row in the Control Library: what it is for, practical steps, what an auditor samples, the usual owner, common mistakes and whether it usually applies.
Statement of Applicability TemplateExcel
Has its own row on the Statement of Applicability sheet, where you record whether it applies, why and how far it is implemented.