Test data and test accounts must be taken off system components before the system is put into production. The testing procedures cover commercial packaged software as well as applications built in-house, including recently installed or updated ones. Leftover test records and accounts can reveal how an application works and give an attacker an easy foothold into the system and the account data it handles. It applies to all entities. Objective under the customized approach: test data and test accounts cannot be present in production environments.
This control maps to 21 controls across 12 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
PCI DSS 4.0 6.5.6 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.
The graph holds this control, the 21 it maps to, and the evidence behind each claim, over MCP and REST.