Meet TSA SD 1580/82-2022-01 rail cyber rules with evidence ready
TSA SD 1580/82-2022-01 is the Transportation Security Administration's security directive on Rail Cybersecurity Mitigation Actions and Testing, first issued in October 2022. It requires covered railroads to identify their Critical Cyber Systems and implement a TSA-approved Cybersecurity Implementation Plan for network segmentation, access control, continuous monitoring and patch management. Operators must also run a Cybersecurity Assessment Program that tests whether those measures work.
Is TSA SD 1580/82-2022-01 right for your organisation?
The directive applies to freight railroad carriers identified in 49 CFR 1580.101 and to other freight and passenger railroads that TSA designates based on risk. It sits alongside the earlier rail directives SD 1580-21-01 and SD 1582-21-01, which cover incident reporting, a cybersecurity coordinator and incident response planning. Suppliers and managed security providers serving these railroads often need to support the same controls, although the operator keeps responsibility for compliance.
It is a legal or regulatory requirement for organisations in scope.
- Issued by
- Transportation Security Administration (TSA), US Department of Homeland Security
- First issued
- 18 October 2022, effective 24 October 2022
- Current version
- SD 1580/82-2022-01E, effective 3 May 2026 to 2 May 2027
- Applies to
- Freight railroads in 49 CFR 1580.101 and other TSA-designated freight and passenger railroads
- Core deliverables
- TSA-approved Cybersecurity Implementation Plan and an annual Cybersecurity Assessment Plan
- Assessment cycle
- All cybersecurity measures assessed within a three-year period, with annual reporting to TSA
- Legal basis
- Issued under 49 U.S.C. 114(l)(2) and ratified by the Transportation Security Oversight Board
- Type
- Regulation (mandatory)
- Region
- United States, US
- In OneClickComply
- Supported today
OneClickComply makes it simple
TSA SD 1580/82-2022-01 is mapped in OneClickComply's control library and is available on request, rather than live as a standard framework today. Once enabled, the IT side of your Critical Cyber Systems can be evidenced through direct integrations and continuous monitoring for access control, MFA, logging and patching, with controls shared across frameworks such as NIST CSF and ISO 27001. Our in-house audit team can help you structure the Cybersecurity Implementation Plan and assessment evidence that TSA expects.
Requirements covered
Security outcomes are set out in Section III: identify Critical Cyber Systems (III.A), network segmentation (III.B), access control (III.C), continuous monitoring and detection (III.D) and patch management (III.E), supported by a Cybersecurity Assessment Program and compliance documentation requirements.
Manual TSA SD 1580/82-2022-01 vs. OneClickComply
- Mapping every Critical Cyber System and its IT and OT dependencies in spreadsheets
- Writing and updating a Cybersecurity Implementation Plan by hand each time the directive is reissued
- Chasing screenshots of MFA, shared account and domain trust settings across tools
- Tracking patch timelines and KEV catalogue items with no single view of risk
- Rebuilding evidence every year to show TSA that measures were assessed and work
- One asset register links Critical Cyber Systems to owners, data flows and controls
- Policies generated from your real environment keep the plan aligned with how you operate
- Integrations collect access control and MFA evidence automatically and flag drift
- Continuous monitoring surfaces unpatched and known exploited vulnerabilities for action
- Evidence collected once is stored and reused for each annual assessment cycle
Everything you need for TSA SD 1580/82-2022-01
Critical Cyber System inventory with owners, dependencies and external connections
Continuous monitoring of IT access control, MFA and shared account use
Patch and vulnerability tracking with CISA Known Exploited Vulnerabilities prioritised
Logging and alerting evidence for continuous monitoring and detection
Policy generation for segmentation, access, monitoring and patch management
Assessment evidence and penetration testing support for your Cybersecurity Assessment Program
Three steps to TSA SD 1580/82-2022-01 compliance
Connect & scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against TSA SD 1580/82-2022-01 and shows you exactly where you stand.
Fix & generate
OneClickFix remediates technical gaps in one click, and AutoComplete generates TSA SD 1580/82-2022-01-aligned policies from your real environment.
Monitor & evidence
Continuous monitoring keeps you compliant, and our in-house audit team is on hand when you need expert guidance.
TSA Security Directive 1580/82-2022-01: Rail Cybersecurity Mitigation Actions and Testing requirements
The security outcomes of the directive's Section III with their numbered sub-requirements, plus the plan, assessment and documentation obligations; definitions and administrative provisions are not listed.
| Reference | Requirement |
|---|---|
| II.B | Develop, submit and implement a TSA-approved Cybersecurity Implementation Plan |
| III.A | Identify Critical Cyber Systems |
| III.B | Network segmentation policies and controls |
| III.B.1 | IT and OT interdependencies, external connections, zone boundaries and related policies |
| III.B.2 | Measures to secure and defend zone boundaries |
| III.C | Access control measures for Critical Cyber Systems |
| III.C.1 | Identification and authentication policies and procedures |
| III.C.2 | Multi-factor authentication or other logical and physical security controls |
| III.C.3 | Access rights based on least privilege and separation of duties |
| III.C.4 | Limits on the availability and use of shared accounts |
| III.C.5 | Regular review of domain trust relationships |
| III.D | Continuous monitoring and detection policies and procedures |
| III.D.1 | Capabilities to block malicious email, domains, code and command and control traffic |
| III.D.2 | Procedures to audit access, IT and OT communications and unauthorised code |
| III.D.3 | Logging policies for continuous collection and analysis of data |
| III.D.4 | Mitigation measures or manual controls to isolate industrial control systems |
| III.E | Patch management for Critical Cyber Systems |
| III.E.1 | Patch management strategy keeping critical security patches current |
| III.E.2 | Risk methodology, implementation timelines and KEV catalogue prioritisation |
| III.E.3 | Additional mitigations where OT systems cannot be patched |
Always check the official TSA SD 1580/82-2022-01 text for the exact wording.
TSA SD 1580/82-2022-01 FAQs
What is TSA Security Directive 1580/82-2022-01?
TSA Security Directive 1580/82-2022-01 is a mandatory cybersecurity directive for US railroads titled Rail Cybersecurity Mitigation Actions and Testing. First issued in October 2022, it requires covered operators to identify Critical Cyber Systems, implement a TSA-approved Cybersecurity Implementation Plan for segmentation, access control, monitoring and patching, and run a Cybersecurity Assessment Program that tests those measures. TSA reissues it periodically with lettered revisions.
Who must comply with TSA SD 1580/82-2022-01?
The directive applies to freight railroad carriers identified in 49 CFR 1580.101 and to other freight and passenger railroads that TSA designates. In practice this covers major freight railroads and higher-risk passenger rail operators. If TSA has not notified your organisation that it is covered, you are not directly bound, although customers that are covered may expect suppliers to support the same controls.
What is the current version of the directive?
The current version is SD 1580/82-2022-01E, which TSA states is effective from 3 May 2026 to 2 May 2027 and supersedes 01D. Earlier revisions included 01A in October 2023, 01B in May 2024 and the corrected 01C in July 2024, which brought Positive Train Control systems within the scope of Critical Cyber Systems. Always check TSA's security directives page for the latest revision.
What does the Cybersecurity Implementation Plan have to cover?
The plan must describe how the operator meets each security outcome in Section III: identifying Critical Cyber Systems, network segmentation so operational technology can keep running if IT is compromised, access control including multi-factor authentication and least privilege, continuous monitoring and detection, and a risk-based patch management strategy that prioritises CISA's Known Exploited Vulnerabilities catalogue. TSA must approve the plan, and the operator must then implement it on the agreed schedule.
What is the Cybersecurity Assessment Program?
The Cybersecurity Assessment Program is the directive's testing requirement. Operators must proactively assess whether the measures in their implementation plan are effective, including an architecture design review of the network and additional testing such as penetration testing. Since the 01A revision, the assessment plan is reviewed and submitted to TSA annually, and all cybersecurity measures must be assessed within a three-year period, with results reported to TSA.
What happens if a railroad does not comply?
Security directives issued under 49 U.S.C. 114(l)(2) are binding on covered owners and operators, and TSA inspects compliance and can take enforcement action, which may include civil penalties. The directive also requires operators to make records available to TSA to demonstrate compliance. Using a managed security service provider does not transfer responsibility: the operator remains accountable for meeting every requirement.
How does TSA SD 1580/82-2022-01 relate to NIST CSF and ISO 27001?
The directive is performance based and does not require certification to any standard, but TSA's informational supplement maps its requirements to the NIST Cybersecurity Framework and NIST SP 800-53 controls. Organisations already running an ISO 27001 or NIST CSF programme will find strong overlap in access control, logging and vulnerability management, though the directive adds rail-specific expectations around IT and OT segmentation and TSA plan approval.
Does OneClickComply support TSA SD 1580/82-2022-01?
Yes, on request. TSA SD 1580/82-2022-01 is mapped in OneClickComply's control library and can be enabled for your organisation, but it is not yet a live framework in the product. Once enabled, evidence collected for overlapping controls in frameworks such as NIST CSF or ISO 27001 counts towards it, and our audit team can advise on your implementation and assessment plans.
Related standards
All standards- HIPAA Administrative Simplification RegulationsRegulation · US
- NISPOM (32 CFR Part 117)Regulation · US
- NYDFS Cybersecurity Regulation (23 NYCRR Part 500)Regulation · US
- HIPAA Security RuleRegulation · US
- Unclassified Naval Nuclear Propulsion Information (U-NNPI)Regulation · US
- FTC Safeguards Rule (GLBA, 16 CFR Part 314)Regulation · US
- 45 CFR 155.260 (ACA Exchange Privacy and Security)Regulation · US
- FINRA Cybersecurity RequirementsRegulation · US
Products that power TSA SD 1580/82-2022-01 compliance
Get TSA SD 1580/82-2022-01 ready, not stressed
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.