TSA Pipeline Cybersecurity Directives
The TSA Security Directives binding the most critical US hazardous liquid and natural gas pipeline and LNG owner/operators since the Colonial Pipeline attack: the Pipeline-2021-01 series (currently 01G: 24/7 Cybersecurity Coordinators, reporting incidents to CISA within 72 hours, a vulnerability assessment against Section 7 of the Pipeline Security Guidelines) and the performance-based Pipeline-2021-02 series (currently 02G: a TSA-approved Cybersecurity Implementation Plan covering Critical Cyber System identification, IT/OT segmentation, access control, continuous monitoring and patching, a tested incident response plan and an annual assessment plan with a two-yearly architecture review and one-third annual coverage). Read in full from the directives TSA publishes.
TSA Pipeline Cybersecurity Directives is a compliance framework from United States (federal, TSA) with 5 domains and 49 controls that map to 119 other frameworks. The largest domains are SD Pipeline-2021-02G Section III.A to III.E: Cybersecurity measures – TSA Pipeline Cybersecurity Directives (15 controls), SD Pipeline-2021-02G Sections II and IV to VI: Applicability, implementation plan, records and amendments – TSA Pipeline Cybersecurity Directives (11 controls), SD Pipeline-2021-01G: Coordinator, incident reporting and vulnerability assessment – TSA Pipeline Cybersecurity Directives (9 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are interpretations grounded in the published source, for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (5)
SD Pipeline-2021-01G: Coordinator, incident reporting and vulnerability assessment – TSA Pipeline Cybersecurity Directives
| Code | Title |
|---|---|
| tsa-pipeline-cybersecurity-directives::SD01-II.B.1 | SD01 II.B.1 Designate primary and alternate Cybersecurity Coordinators |
| tsa-pipeline-cybersecurity-directives::SD01-II.B.1.d | SD01 II.B.1.d and e Report coordinator details to TSA and keep them current |
| tsa-pipeline-cybersecurity-directives::SD01-II.B.2 | SD01 II.B.2 Coordinator duties and 24/7 availability |
| tsa-pipeline-cybersecurity-directives::SD01-II.C.2 | SD01 II.C.2 Report cybersecurity incidents to CISA |
| tsa-pipeline-cybersecurity-directives::SD01-II.C.3 | SD01 II.C.3 and 4 Report within 72 hours through CISA Central |
| tsa-pipeline-cybersecurity-directives::SD01-II.C.5 | SD01 II.C.5 Content of the CISA report and supplemental information |
| tsa-pipeline-cybersecurity-directives::SD01-II.D.1 | SD01 II.D.1 Cybersecurity Vulnerability Assessment against Section 7 of the Pipeline Security Guidelines |
| tsa-pipeline-cybersecurity-directives::SD01-II.D.2 | SD01 II.D.2 and 3 Use TSA Form 1604 and submit the assessment and remediation plan |
| tsa-pipeline-cybersecurity-directives::SD01-III | SD01 III and V Directive procedures and alternative measures |
SD Pipeline-2021-02G Section III.A to III.E: Cybersecurity measures – TSA Pipeline Cybersecurity Directives
| Code | Title |
|---|---|
| tsa-pipeline-cybersecurity-directives::SD02-III.A | SD02 III.A Identify Critical Cyber Systems |
| tsa-pipeline-cybersecurity-directives::SD02-III.B.1 | SD02 III.B.1 List and describe interdependencies, external connections and zone boundaries |
| tsa-pipeline-cybersecurity-directives::SD02-III.B.2 | SD02 III.B.2 Secure and defend zone boundaries |
| tsa-pipeline-cybersecurity-directives::SD02-III.C.1 | SD02 III.C.1 Identification and authentication, memorized secret reset schedule |
| tsa-pipeline-cybersecurity-directives::SD02-III.C.2 | SD02 III.C.2 Multi-factor authentication or equivalent controls |
| tsa-pipeline-cybersecurity-directives::SD02-III.C.3 | SD02 III.C.3 Least privilege and separation of duties |
| tsa-pipeline-cybersecurity-directives::SD02-III.C.4 | SD02 III.C.4 Shared accounts limited to operational necessity |
| tsa-pipeline-cybersecurity-directives::SD02-III.C.5 | SD02 III.C.5 Domain trust relationship review |
| tsa-pipeline-cybersecurity-directives::SD02-III.D.1 | SD02 III.D.1 Preventive and blocking capabilities |
| tsa-pipeline-cybersecurity-directives::SD02-III.D.2 | SD02 III.D.2 Audit and response procedures |
| tsa-pipeline-cybersecurity-directives::SD02-III.D.3 | SD02 III.D.3 Logging policies |
| tsa-pipeline-cybersecurity-directives::SD02-III.D.4 | SD02 III.D.4 Ability to isolate industrial control systems |
| tsa-pipeline-cybersecurity-directives::SD02-III.E.1 | SD02 III.E.1 Patch management strategy keeping critical patches current |
| tsa-pipeline-cybersecurity-directives::SD02-III.E.2 | SD02 III.E.2 Risk methodology, timelines and KEV prioritization |
| tsa-pipeline-cybersecurity-directives::SD02-III.E.3 | SD02 III.E.3 Mitigations where OT cannot be patched |
SD Pipeline-2021-02G Section III.F: Cybersecurity Incident Response Plan – TSA Pipeline Cybersecurity Directives
| Code | Title |
|---|---|
| tsa-pipeline-cybersecurity-directives::SD02-III.F.1.a | SD02 III.F.1.a Prompt containment |
| tsa-pipeline-cybersecurity-directives::SD02-III.F.1.b | SD02 III.F.1.b Segregation of infected networks and devices |
| tsa-pipeline-cybersecurity-directives::SD02-III.F.1.c | SD02 III.F.1.c Security and integrity of backups |
| tsa-pipeline-cybersecurity-directives::SD02-III.F.1.d | SD02 III.F.1.d Capability and governance to isolate IT and OT |
| tsa-pipeline-cybersecurity-directives::SD02-III.F.1.e | SD02 III.F.1.e Annual exercises testing at least two objectives |
| tsa-pipeline-cybersecurity-directives::SD02-III.F.2 | SD02 III.F.2 Responsibilities by position and resources |
SD Pipeline-2021-02G Section III.G: Cybersecurity Assessment Plan – TSA Pipeline Cybersecurity Directives
| Code | Title |
|---|---|
| tsa-pipeline-cybersecurity-directives::SD02-III.G.1 | SD02 III.G.1 Develop a Cybersecurity Assessment Plan |
| tsa-pipeline-cybersecurity-directives::SD02-III.G.2.a | SD02 III.G.2.a Assess the effectiveness of the approved CIP |
| tsa-pipeline-cybersecurity-directives::SD02-III.G.2.b | SD02 III.G.2.b Architecture design review at least every two years |
| tsa-pipeline-cybersecurity-directives::SD02-III.G.2.c | SD02 III.G.2.c Other assessment capabilities: penetration testing, red and purple teams |
| tsa-pipeline-cybersecurity-directives::SD02-III.G.2.d | SD02 III.G.2.d Schedule covering one-third each year and all over three years |
| tsa-pipeline-cybersecurity-directives::SD02-III.G.2.e | SD02 III.G.2.e Annual report content |
| tsa-pipeline-cybersecurity-directives::SD02-III.G.3 | SD02 III.G.3 Submit the CAP annually for approval |
| tsa-pipeline-cybersecurity-directives::SD02-III.G.4 | SD02 III.G.4 Submit the CAP annual report |
SD Pipeline-2021-02G Sections II and IV to VI: Applicability, implementation plan, records and amendments – TSA Pipeline Cybersecurity Directives
| Code | Title |
|---|---|
| tsa-pipeline-cybersecurity-directives::SD02-II.A.3 | SD02 II.A.3 Managed Security Service Providers: owner/operator keeps sole responsibility |
| tsa-pipeline-cybersecurity-directives::SD02-II.A.4 | SD02 II.A.4 Authorized Representatives: joint liability |
| tsa-pipeline-cybersecurity-directives::SD02-II.A.5 | SD02 II.A.5 Scope: Critical Cyber Systems and the no-system notification |
| tsa-pipeline-cybersecurity-directives::SD02-II.B.1 | SD02 II.B.1 CIP content: defense-in-depth plan for Sections III.A to III.E |
| tsa-pipeline-cybersecurity-directives::SD02-II.B.2 | SD02 II.B.2 Implement and maintain the approved CIP and its schedule |
| tsa-pipeline-cybersecurity-directives::SD02-IV.A | SD02 IV.A Use of previous plans, assessments, tests and evaluations |
| tsa-pipeline-cybersecurity-directives::SD02-IV.B | SD02 IV.B Protection of sensitive security information |
| tsa-pipeline-cybersecurity-directives::SD02-IV.C | SD02 IV.C Documentation to establish compliance |
| tsa-pipeline-cybersecurity-directives::SD02-V.A | SD02 V Directive procedures: receipt, dissemination and submissions |
| tsa-pipeline-cybersecurity-directives::SD02-VI.A | SD02 VI.A Amend the CIP on a change of ownership or control |
| tsa-pipeline-cybersecurity-directives::SD02-VI.B | SD02 VI.B to D Amend the CIP for permanent changes within 50 days |
Your Compliance Coverage
If you comply with TSA Pipeline Cybersecurity Directives, you already cover:
ISO 27002:2022
23%
17 controls mapped
Compare →API 1164
4%
3 controls mapped
Compare →ICAO Annex 17 - Aviation Security (AVSEC)
3%
2 controls mapped
Compare →+ 116 more: Vietnam PDPD (3%), Vietnam Law on Cybersecurity (No. 116/2025/QH15) (3%)
See all 119 mapped frameworks ↓Maps to 119 other frameworks
Coverage is not the same as your position
This page shows what TSA Pipeline Cybersecurity Directives overlaps with in general. Where your organisation actually stands, against the standard you are going for and the certifications you already hold, is a different question. Same graph and the same recorded refutations, scoped to you rather than to a pair.
The Compliance Position Diagnostic, $5,000 fixed, ten business daysWhat is TSA Pipeline Cybersecurity Directives and who does it apply to?
TSA Pipeline Cybersecurity Directives is a compliance framework from United States (federal, TSA) with 5 domains and 49 controls. The TSA Security Directives binding the most critical US hazardous liquid and natural gas pipeline and LNG owner/operators since the Colonial Pipeline attack: the Pipeline-2021-01 series (currently 01G: 24/7 Cybersecurity Coordinators, reporting incidents to CISA within 72 hours, a vulnerability assessment against Section 7 of the Pipeline Security Guidelines) and the performance-based Pipeline-2021-02 series (currently 02G: a TSA-approved Cybersecurity Implementation Plan covering Critical Cyber System identification, IT/OT segmentation, access control, continuous monitoring and patching, a tested incident response plan and an annual assessment plan with a two-yearly architecture review and one-third annual coverage). Read in full from the directives TSA publishes. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does TSA Pipeline Cybersecurity Directives actually require?
TSA Pipeline Cybersecurity Directives has 49 controls organised across 5 domains. The largest domains are SD Pipeline-2021-02G Section III.A to III.E: Cybersecurity measures – TSA Pipeline Cybersecurity Directives (15 controls), SD Pipeline-2021-02G Sections II and IV to VI: Applicability, implementation plan, records and amendments – TSA Pipeline Cybersecurity Directives (11 controls), SD Pipeline-2021-01G: Coordinator, incident reporting and vulnerability assessment – TSA Pipeline Cybersecurity Directives (9 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of TSA Pipeline Cybersecurity Directives do I already cover?
TSA Pipeline Cybersecurity Directives maps to 119 other compliance frameworks. The top mapping partners are ISO 27002:2022 (23% coverage), API 1164 (4% coverage), ICAO Annex 17 - Aviation Security (AVSEC) (3% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement TSA Pipeline Cybersecurity Directives?
Start your TSA Pipeline Cybersecurity Directives compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about TSA Pipeline Cybersecurity Directives requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 49 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 1,120 frameworks.
Get Started Free →Free forever, no credit card required