Cross-Framework Mapping

APRA CPS 234vsTSA Pipeline Cybersecurity Directives

See exactly how APRA CPS 234 controls map to TSA Pipeline Cybersecurity Directives. Pre-computed mappings, identified gaps, and coverage analysis.

8
Controls Mapped
27
Gaps Found
14%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

APRA CPS 234 maps to TSA Pipeline Cybersecurity Directives with 14% coverage across 8 directly mapped controls. Analysis of 35 APRA CPS 234 controls identifies 37 compliance gaps — primarily concentrated in APRA CPS 234: Third-Party Risk Management.

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

Control Mappings

Showing 8 of 8 mapped controls across 6 domains. Sign up to explore all 332K+ mappings across 723 frameworks.

APRA CPS 234: Cybersecurity Controls(1 mappings)

CPS234-06Network security and segmentation
TSAPIPE-2OT/IT Network Segmentation and Access Control

APRA CPS 234: Operational Resilience(1 mappings)

CPS234-12Disaster recovery procedures
TSAPIPE-2OT/IT Network Segmentation and Access Control

Controls(1 mappings)

CPS234-21Implementation of Controls
TSAPIPE-2OT/IT Network Segmentation and Access Control

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

CPS234-21Implementation of Controls
TSAPIPE-2OT/IT Network Segmentation and Access Control
CPS234-23Frequency and Methodology of Testing
TSAPIPE-2OT/IT Network Segmentation and Access Control
CPS234-25Internal Audit of Information Security
TSAPIPE-2OT/IT Network Segmentation and Access Control

Assurance(1 mappings)

CPS234-23Frequency and Methodology of Testing
TSAPIPE-2OT/IT Network Segmentation and Access Control

Audit(1 mappings)

CPS234-25Internal Audit of Information Security
TSAPIPE-2OT/IT Network Segmentation and Access Control

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 723 framework browser
  • Cross-framework mappings (332K+)
  • 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 TSA Pipeline Cybersecurity Directives?

APRA CPS 234 has 35 controls across its framework, while TSA Pipeline Cybersecurity Directives covers 4 controls. Direct mapping analysis identifies 8 overlapping controls (14% coverage). The frameworks diverge most significantly in APRA CPS 234: Third-Party Risk Management, where 5 APRA CPS 234 controls have no direct TSA Pipeline Cybersecurity Directives equivalent.

How many controls map between APRA CPS 234 and TSA Pipeline Cybersecurity Directives?

Of 35 total APRA CPS 234 controls, 8 map directly to TSA Pipeline Cybersecurity Directives controls — representing 14% coverage. The remaining 37 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 TSA Pipeline Cybersecurity Directives?

37 APRA CPS 234 controls have no direct equivalent in TSA Pipeline Cybersecurity Directives. 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 TSA Pipeline Cybersecurity Directives?

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.