Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Select, protect and manage information used for testing appropriately.
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
Test information can expose live personal or business data if teams copy it carelessly, use broad access, or leave it behind after testing. Teams should decide when synthetic, masked, or approved production data is appropriate and what evidence demonstrates proper handling. The focus is on controlled selection, protection, retention, and disposal, not on assuming that any one dataset is acceptable for all tests.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Production data was copied into a test environment without documented approval, masking checks, or a defined deletion date after test completion.
Developers and testers use real customer records for convenience, but the records remain searchable, broadly accessible, and insufficiently protected in non-production.
The organization cannot show that test data was removed, destroyed, or archived according to the agreed retention rules, leaving unclear residual exposure.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Set a default hierarchy for testing inputs: synthetic data first, masked data second, and production data only when the owner approves a documented need. The data owner, privacy lead, and test lead should agree on scope, fields to mask, and whether the test environment has the same protections as production. Align this with the separation procedure.
Use a masking standard that covers direct identifiers, quasi-identifiers, and sensitive business fields. Specify the masking method, validation checks, and residual risk notes in the Data Masking Procedure. Where test results depend on realistic volumes, use approved snapshots with access restrictions and timed deletion rather than unrestricted copies.
Track every production-data exception with source system, purpose, approver, expiry, and destruction method. The test manager should confirm completion, while the data owner signs off that retention no longer applies. Store deletion logs, secure wipe certificates, or cloud lifecycle records as evidence of closure.
Build lightweight operational checks: compare test database access lists, confirm encrypted storage, and review whether non-production backups also contain test data. Use periodic reviews after major releases to remove stale datasets, refresh masks, and record lessons learned when testers request data that would be better represented by anonymized fixtures.
What an auditor will ask to see
A masking approval record naming the data owner, test purpose, masked fields, and expiry date.
A test dataset inventory showing synthetic, masked, or approved production data and where it resides.
Deletion or secure wipe evidence from the test environment, including lifecycle or purge logs.
A test plan or ticket referencing the approved dataset and any restrictions on copying or exporting it.
Baseline documents in the kit
These free kit documents help you document or evidence A.8.33. Each one is tailored to your organization when you build your kit.
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.