Skip to content

Sushegaad/Claude-Skills-Governance-Risk-and-Compliance / plugins/tsa-compliance/skills/tsa-compliance

tsa-compliance

Verified

Expert TSA cybersecurity compliance advisor for critical infrastructure owners and operators. Use this skill whenever a user asks about TSA Security Directives for pipelines, freight railroads, passenger rail, public transit, or bus operators; the TSA Cyber Risk Management Program (CRMP); Cybersecurity Implementation Plan (CIP); Cybersecurity Operational Implementation Plan (COIP); Cybersecurity Assessment Plan (CAP); incident reporting to CISA; designation of a Cybersecurity Coordinator; Critical Cyber Systems (CCS); OT/IT network segmentation; the TSA November 2024 NPRM; or any directive in the SD Pipeline-2021 series, SD 1580-21-01 (freight rail), SD 1582-21-01 (public transit/passenger rail), or SD 1580/82-2022-01 (rail CRMP). Also trigger for questions like "are we covered by TSA directives?", "what does the TSA require for pipeline cybersecurity?", "how do I build a CIP?", "what must I report to CISA?", or any request involving transportation critical infrastructure cybersecurity compliance.

references/tsa-directives-overview.md

View on GitHub
# TSA Cybersecurity Security Directives - Overview and Revision History

Source: Transportation Security Administration (TSA); Federal Register; DHS publications
https://www.tsa.gov/sd-and-ea

Note: TSA Security Directives are classified as Sensitive Security Information (SSI). Full directive text is not publicly available. This reference is based on publicly disclosed summaries, Federal Register notices, and TSA press releases.

---

## Overview

Following the May 2021 Colonial Pipeline ransomware attack, TSA issued mandatory cybersecurity Security Directives requiring critical transportation infrastructure owners and operators to implement baseline cybersecurity measures. These directives have been updated through multiple revisions and now cover pipelines, freight rail, passenger rail, public transit, and (via NPRM) bus operators.

Directives are renewed annually and carry the force of law under 49 U.S.C. § 114. Non-compliance can result in civil penalties. Each directive identifies specific "covered entities" by name - not all operators in a sector are automatically covered.

---

## Pipeline Security Directives

### SD Pipeline-2021-01 Series - Immediate Measures
**Purpose**: Established minimum immediate cybersecurity requirements for pipeline operators following the Colonial Pipeline incident.

**Current revision**: Pipeline-2021-01G (effective January 2026; in effect through January 15, 2027)

| Revision | Issued | Key Changes |
|----------|--------|-------------|
| Pipeline-2021-01 | May 2021 | Initial directive: incident reporting, coordinator, practices review |
| Pipeline-2021-01A | July 2021 | Minor clarifications |
| Pipeline-2021-01B/C | 2022–2023 | Renewed with refinements |
| Pipeline-2021-01D | May 2024 | Extended; clarified applicability and reporting requirements |
| Pipeline-2021-01E | 2025 | Extended; additional clarifications |
| Pipeline-2021-01F | 2025 | Renewed; extended the series pending the final rule |
| Pipeline-2021-01G | January 2026 | Current revision; in effect through January 15, 2027 |

**Core requirements of SD Pipeline-2021-01 series**:
1. Report cybersecurity incidents to CISA within 24 hours
2. Designate a Cybersecurity Coordinator (24/7 availability; backup designee)
3. Review current cybersecurity practices and identify gaps relative to TSA/CISA guidance
4. Develop and implement remediation measures to address identified gaps

**Covered entities**: Owners and operators of TSA-designated critical hazardous liquid and natural gas pipelines and LNG facilities.

---

### SD Pipeline-2021-02 Series - Comprehensive CRMP
**Purpose**: Established comprehensive Cyber Risk Management Program requirements for pipeline operators.

**Current revision**: Pipeline-2021-02F (latest)

| Revision | Issued | Key Changes |
|----------|--------|-------------|
| Pipeline-2021-02 | July 2021 | Initial comprehensive CRMP requirements |
| Pipeline-2021-02A/B | 2021–2022 | Renewals and refinements of the prescriptive requirements |
| Pipeline-2021-02C | July 2022 | Performance-based rewrite; replaced prescriptive controls with outcome-focused CRMP requirements |
| Pipeline-2021-02D | 2023 | Further refinements; feedback incorporated from operators |
| Pipeline-2021-02E | July 2024 | Extended; strengthened; additional clarity on OT/IT requirements |
| Pipeline-2021-02F | 2025/2026 | Current revision |

**Core requirements of SD Pipeline-2021-02 series**:
1. **Cybersecurity Implementation Plan (CIP)**: Submit to TSA for review and approval
2. **Cybersecurity Incident Response Plan (IRP/CIRP)**: Document + test two objectives annually
3. **Architecture Design Review (ADR)**: Annual review of IT/OT network architecture
4. **Cybersecurity Assessment Plan (CAP)**: Annual assessment + results reported to TSA
5. **Four technical domains**: Network segmentation, access controls, continuous monitoring, patch management
6. **Accountable Executive**: C-suite individual with authority for cybersecurity decisions

**Sensitive Security Information (SSI)**: The full text of SD Pipeline-2021-02 and its revisions is SSI. Covered entities receive the directive directly from TSA.

---

## Freight Rail Security Directives

### SD 1580-21-01 Series - "Enhancing Rail Cybersecurity" (Baseline Duties)
**Purpose**: Establishes the baseline cybersecurity duties for freight railroad carriers: cybersecurity coordinator, incident reporting, incident response plan, and vulnerability assessment.

**Current revision**: SD 1580-21-01C (October 23, 2024)

| Revision | Issued | Key Changes |
|----------|--------|-------------|
| SD 1580-21-01 | December 2021 | Initial rail cybersecurity baseline: incident reporting, coordinator, incident response plan, vulnerability assessment |
| SD 1580-21-01A/B | 2022–2023 | Renewals with refinements |
| SD 1580-21-01C | October 23, 2024 | Current revision |

**Core requirements of SD 1580-21-01 series** (baseline duties only):
1. Report cybersecurity incidents to CISA within 24 hours
2. Designate a Cybersecurity Coordinator (24/7)
3. Develop and adopt a cybersecurity incident response plan
4. Complete a cybersecurity vulnerability assessment

**Covered entities**: TSA-designated freight railroad owners and operators with higher cybersecurity risk profiles. Includes Class I railroads and potentially higher-risk Class II/III operations.

> **Note**: The CRMP, Cybersecurity Implementation Plan, and assessment-program requirements for rail do NOT live in this series - they are carried by the SD 1580/82-2022-01 series below.

---

### SD 1580/82-2022-01 Series - "Rail Cybersecurity Mitigation Actions and Testing" (CRMP/CIP)
**Purpose**: Carries the comprehensive rail cybersecurity program requirements for both freight railroads (1580) and passenger rail/transit (1582): the four-domain mitigation measures, Cybersecurity Implementation Plans, and assessment programs.

**Issued**: October 24, 2022

**Current revision**: SD 1580/82-2022-01D (effective May 3, 2025)

| Revision | Issued | Key Changes |
|----------|--------|-------------|
| SD 1580/82-2022-01 | October 24, 2022 | Initial performance-based rail CRMP: four technical domains, CIP, assessment program |
| SD 1580/82-2022-01A/B/C | 2023–2024 | Renewals with refinements |
| SD 1580/82-2022-01D | Effective May 3, 2025 | Current revision |

**Core requirements of SD 1580/82-2022-01 series**:
1. Implement the four technical mitigation domains: network segmentation, access controls, continuous monitoring and detection, patch management
2. **Cybersecurity Implementation Plan (CIP)**: Submit to TSA for approval; identify Critical Cyber Systems
3. **Cybersecurity Assessment Program**: Annual plan and reporting to TSA on assessment of CRMP effectiveness
4. Specific attention to ICS/SCADA systems controlling rail operations (switches, signals, dispatch)

**Covered entities**: TSA-designated freight railroads, passenger railroads, and rail transit systems with higher cybersecurity risk profiles.

---

## Public Transportation and Passenger Rail Security Directives

### SD 1582-21-01 Series - "Enhancing Rail Cybersecurity" (Baseline Duties)
**Purpose**: Establishes the baseline cybersecurity duties for public transportation agencies and passenger railroad operators.

**Current revision**: SD 1582-21-01C (October 23, 2024)

| Revision | Issued | Key Changes |
|----------|--------|-------------|
| SD 1582-21-01 | December 2021 | Initial transit cybersecurity baseline: incident reporting, coordinator, incident response plan, vulnerability assessment |
| SD 1582-21-01A/B | 2022–2023 | Renewals with refinements |
| SD 1582-21-01C | October 23, 2024 | Current revision |

**Core requirements of SD 1582-21-01 series** (baseline duties only): Same structure as SD 1580-21-01 - 24-hour CISA incident reporting, Cybersecurity Coordinator, incident response plan, vulnerability assessment. The CRMP/CIP/assessment-program requirements for passenger rail and transit are carried by the SD 1580/82-2022-01 series above.

**Covered entities**: TSA-designated public transportation agencies (metro, light rail, commuter rail, bus rapid transit) and passenger railroad operators (Amtrak and designated commuter rail agencies).

**OT focus for transit**: Automatic Train Control (ATC) systems, SCADA for traction power and ventilation, Communications-Based Train Control (CBTC), Electronic Ticketing Systems (where they interface with operational systems), CCTV/access control integration.

---

## Aviation Cybersecurity

Aviation cybersecurity directives are issued separately by TSA to airport operators and aircraft operators. These are largely SSI and address:
- Incident reporting to CISA within 24 hours
- Cybersecurity Coordinator designation
- Access controls for aviation systems
- Network segmentation between passenger and operational networks
- Passenger screening system security

The aviation sector also operates under FAA cybersecurity requirements for aircraft systems, which are distinct from TSA directives.

---

## November 2024 NPRM - Proposed Permanent Rule

**Title**: "Enhancing Surface Cyber Risk Management"
**Published**: 89 FR 88488 (November 7, 2024); RIN 1652-AA74
**Comment period**: Closed February 5, 2025

### What the NPRM proposes:
The NPRM would formalise current Security Directive requirements into permanent federal regulations under 49 CFR, making them enforceable as regulation rather than directive.

**Proposed covered entities**:
| Sector | Coverage |
|--------|---------|
| Pipelines | Same as current directives; higher-risk designated operators |
| Freight railroad | Higher-risk Class I and designated Class II/III |
| Passenger rail/transit | Higher-risk passenger rail and transit agencies |
| Bus operators | Incident reporting requirements only (less prescriptive) |

**Three core proposed requirements**:
1. **Annual Cybersecurity Evaluation**: Enterprise-wide evaluation comparing current profile vs target profile (explicitly using NIST CSF 2.0 as the framework)
2. **Cybersecurity Operational Implementation Plan (COIP)**: TSA-approved plan (equivalent to current CIP) with accountable executive, CCS inventory, network architecture description, and measures for all four domains
3. **Cybersecurity Assessment Plan (CAP)**: Annual assessment schedule and reporting to TSA

**Framework alignment**:
- **NIST CSF 2.0**: Primary framework for the annual profile-based evaluation
- **CISA Cross-Sector Cybersecurity Performance Goals (CPGs)**: Baseline performance measures referenced in the NPRM
- CPGs are grouped into IT and OT goals and map closely to NIST CSF subcategories

**Status as of 2026**: Comment period closed; final rule not yet published. Current Security Directives remain in force.

---

## Relationship to Other Frameworks

| Framework | Relationship to TSA Directives |
|-----------|-------------------------------|
| **NIST CSF 2.0** | Referenced in 2024 NPRM for annual profile evaluation; GV/ID/PR/DE/RS/RC maps to TSA domains |
| **CISA CPGs** | Baseline goals for critical infrastructure; TSA directives align with IT and OT CPGs |
| **NIST SP 800-82** | Guide to ICS/OT security; informative reference for implementing TSA's OT requirements |
| **NERC CIP** | Electric sector parallel; some operators subject to both TSA and NERC CIP |
| **IEC 62443** | OT/ICS security standard; applicable for implementing TSA's Domain 1–4 requirements |
| **NIST SP 800-53** | Federal controls; FedRAMP-covered systems within covered entities may have dual obligations |

---

## Key Definitions

| Term | Definition |
|------|-----------|
| **Critical Cyber System (CCS)** | IT or OT system whose compromise could disrupt operations, safety, or security |
| **Cybersecurity Coordinator** | 24/7 designated contact person for TSA and CISA |
| **CIP / COIP** | Cybersecurity Implementation Plan / Cybersecurity Operational Implementation Plan |
| **IRP / CIRP** | (Cybersecurity) Incident Response Plan |
| **ADR** | Architecture Design Review - annual IT/OT network architecture assessment |
| **CAP** | Cybersecurity Assessment Plan - annual CRMP effectiveness assessment |
| **CRMP** | Cyber Risk Management Program - the collective set of CIP, IRP, ADR, CAP requirements |
| **SSI** | Sensitive Security Information - information protected under 49 CFR Part 1520 |
| **OT** | Operational Technology - hardware/software controlling physical industrial processes |
| **ICS** | Industrial Control System - subset of OT |
| **SCADA** | Supervisory Control and Data Acquisition - OT system for monitoring/controlling distributed assets |
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall