Skip to content
Technological controls
ISO 27001A.8.34

ISO 27001 Annex A 8.34 Protection of information systems during audit testing

What it says

Audit tests and other assurance activities involving assessment of operational systems shall be planned and agreed between the tester and appropriate management.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Plan audit tests and other assurance activities that assess operational systems, and agree them between the tester and appropriate management, before they start.

The tester and appropriate management must plan and agree audit tests and other assurance activities that assess operational systems, before they begin. Operational systems are live ones the business relies on. Assurance activities include internal and external audit tests, vulnerability scans, penetration tests and configuration reviews, whoever performs them. Your organisation decides who appropriate management is, based on its risks and context: normally the people with authority over the systems and processes affected.

Why it matters

A scan or audit query on a live system can slow it, stop it or change data during business hours. Agreeing scope, access and timing first limits the disruption to operations and the exposure of data to the tester.

How to implement

  1. Identify which activities touch live systems and who agrees them.

    Include internal and external audits, vulnerability scans, penetration tests and customer assessments. For each system, name the manager with authority over it, as your organisation decides from its risks. One agreement can cover routine scanning, provided its scope and timing are set out.

  2. Agree a written plan before any test starts.

    State the systems and data in scope, the tests and tools, dates and times, who is testing, the access needed and who to call if something goes wrong. Have the tester and the manager both confirm it, and handle any later change of scope the same way.

  3. Limit access to what the test needs.

    Give read-only access where you can. If that will not get the information, have an experienced administrator run the test on the tester's behalf. Allow write access only on isolated copies (delete or protect them afterwards) or for an agreed penetration test. Check the tester's device is patched and protected before it connects.

  4. Schedule disruptive tests and watch them as they run.

    Run anything that could affect availability outside business hours or in a window the manager agrees. Agree anything that adds load, such as running audit tools. Log and monitor all test access, and remove it when the test ends.

  5. Agree tests of bought services with the provider first.

    Many providers set rules for customer testing, so check those terms, get written agreement where they require it, and test only your own tenant. Where testing is not allowed, rely on the provider's assurance reports (Annex A 5.22 covers monitoring suppliers).

Keep it running

Keep a list of who can agree tests for each system, and update it when systems or managers change. Look again when you engage a new auditor or tool, when a provider changes its testing terms, or when a test affects a live service.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    A list of audit tests and assurance activities for the period, compared with invoices, audit reports and scanner activity in firewall logs.

    Look at

    Activities that appear in those sources but have no plan.

    Good evidence

    Every activity found in those sources has an agreed plan.

  2. Check 2 of 5What an auditor asks for

    Ask for

    The agreed plan for a recent test on an operational system.

    Look at

    Its scope, access, tools and timing, who agreed it and when.

    Good evidence

    The plan sets scope, access, tools and timing, and the tester and a manager with authority over the system agreed it on a date before testing began.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Access and activity logs for that test, compared with the plan.

    Look at

    Systems touched, times, permissions used and whether access was removed afterwards.

    Good evidence

    Logged activity stayed within the agreed scope, times and access level, and test access was removed when the test ended.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Service and incident records for the window of a test that could affect availability.

    Look at

    Whether it ran in the agreed window, and what happened if a live service was affected.

    Good evidence

    The test ran in the agreed window, and any effect on a live service was handled as the plan set out.

  5. Check 5 of 5What an auditor asks for

    Ask for

    The provider's testing terms or written agreement for a test on a bought service.

    Look at

    Whether the test was allowed and stayed within those terms.

    Good evidence

    The provider's terms or written agreement cover the test, and it touched only your own tenant.

Mappings

Closest match in ASD Information Security Manual: ISM-1524, Ensure rigorous security testing of CDS content filters, which partially overlaps with this control.

ASD ISM

ASD Information Security Manual: 4 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.

Get help with this control

ISO 27001 training

Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.