What evidence do auditors commonly ask for on A.8.11 Data masking?

Statement of Applicability entry for control A.8.11, showing inclusion or justified exclusion, implementation status and the risks it treats; Policy or standard specifying where masking, pseudonymization or anonymization is required, based on access control policy, business needs and law; Masking configurations in applications, databases and reports showing minimum necessary data displayed per role; Verification or re-identification risk assessments demonstrating that anonymization or pseudonymization is adequate; Protection and separation of pseudonymization keys or additional information.

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

Data labelled as anonymized can be re-identified by combining remaining fields

ISO/IEC 27001:2022 · Technological controls

`A.8.11` Data masking

Data masking is to be applied as directed by the access control policy, related topic policies and what the business needs, with applicable law taken into account. Purpose (stated in ISO/IEC 27002:2022): reduces exposure of sensitive data such as PII and supports legal and contractual compliance. 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.11.

Source: ISO/IEC 27001:2022, A.8.11. 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

hard

to go live

Policy repository / GRC workspace

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

Masking configurations in applications, databases and reports showing minimum necessary data displayed per role · Identity provider / directory

periodic reviewEvidence produced at each review

Verification or re-identification risk assessments demonstrating that anonymization or pseudonymization is adequate · Data governance / DLP tooling

governing documentDocuments that govern the control

Statement of Applicability entry for control A.8.11, showing inclusion or justified exclusion, implementation status and the risks it treats · Policy repository / GRC workspace
Policy or standard specifying where masking, pseudonymization or anonymization is required, based on access control policy, business needs and law · Policy repository / GRC workspace
Protection and separation of pseudonymization keys or additional information · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Identity provider / directory on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

Data labelled as anonymized can be re-identified by combining remaining fields
Hashes of identifiers are unsalted and easily reversed by enumeration
Pseudonymization keys are stored alongside the pseudonymized data
Full production data is visible to all users of support and reporting tools

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.10 Information deletion · A.8.12 Data leakage prevention