Cross-Framework Mapping

ISO/IEC 29147:2018vsTSA Pipeline Cybersecurity Directives

See exactly how ISO/IEC 29147:2018 controls map to TSA Pipeline Cybersecurity Directives. Pre-computed mappings, identified gaps, and coverage analysis.

8
Controls Mapped
32
Gaps Found
12%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

ISO/IEC 29147:2018 maps to TSA Pipeline Cybersecurity Directives with 12% coverage across 7 directly mapped controls. Analysis of 40 ISO/IEC 29147:2018 controls identifies 41 compliance gaps — primarily concentrated in Clause 6: Receiving Vulnerability Reports.

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

Control Mappings

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

Legal(1 mappings)

29147-5.11Researcher Safe Harbour and Legal Posture
TSAPIPE-1Cybersecurity Implementation Plan and Coordinator

Clause 5: Vulnerability Disclosure Concepts(2 mappings)

29147-5.11Researcher Safe Harbour and Legal Posture
TSAPIPE-1Cybersecurity Implementation Plan and Coordinator
29147-5.6Advisory Content and Quality
TSAPIPE-1Cybersecurity Implementation Plan and Coordinator

Disclosure Artefacts(1 mappings)

29147-5.6Advisory Content and Quality
TSAPIPE-1Cybersecurity Implementation Plan and Coordinator

Clause 7: Publishing Vulnerability Advisories(1 mappings)

29147-7.8Remediation information
TSAPIPE-1Cybersecurity Implementation Plan and Coordinator

Clause 1-4: Introduction(3 mappings)

30111-1Scope
TSAPIPE-1Cybersecurity Implementation Plan and Coordinator
30111-3Terms and definitions2 targets
TSAPIPE-1Cybersecurity Implementation Plan and Coordinator
TSAPIPE-2OT/IT Network Segmentation and Access Control

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 718 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 ISO/IEC 29147:2018 and TSA Pipeline Cybersecurity Directives?

ISO/IEC 29147:2018 has 40 controls across its framework, while TSA Pipeline Cybersecurity Directives covers 4 controls. Direct mapping analysis identifies 7 overlapping controls (12% coverage). The frameworks diverge most significantly in Clause 6: Receiving Vulnerability Reports, where 7 ISO/IEC 29147:2018 controls have no direct TSA Pipeline Cybersecurity Directives equivalent.

How many controls map between ISO/IEC 29147:2018 and TSA Pipeline Cybersecurity Directives?

Of 40 total ISO/IEC 29147:2018 controls, 7 map directly to TSA Pipeline Cybersecurity Directives controls — representing 12% coverage. The remaining 41 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping ISO/IEC 29147:2018 to TSA Pipeline Cybersecurity Directives?

41 ISO/IEC 29147:2018 controls have no direct equivalent in TSA Pipeline Cybersecurity Directives. The highest concentration of gaps is in Clause 6: Receiving Vulnerability Reports with 7 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 ISO/IEC 29147:2018 and TSA Pipeline Cybersecurity Directives?

The domain with the highest gap count is Clause 6: Receiving Vulnerability Reports (7 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.