What evidence do auditors commonly ask for on A.8.33 Test information?

Statement of Applicability entry for control A.8.33, showing inclusion or justified exclusion, implementation status and the risks it treats; A test data procedure stating how test information is selected and prohibiting unprotected sensitive data in non-production; Authorization records for each copy of operational information into a test environment; Logs of copying and use of operational information in test environments; Masking or anonymization configuration applied to test data sets.

What is the most common gap auditors find on A.8.33?

Full production databases are cloned into test environments routinely without approval

ISO/IEC 27001:2022 · Technological controls

`A.8.33` Test information

Information used for testing is to be chosen, protected and managed appropriately. Purpose (stated in ISO/IEC 27002:2022): ensures testing is relevant and operational information used for testing is protected. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.33.

Source: ISO/IEC 27001:2022, A.8.33. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.

Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.

artefacts

held by a system

at each review

moderate

to go live

SIEM / log platform

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Logs of copying and use of operational information in test environments · SIEM / log platform
Masking or anonymization configuration applied to test data sets · Cloud console / configuration management

periodic reviewEvidence produced at each review

Authorization records for each copy of operational information into a test environment · Cloud console / configuration management

governing documentDocuments that govern the control

Statement of Applicability entry for control A.8.33, showing inclusion or justified exclusion, implementation status and the risks it treats · Policy repository / GRC workspace
A test data procedure stating how test information is selected and prohibiting unprotected sensitive data in non-production · Policy repository / GRC workspace

First move

Start with the 2 of 5 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Full production databases are cloned into test environments routinely without approval
Test environments hold personal data with far weaker access controls than production
Copies of production data remain in test long after testing ends
Masking is applied inconsistently, leaving identifiable fields

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

A.8.32 Change management · A.8.34 Protection of information systems during audit testing