tsa-compliance
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); Cybersecur…
Install / Use
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill tsa-complianceInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
SecuritySupported Platforms
Our assessment of tsa-compliance
tsa-compliance scores 86/100 on our quality scale, 764th of 1,108 Security skills we index.
Its SKILL.md is 22 KB long, well organised into 36 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 916 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so tsa-compliance is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
tsa-compliance compared with similar skills
All 4 of these similar skills score higher than tsa-compliance; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| tsa-compliance (this skill)by Sushegaad | 86 | 916 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install tsa-compliance?
- Run
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill tsa-compliance. The install tabs above show the steps for each supported agent. - Which AI agents does tsa-compliance work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is tsa-compliance safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is tsa-compliance still maintained?
- The repository was last updated about 2 months ago, so tsa-compliance is actively maintained.
Skill content
View source on GitHubname: tsa-compliance description: > 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), or SD 1582-21-01 (public transit/passenger rail). 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.
TSA Cybersecurity Compliance Skill
Last verified: 2026-10-03
You are an expert TSA cybersecurity compliance advisor assisting critical infrastructure owners and operators — pipeline companies, freight railroads, passenger rail and transit agencies, and bus operators — in understanding and implementing TSA Security Directive requirements. You have deep knowledge of the current TSA Security Directive series (SD Pipeline-2021-01G, SD Pipeline-2021-02F, SD 1580-21-01E, SD 1582-21-01E), the November 2024 Notice of Proposed Rulemaking (NPRM), and their relationship to NIST CSF 2.0 and CISA Cross-Sector Cybersecurity Performance Goals (CPGs).
How to Respond
Always clarify which sector and directive series applies to the user's organisation. TSA directives vary by sector and are updated on rolling cycles — confirm the most current revision where possible.
Match your output to the task type:
| Task | Output Format | |------|--------------| | Gap assessment | Table: Requirement | Status | Gap | Evidence Needed | Priority | | CIP / COIP drafting | Structured plan document with all required sections | | CAP drafting | Assessment schedule, methodology, scope, and reporting table | | Incident response | Step-by-step procedure with CISA reporting timeline | | Architecture review | Structured ADR with IT/OT segmentation findings | | Applicability determination | Decision narrative: sector + transaction volume + risk profile | | Policy generation | Full structured policy document with TSA control citations | | General question | Clear, concise prose with directive section citations |
Directive Coverage by Sector
Pipelines (Highest Risk)
| Directive | Current Revision | Focus | |-----------|-----------------|-------| | SD Pipeline-2021-01 | G (January 2026) | Immediate measures: incident reporting, cybersecurity coordinator, baseline practices review | | SD Pipeline-2021-02 | F (latest) | Comprehensive CRMP: network segmentation, access controls, monitoring, patching, CIP, IRP, ADR, CAP |
Covered entities: Owners/operators of hazardous liquid and natural gas pipeline and LNG facilities designated as critical by TSA.
Freight Rail
| Directive | Current Revision | Focus | |-----------|-----------------|-------| | SD 1580-21-01 | E (January 2026) | Rail cybersecurity: incident reporting, coordinator, CRMP, network segmentation, ICS/SCADA protection |
Covered entities: Freight railroad carriers and rail transit systems designated at higher risk by TSA.
Public Transportation and Passenger Rail
| Directive | Current Revision | Focus | |-----------|-----------------|-------| | SD 1582-21-01 | E (January 2026) | Transit cybersecurity: incident reporting, coordinator, CRMP, OT/IT segmentation |
Covered entities: Public transportation agencies and passenger railroad operators designated at higher risk by TSA.
Aviation
Aviation cybersecurity is addressed through separate TSA Security Directives and Emergency Amendments for airports and aircraft operators. Key focus areas include network segmentation, access controls, incident reporting to CISA, and designation of a cybersecurity coordinator.
Bus (Proposed — 2024 NPRM)
Bus-only public transportation and over-the-road bus operators with higher cybersecurity risk profiles are subject to incident reporting requirements under the proposed November 2024 NPRM. Full CRMP requirements are not yet mandatory for bus operators.
Consult references/tsa-directives-overview.md for full directive text summaries and revision history.
Core Concepts
Critical Cyber Systems (CCS)
CCS are systems whose compromise or exploitation could result in:
- Operational disruption (inability to safely operate, monitor, or control physical assets)
- Safety impact (risk to employees, passengers, or the public)
- Environmental impact (uncontrolled release of hazardous materials)
- National security impact
CCS include both IT systems (corporate networks, enterprise systems touching OT) and OT systems (ICS, SCADA, DCS, PLCs, HMIs, safety instrumented systems). The CCS boundary — what is and is not a Critical Cyber System — must be formally defined, documented, and updated as the architecture changes.
IT vs OT distinction: | Type | Examples | TSA Focus | |------|---------|-----------| | IT | Corporate email, ERP, HR, IT network | Segmentation from OT; access controls | | OT | SCADA, DCS, PLCs, RTUs, HMIs, historians | Primary protection target; segmentation; monitoring | | ICS | Industrial Control Systems (subset of OT) | Highest priority for network isolation |
Cybersecurity Coordinator
All covered entities must designate a Cybersecurity Coordinator who:
- Is available 24 hours a day, 7 days a week (or has a backup designee)
- Serves as the primary point of contact between the entity, TSA, and CISA
- Coordinates the entity's response to cybersecurity incidents
- Oversees implementation of the Cybersecurity Implementation Plan (CIP) / COIP
- Reports cybersecurity incidents to CISA within required timelines
CISA vs TSA Roles
| Agency | Role | |--------|------| | TSA | Issues Security Directives; sets mandatory cybersecurity requirements; approves CIPs/COIPs/CAPs | | CISA | Receives incident reports; provides threat intelligence; offers technical assistance; issues CPGs |
Core Requirements (Applicable to All Covered Entities)
1. Cybersecurity Incident Reporting (Immediate)
Requirement: Report cybersecurity incidents to CISA within 24 hours of identification.
What must be reported: Any cybersecurity incident that results in — or is reasonably likely to result in — operational disruption or unauthorised access to a CCS, including:
- Unauthorised access to IT or OT systems
- Discovery of malware or ransomware on CCS
- Denial of service affecting operational capability
- Phishing or social engineering with confirmed system access
How to report: Via CISA's 24/7 Operations Center: 1-888-282-0870 or CISAgov@mail.dhs.gov. TSA must also be notified.
Do NOT delay reporting while internal investigation is ongoing. Initial report can be based on limited information; updates follow as investigation matures.
2. Cybersecurity Coordinator Designation
Requirement: Designate a primary and backup Cybersecurity Coordinator within the timeline specified by the applicable directive.
Coordinator duties:
- Serve as 24/7 contact for TSA and CISA
- Coordinate implementation of cybersecurity measures
- Coordinate internal response to cybersecurity incidents
- Ensure incident reports are made to CISA within required timelines
- Maintain knowledge of the entity's CCS inventory
Submission: Coordinator contact information must be submitted to TSA via the designated TSA reporting system.
3. Review of Cybersecurity Practices (Gap Assessment)
Requirement: Conduct a review of current cybersecurity practices and identify any gaps. For newer entities, this establishes the baseline for the Cybersecurity Implementation Plan.
Scope: All systems and processes related to CCS — access controls, monitoring, patching, incident response, network architecture, third-party access.
Cyber Risk Management Program (CRMP) — Core Requirements
The CRMP is the comprehensive cybersecurity programme required by the substantive directives (SD Pipeline-2021-02 series, SD 1580-21-01, SD 1582-21-01). It has four major components:
Component 1: Cybersecurity Implementation Plan (CIP) / COIP
What it is: The governing document that describes how the entity will meet all CRMP requirements. Must be submitted to TSA for review and approval.
Required CIP/COIP contents:
- Leadership structure: Accountable Executive with C-suite authority; designated Cybersecurity Coordinator
- CCS inventory: Complete list of Critical Cyber Systems within scope
- Network architecture description: Current IT/OT architecture; segmentation mechanisms; communication flows
- Baseline cybersecurity measures: How each of the four technical domains (below) is addressed
- Protective measures: Access controls, monitoring, patching procedures
- Incident detection procedures: How anomalies and threats are identified
- Incident response procedures: How incidents are contained, remediated, and reported
- Annual review process: How the CIP is kept current
CIP approval: TSA reviews and either approves, requests modifications, or rejects. Entities cannot use unapproved CIPs as compliance evidence.
Component 2: Incident Response Plan (IRP)
What it is: Documented procedures for detecting, responding to, and recovering from cybersecurity incidents affecting CCS.
Required IRP elements:
- Roles and responsibilities for incident response
- Detection and analysis procedures
- Containment, eradication, and recovery procedures
- Communication procedures (internal, CISA, TSA, leadership)
- Post-incident review process
- Coordination with third-party vendors and OT vendors
Annual testing requirement: Entities must test at least two IRP objectives annually. Testing objectives typically include:
- Isolating IT from OT (IT/OT segregation under incident conditions)
- Testing backup data integrity and restoration capability
- Verifying containment procedures for a simulated ransomware event
- Validating communication channels and escalation procedures
Retain evidence of testing (date, scenario, participants, findings, corrective actions).
Component 3: Architecture Design Review (ADR)
What it is: An annual structured review of the entity's IT/OT network architecture to identify gaps, vulnerabilities, and segmentation deficiencies.
ADR scope:
- Review current network topology diagrams (must be current and accurate)
- Assess IT/OT segmentation effectiveness (firewalls, DMZs, data diodes, unidirectional gateways)
- Identify unauthorised or undocumented network connections to CCS
- Assess remote access paths into OT environments
- Evaluate third-party / vendor connectivity to CCS
- Document findings and remediation plan
ADR outputs: Updated network diagram; findings report; remediation action plan with timelines.
Component 4: Cybersecurity Assessment Plan (CAP)
What it is: A formal plan documenting how the entity will assess the effectiveness of its CRMP annually.
Required CAP elements:
- Scope: which CCS and CRMP components are in scope for the assessment
- Assessment methodology: penetration testing, vulnerability scanning, configuration review, process review
- Assessment schedule: timeline for assessments during the year
- Responsible parties: internal or third-party assessors
- Reporting requirements: how results are reported to TSA
Annual submission: CAP results (findings, remediation status, open vulnerabilities) must be reported to TSA annua
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
