The entity tests whether its security controls work through a systematic testing program. How it tests and how often must reflect: (a) how quickly vulnerabilities and threats change; (b) the asset's criticality and sensitivity; (c) what an incident would cause; (d) the risks of exposure to untrusted environments where the entity cannot enforce its security policies; and (e) how material and frequent changes to the assets are.
This control maps to 2 controls across 2 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.
APRA CPS 234 27 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of APRA CPS 234 your existing evidence covers. Hold NIST Cybersecurity Framework 2.0 and 19 of 48 APRA CPS 234 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. 5 were rejected on the NIST Cybersecurity Framework 2.0 pair alone.
The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.