A.8 Technological controls

A.8.34 Protection of information systems during audit testing

Not mandatory by default – decided in your SoA

What it means in plain language

Plan audits and technical tests on live systems so they do not disrupt operations.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Audit and technical testing can itself create an information security incident if scope, privileges or test intensity are poorly controlled. Production systems may contain sensitive data and dependencies that a tester cannot see from an initial brief. Clear agreements let the organisation obtain meaningful assurance while protecting service availability, limiting data exposure and ensuring temporary access and test artefacts are removed afterwards.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • A technical assessment begins with broad credentials but no agreed target list, permitted methods, stop conditions or accountable operational contact for an emergency.
  • Test extracts contain production personal data and remain in a reviewer’s workspace after the assessment, without approved retention or secure disposal arrangements.
  • A scan disrupts a fragile service because operations were not consulted about timing, load limits or dependencies outside the apparent target system.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Agree the assessment’s objectives, systems, methods and boundaries with authorised service owners before testing starts. Identify sensitive dependencies and distinguish observation from intrusive actions. Document prohibited techniques and conditions requiring additional approval so permission cannot be interpreted more broadly than intended.
  • Provide the minimum access needed for the agreed work, using named temporary accounts where practical. Prefer non-production testing or sanitised information when it answers the assurance question. Define how evidence will be protected and how reviewers may transfer it outside the environment.
  • Coordinate timing, monitoring and recovery arrangements with operations. Establish a live contact and clear stop criteria for unexpected effects, and confirm that restoration options are available for the planned activity. Record any deviations approved during the assessment rather than relying on informal permission.
  • Close the assessment by revoking temporary rights, removing test artefacts and confirming the system’s operational state. Reconcile evidence handling with the agreed retention and disposal terms. Feed findings into the normal corrective-action process while keeping testing safety lessons available for the next engagement.

What an auditor will ask to see

  • An authorised testing plan identifying targets, techniques, access limits, timing, operational contacts, stop conditions and the responsibilities of internal teams and external assessors.
  • Temporary-access records and monitoring or change approvals demonstrating that the assessment ran within the agreed boundaries and that unexpected effects were identified and handled.
  • Closeout evidence showing revocation of reviewer access, removal of artefacts, protection or disposal of extracted information and confirmation of the system’s condition after testing.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.34. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with 9.2 — Internal audit and A.8.32 — Change management. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.