Meet TSA cybersecurity directives and protect supply chain infrastructure. FrameworkMapper maps your security controls against NIST CSF v2 and CIS Controls — the frameworks TSA directives reference.
Why This Matters
TSA has issued mandatory cybersecurity directives for pipeline, rail, and aviation operators — with NIST CSF as the reference framework.
TSA has issued binding cybersecurity directives for pipeline, rail, and aviation operators since 2021
TSA Security Directives
Colonial Pipeline ransomware attack disrupted fuel supply across the Eastern U.S. in 2021
Documented incident
TSA directives require NIST CSF-aligned cybersecurity controls and incident reporting from covered operators
TSA requirement
Supply chain cyberattacks targeting logistics networks can cascade disruption across multiple sectors
Systemic risk
Recommended Frameworks
FrameworkMapper supports all three frameworks below, with transportation sector prioritization built in.
| Framework | Why It Applies | Status |
|---|---|---|
| NIST CSF v2 | Referenced directly in TSA security directives for pipeline, rail, and aviation sectors | Strongly Recommended (TSA-covered) |
| CIS Controls v8.1 | Practical implementation path complementing NIST CSF for transportation operators | Strongly Recommended |
| NIST SP 800-53 | Applicable for transportation operators with federal contracts or under DHS oversight | Conditional |
How FrameworkMapper Helps
Visualize how your existing security tools and controls address the NIST CSF subcategories referenced in TSA security directives — a critical step before a TSA audit.
Launch AggregatorToolMapper surfaces tools relevant for transportation IT/OT environments with analyst coverage from Gartner and Forrester.
Launch ToolMapperNIST CSF assessments produce structured reports documenting your control implementation — useful for TSA compliance demonstrations and executive reporting.
View AssessmentsThe Universal Control Prioritization Algorithm uses seven factors, each weighted to reflect the realities of transportation security programs. Transportation & Logistics currently uses the SLTT (V06) weight profile as a proxy — a dedicated Transportation profile (V12) is on the FrameworkMapper roadmap.
| Factor | Weight | What This Means |
|---|---|---|
| T Threat Relevance | 0.20 | Controls targeting ransomware, OT intrusion, and supply chain attacks facing transportation operators score higher |
| D Dependency Score | 0.15 | Foundation controls enabling others across IT and OT environments are prioritized |
| E Effort-to-Value | 0.15 | High-impact controls relative to implementation cost are surfaced earlier in the roadmap |
| B Blast Radius | 0.15 | Controls preventing supply chain disruptions or multi-sector cascading incidents receive a boost |
| R Regulatory Criticality | 0.20 | Significant weight due to binding TSA security directives for pipeline, rail, and aviation operators |
| C Coverage Breadth | 0.10 | Controls addressing multiple attack vectors across IT and OT environments are prioritized |
| A Asset Exposure | 0.05 | Controls protecting critical transportation assets and operational systems weighted accordingly |
For Transportation & Logistics, Regulatory Criticality carries significant weight due to binding TSA directives. Threat Relevance is equally weighted given the critical infrastructure status of transportation systems and the demonstrated impact of attacks like Colonial Pipeline.
Read the Full UCPA MethodologyStart free with the Coverage Aggregator or run a full NIST CSF assessment to document your compliance with TSA security directives.