cm/controlmapping
Sources
CPS 234 · Testing control effectiveness
Para 31

Review the testing programme at least annually

frameworkAPRA CPS 234 Information Security sectionTesting control effectiveness csf 2.0GV.RM-01 GV.RM-02 GV.RM-03 GV.RM-06 topicsRisk Management frameworks0 10 0 3
Official textAn APRA-regulated entity must review the sufficiency of the testing program at least annually or when there is a material change to information assets or the business environment.APRA Prudential Standard CPS 234 Information Security. Based on content from the Federal Register of Legislation at 27 October 2026 (footnote markers removed and lines reflowed). For the latest information on Australian Government legislation please go to https://www.legislation.gov.au. Licensed under CC BY 4.0: https://creativecommons.org/licenses/by/4.0/

Wrong or missing mapping? Report it

Equivalents of Para 31 in other frameworks
FrameworkRequirementTitleLinkSource / reason
NIST CSF 2.0GV.RM-01GV.RM-02GV.RM-03GV.RM-06Risk management objectives are established and agreed to by organizational stakeholders; Risk appetite and risk tolerance statements are established, communicated, and maintained…EditorialSame topic: Risk Management (editorial pick)
ISO 27001Clause 6.1.1Clause 6.1.3General; Information security risk treatmentEditorialSame topic: Risk Management (editorial pick)
2 loosely related (not mappings)
A.5.1 Policies for information security Loosely related
Only shares CSF GV.RM-01, GV.RM-02, GV.RM-03, GV.RM-06: related, not a mapping
Clause 6.1.2 Information security risk assessment Loosely related
Only shares CSF GV.RM-01, GV.RM-02, GV.RM-06: related, not a mapping
CIS v8.1—No requirementNo mapping in our dataNo mapping in our data (most CIS links are editorial: CIS's published crosswalk covers 49 of 153 safeguards).
SOC 2CC3.1CC5.1CC9.1Objectives specified clearly enough to identify risks; Control activities that mitigate risks…EditorialSame topic: Risk Management (editorial pick)
PCI DSS12.3.1Targeted risk analysis for flexible-frequency requirementsEditorialSame topic: Risk Management (editorial pick)
19 loosely related (not mappings)
5.2.3.1 Re-evaluation frequency set by targeted risk analysis Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
5.3.2.1 Scan frequency set by targeted risk analysis Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
6.3.1 Vulnerabilities identified and risk-ranked Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
6.3.3 Security patches installed promptly Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
7.2.5.1 System and application account access periodically reviewed Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
8.6.3 System account passwords protected and changed Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
9.5.1.2.1 Inspection frequency set by targeted risk analysis Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
10.4.2.1 Review frequency set by targeted risk analysis Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
…and 11 more in the downloads
CMMCRA.L2-3.11.1Risk AssessmentsEditorialSame topic: Risk Management (editorial pick)
800-53PM-9PM-28RA-7Risk Management Strategy; Risk Framing…EditorialSame topic: Risk Management (editorial pick)
6 loosely related (not mappings)
PM-30 Supply Chain Risk Management Strategy Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
SR-2 Supply Chain Risk Management Plan Loosely related
Only shares CSF GV.RM-01, GV.RM-03: related, not a mapping
PM-3 Information Security and Privacy Resources Loosely related
Only shares CSF GV.RM-03: related, not a mapping
PM-18 Privacy Program Plan Loosely related
Only shares CSF GV.RM-06: related, not a mapping
RA-3 Risk Assessment Loosely related
Only shares CSF GV.RM-06: related, not a mapping
SA-24 Design For Cyber Resiliency Loosely related
Only shares CSF GV.RM-03: related, not a mapping
HIPAA§164.308(a)(1)(ii)(B)Risk ManagementEditorialSame topic: Risk Management (editorial pick)
2 loosely related (not mappings)
§164.308(a)(1)(ii)(A) Risk Analysis Loosely related
Only shares CSF GV.RM-06: related, not a mapping
§164.316(a) Policies and Procedures Loosely related
Only shares CSF GV.RM-06: related, not a mapping
GDPRArt.24(1)Art.32(2)Responsibility of the controller; Security of processingEditorialSame topic: Risk Management (editorial pick)
NIS22.17.1Risk management framework; Policies and procedures to assess the effectiveness of cybersecurity risk-management measuresEditorialSame topic: Risk Management (editorial pick)
1 loosely related (not mappings)
1.1 Policy on the security of network and information systems Loosely related
Only shares CSF GV.RM-03: related, not a mapping
Essential Eight—No requirementNo mapping in our dataNo mapping in our data (Essential Eight links are editorial only).
DORAArt.5(2)(a)Art.6(1)Art.6(8)Art.16(1)Art.24(1)Governance and organisation; ICT risk management framework…EditorialSame topic: Risk Management (editorial pick)
Cyber Essentials—No requirementNo mapping in our dataNo mapping in our data (Cyber Essentials covers five technical controls only).

Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · Loosely related only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.