Cross-Framework Mapping

APRA CPS 234vsNIST SP 800-145

See exactly how APRA CPS 234 controls map to NIST SP 800-145. Pre-computed mappings, identified gaps, and coverage analysis.

12
Controls Mapped
23
Gaps Found
23%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

APRA CPS 234 maps to NIST SP 800-145 with 23% coverage across 11 directly mapped controls. Analysis of 35 APRA CPS 234 controls identifies 34 compliance gaps — primarily concentrated in APRA CPS 234: Third-Party Risk Management.

Source: TheArtOfService Knowledge Graph | 35 controls analysed | 730 frameworks | 503K+ cross-framework mappings

Control Mappings

Showing 12 of 12 mapped controls across 7 domains. Sign up to explore all 503K+ mappings across 730 frameworks.

APRA CPS 234: Information Security Governance(1 mappings)

CPS234-05Roles and responsibilities definition
NIST145-01Shared responsibility model definition

APRA CPS 234: Cybersecurity Controls(4 mappings)

CPS234-06Network security and segmentation
NIST145-16Virtual network segmentation
CPS234-09Encryption and key management
NIST145-12Encryption of cloud-stored data
CPS234-10Secure configuration standards2 targets
NIST145-19Image and template hardening
NIST145-20Cloud configuration management

APRA CPS 234: Operational Resilience(1 mappings)

CPS234-12Disaster recovery procedures
NIST145-14Data backup and recovery in cloud

Controls(1 mappings)

CPS234-21Implementation of Controls
NIST145-22Incident response in cloud

APRA CPS 234: Incident Management & Reporting(3 mappings)

CPS234-21Implementation of Controls
NIST145-22Incident response in cloud
CPS234-23Frequency and Methodology of Testing
NIST145-22Incident response in cloud
CPS234-25Internal Audit of Information Security
NIST145-22Incident response in cloud

Assurance(1 mappings)

CPS234-23Frequency and Methodology of Testing
NIST145-22Incident response in cloud

Audit(1 mappings)

CPS234-25Internal Audit of Information Security
NIST145-22Incident response in cloud

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 730 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 730 framework browser
  • Cross-framework mappings (503K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between APRA CPS 234 and NIST SP 800-145?

APRA CPS 234 has 35 controls across its framework, while NIST SP 800-145 covers 45 controls. Direct mapping analysis identifies 11 overlapping controls (23% coverage). The frameworks diverge most significantly in APRA CPS 234: Third-Party Risk Management, where 5 APRA CPS 234 controls have no direct NIST SP 800-145 equivalent.

How many controls map between APRA CPS 234 and NIST SP 800-145?

Of 35 total APRA CPS 234 controls, 11 map directly to NIST SP 800-145 controls — representing 23% coverage. The remaining 34 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping APRA CPS 234 to NIST SP 800-145?

34 APRA CPS 234 controls have no direct equivalent in NIST SP 800-145. The highest concentration of gaps is in APRA CPS 234: Third-Party Risk Management with 5 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between APRA CPS 234 and NIST SP 800-145?

The domain with the highest gap count is APRA CPS 234: Third-Party Risk Management (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.