API 1164vsTSA Pipeline Cybersecurity Directives
See exactly how API 1164 controls map to TSA Pipeline Cybersecurity Directives. Pre-computed mappings, identified gaps, and coverage analysis.
Need this as a report you can hand to an assessor? A coverage crosswalk for this pair can be built to order.
According to the TheArtOfService Compliance Knowledge Graph:
API 1164 maps to TSA Pipeline Cybersecurity Directives with 7% coverage across 9 directly mapped controls. Analysis of 132 API 1164 controls identifies 154 compliance gaps, primarily concentrated in Protect (PR): access control, training, data security, protection processes, maintenance, protective technology (Section 7) – API 1164.
Source: TheArtOfService Knowledge Graph | 132 controls analysed | 704 frameworks | 307K+ cross-framework mappings
Control Mappings
Showing 10 of 10 mapped controls across 1 domains. Sign up to explore all 307K+ mappings across 704 frameworks.
Superseded batch representation – API 1164(10 mappings)
A API 1164 to TSA Pipeline Cybersecurity Directives crosswalk, built to order
The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which TSA Pipeline Cybersecurity Directives controls your existing API 1164 work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.
This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.
If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.
This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.
If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.
- Every evidenced control, with the reasoning behind it
- Every gap, with what it requires
- Its level of review stated plainly, not a bare number
Why this page shows two different percentages. The 7% in the header counts how many API 1164 controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many TSA Pipeline Cybersecurity Directives controls are actually evidenced, after a pass that argued against each mapping and kept only what survived. They answer different questions and they are not meant to agree.
A crosswalk narrows the work. It does not replace an audit, and your assessor may take a different view on individual controls. Mappings between frameworks are judgements, not text printed in either standard, which is why every claim in the report shows its reasoning. Questions go to support@theartofservice.com.
Related Comparisons
Other API 1164 comparisons
Other TSA Pipeline Cybersecurity Directives comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 704 frameworks, at a fraction of consulting costs.
Free
- ✓ 704 framework browser
- ✓ Cross-framework mappings (307K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between API 1164 and TSA Pipeline Cybersecurity Directives?
API 1164 has 132 controls across its framework, while TSA Pipeline Cybersecurity Directives covers 26 controls. Direct mapping analysis identifies 9 overlapping controls (7% coverage). The frameworks diverge most significantly in Protect (PR): access control, training, data security, protection processes, maintenance, protective technology (Section 7) – API 1164, where 46 API 1164 controls have no direct TSA Pipeline Cybersecurity Directives equivalent.
How many controls map between API 1164 and TSA Pipeline Cybersecurity Directives?
Of 132 total API 1164 controls, 9 map directly to TSA Pipeline Cybersecurity Directives controls, representing 7% coverage. The remaining 154 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping API 1164 to TSA Pipeline Cybersecurity Directives?
154 API 1164 controls have no direct equivalent in TSA Pipeline Cybersecurity Directives. The highest concentration of gaps is in Protect (PR): access control, training, data security, protection processes, maintenance, protective technology (Section 7) – API 1164 with 46 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 API 1164 and TSA Pipeline Cybersecurity Directives?
The domain with the highest gap count is Protect (PR): access control, training, data security, protection processes, maintenance, protective technology (Section 7) – API 1164 (46 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
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.