United States (federal, TSA)

TSA Pipeline Cybersecurity Directives

93 controls. 126 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

93 controls 126 frameworks share controls with it United States (federal, TSA) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
SD-02-10Cybersecurity Assessment Program0
SD-02-11Annual Architecture Review0
SD-02-12Performance-Based Compliance0
SD-02-13NIST Framework Alignment0
TSA-SD-01TSA Cybersecurity Coordinator designation1
TSA-SD-02Cybersecurity incident reporting to CISA1
TSA-SD-03Cybersecurity Implementation Plan approval1
TSA-SD-04Critical Cyber System identification1
TSA-SD-05Network segmentation between IT and OT1
TSA-SD-06Access control to Critical Cyber Systems1
TSA-SD-07Continuous monitoring and detection1
TSA-SD-08Patch and vulnerability management1
TSA-SD-09Annual Cybersecurity Assessment Plan1
TSA-SD-10Cybersecurity Incident Response Plan1
TSA-SD-11Cybersecurity training and awareness1
TSA-SD-12Configuration and change management1
TSA-SD-13Backups and recovery for Critical Cyber Systems1
TSA-SD-14Supply chain and third party risk1
TSA-SD-15Annual Cybersecurity Assessment report submission1
TSA-SD-16Physical security of cyber assets1
TSA-SD-17Cybersecurity Coordinator update notifications1
TSA-SD-18Performance based outcome measurement1
TSAPIPE-1Cybersecurity Implementation Plan and Coordinator72
TSAPIPE-2OT/IT Network Segmentation and Access Control106
TSAPIPE-3Cybersecurity Incident Reporting to CISA0
TSAPIPE-4Cybersecurity Assessment Programme and Annual Testing0
NPRMPending rule: Enhancing Surface Cyber Risk Management (proposed rule of 7 November 2024)0
SD01-ISD01 I Purpose, information sharing and IV definitions0
SD01-IISD01 Section II Actions required0
SD01-II.B.1SD01 II.B.1 Designate primary and alternate Cybersecurity Coordinators0
SD01-II.B.1.dSD01 II.B.1.d and e Report coordinator details to TSA and keep them current0
SD01-II.B.2SD01 II.B.2 Coordinator duties and 24/7 availability0
SD01-II.CSD01 II.C Reporting cybersecurity incidents0
SD01-II.C.2SD01 II.C.2 Report cybersecurity incidents to CISA0
SD01-II.C.3SD01 II.C.3 and 4 Report within 72 hours through CISA Central0
SD01-II.C.5SD01 II.C.5 Content of the CISA report and supplemental information0
SD01-II.D.1SD01 II.D.1 Cybersecurity Vulnerability Assessment against Section 7 of the Pipeline Security Guidelines0
SD01-II.D.2SD01 II.D.2 and 3 Use TSA Form 1604 and submit the assessment and remediation plan0
SD01-IIISD01 III and V Directive procedures and alternative measures0
SD02-ISD02 I Purpose, performance-based approach, SSI and ratification0
SD02-II.ASD02 II.A Applicability, deadlines and scope0
SD02-II.A.3SD02 II.A.3 Managed Security Service Providers: owner/operator keeps sole responsibility0
SD02-II.A.4SD02 II.A.4 Authorized Representatives: joint liability0
SD02-II.A.5SD02 II.A.5 Scope: Critical Cyber Systems and the no-system notification0
SD02-II.BSD02 II.B Cybersecurity Implementation Plan0
SD02-II.B.1SD02 II.B.1 CIP content: defense-in-depth plan for Sections III.A to III.E0
SD02-II.B.2SD02 II.B.2 Implement and maintain the approved CIP and its schedule0
SD02-IIISD02 III Cybersecurity measures0
SD02-III.ASD02 III.A Identify Critical Cyber Systems0
SD02-III.BSD02 III.B Network segmentation0
SD02-III.B.1SD02 III.B.1 List and describe interdependencies, external connections and zone boundaries0
SD02-III.B.2SD02 III.B.2 Secure and defend zone boundaries0
SD02-III.CSD02 III.C Access control0
SD02-III.C.1SD02 III.C.1 Identification and authentication, memorized secret reset schedule0
SD02-III.C.2SD02 III.C.2 Multi-factor authentication or equivalent controls0
SD02-III.C.3SD02 III.C.3 Least privilege and separation of duties0
SD02-III.C.4SD02 III.C.4 Shared accounts limited to operational necessity0
SD02-III.C.5SD02 III.C.5 Domain trust relationship review0
SD02-III.DSD02 III.D Continuous monitoring and detection0
SD02-III.D.1SD02 III.D.1 Preventive and blocking capabilities0
SD02-III.D.2SD02 III.D.2 Audit and response procedures0
SD02-III.D.3SD02 III.D.3 Logging policies0
SD02-III.D.4SD02 III.D.4 Ability to isolate industrial control systems0
SD02-III.ESD02 III.E Patch management0
SD02-III.E.1SD02 III.E.1 Patch management strategy keeping critical patches current0
SD02-III.E.2SD02 III.E.2 Risk methodology, timelines and KEV prioritization0
SD02-III.E.3SD02 III.E.3 Mitigations where OT cannot be patched0
SD02-III.FSD02 III.F Cybersecurity Incident Response Plan0
SD02-III.F.1.aSD02 III.F.1.a Prompt containment0
SD02-III.F.1.bSD02 III.F.1.b Segregation of infected networks and devices0
SD02-III.F.1.cSD02 III.F.1.c Security and integrity of backups0
SD02-III.F.1.dSD02 III.F.1.d Capability and governance to isolate IT and OT0
SD02-III.F.1.eSD02 III.F.1.e Annual exercises testing at least two objectives0
SD02-III.F.2SD02 III.F.2 Responsibilities by position and resources0
SD02-III.GSD02 III.G Cybersecurity Assessment Plan0
SD02-III.G.1SD02 III.G.1 Develop a Cybersecurity Assessment Plan0
SD02-III.G.2.aSD02 III.G.2.a Assess the effectiveness of the approved CIP0
SD02-III.G.2.bSD02 III.G.2.b Architecture design review at least every two years0
SD02-III.G.2.cSD02 III.G.2.c Other assessment capabilities: penetration testing, red and purple teams0
SD02-III.G.2.dSD02 III.G.2.d Schedule covering one-third each year and all over three years0
SD02-III.G.2.eSD02 III.G.2.e Annual report content0
SD02-III.G.3SD02 III.G.3 Submit the CAP annually for approval0
SD02-III.G.4SD02 III.G.4 Submit the CAP annual report0
SD02-IVSD02 IV Records0
SD02-IV.ASD02 IV.A Use of previous plans, assessments, tests and evaluations0
SD02-IV.BSD02 IV.B Protection of sensitive security information0
SD02-IV.CSD02 IV.C Documentation to establish compliance0
SD02-V.ASD02 V Directive procedures: receipt, dissemination and submissions0
SD02-VISD02 VI Amendments to the Cybersecurity Implementation Plan0
SD02-VI.ASD02 VI.A Amend the CIP on a change of ownership or control0
SD02-VI.BSD02 VI.B to D Amend the CIP for permanent changes within 50 days0
SD02-VIISD02 VII Definitions0
SERIESThe two Security Directive series: history, renewals and ratification0

Tell me when TSA Pipeline Cybersecurity Directives files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • Recovery test plan
  • Test reports comparing expected and actual recovery duration
  • Actions on failed tests
  • Backup strategy and life cycle policy
  • Backup job logs
  • Restoration test results
  • Authentication mechanism documentation per interface
  • Identity store inventory (AD, local, application)
  • MFA implementation evidence on engineering and remote
  • Password policy aligned to SL-T

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for TSA Pipeline Cybersecurity Directives, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition