APRA CPS 234
Testing control effectiveness (paras 27 to 31) – APRA CPS 234

APRA CPS 234 31: Para 31 Review the sufficiency of the testing program

The entity reviews whether its testing program is sufficient at least once a year, and also whenever its information assets or business environment change materially.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 1 controls across 1 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.

Other controls in Testing control effectiveness (paras 27 to 31) – APRA CPS 234

You are reading one control. How much of APRA CPS 234 have you already done?

APRA CPS 234 31 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.

Query this from an agent

The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.