- Biggest threats in the industry
- Real-world cyberattacks
- How to reduce risk
- Cybersec challenges
- Rules and standard guide
- Resources for cybersec teams
- FAQs
- References
Transportation cybersecurity protects the networks, software, devices and operational systems used to move passengers and freight.
It covers ordinary business systems—such as payments and reservations—and digital processes that support dispatch, terminals, equipment monitoring and other essential services. A cyberattack can interrupt operations without compromising the vehicles themselves.
U.S. transportation infrastructure includes aviation, trucking and highway transport, maritime systems, mass transit and passenger rail, freight rail, pipelines, and postal and shipping services. Each has different operating conditions and applicable oversight.
What are the biggest cybersecurity threats to transportation?
Ransomware and data theft. Attackers may encrypt essential systems, steal information or do both. Restoring backups can help resume operations, but cannot reverse a data leak.
Stolen accounts and payment fraud. Phishing, credential theft and impersonation can expose systems or redirect logistics payments and freight instructions. Strong authentication and independent verification of payment changes reduce these risks.
Vendor and remote-access compromise. Equipment suppliers, cloud tools and contractors may be able to reach sensitive networks. Unnecessary privileges and unmonitored connections create pathways for intrusion.
Vulnerable applications and connected devices. Exposed portals, APIs, fleet telematics, electronic logging devices and aging systems all require attention appropriate to their criticality.
Service-disruption and operational risks. Denial-of-service attacks can interrupt websites or online services. OT attacks can have more serious consequences when devices monitor or control physical processes. Such outcomes must be confirmed, not inferred from an incident headline.
| Transportation mode | Systems at risk | Likely service consequence |
|---|---|---|
| Rail and transit | Dispatch support, customer service, fare systems | Service delays, disrupted rider services |
| Ports and maritime | Container/gate applications, terminal equipment | Backlogs and interrupted freight releases |
| Trucking and shipping | Fleet platforms, tracking, freight accounts | Reduced visibility, dispatch and payment fraud |
| Pipelines | Industrial monitoring and remote controls | Operational visibility or continuity risks |
Information technology (IT) supports enterprise applications and data. Operational technology (OT) monitors or influences physical processes.
OT security therefore requires equipment-aware controls and change management rather than assuming all devices can be patched or scanned like ordinary office computers.
Real-world transportation cyberattacks
Estes Express Lines, 2023. A breach notification lists a September 26 intrusion, discovered October 1, and 21,184 affected individuals. Names and Social Security numbers were among the information involved. The case highlights data protection needs in freight operations.
DP World Australia, November 2023. The operator disconnected its Australian corporate network after unauthorized access on November 10, disrupting landside port operations. It resumed operations November 13 and cleared a 30,137-container backlog by November 20. DP World said no ransomware was deployed. The case shows that containment can have immediate logistics consequences.
Port of Seattle, August 24, 2024. The Port attributed its ransomware incident to Rhysida. It reported disruptions to baggage-related and passenger-facing systems at Seattle-Tacoma International Airport, but stated that safe travel and major airline and federal partner systems were not affected. Some employee- and contractor-related personal data was later identified as exposed.
Pittsburgh Regional Transit, December 19, 2024. PRT detected ransomware, reported temporary rail disruption and customer-service problems involving Senior and Kid’s ConnectCards, and later disclosed theft of certain staff and applicant information, including Social Security and driver’s license numbers. The agency activated incident-response resources, investigators and law enforcement.
Hartsfield-Jackson Atlanta International Airport, March 28, 2025. Airport officials described a brief denial-of-service-related website disruption with no effect on airport operations. It is a reminder to distinguish an online outage from a safety-system failure.
Related resources
Why is transportation cybersecurity challenging?
Operators depend on geographically distributed networks, specialist equipment, third-party support and systems that may have limited maintenance windows. A failure in one system can affect passengers, cargo, vendors and other critical infrastructure.
Some operational assets cannot use conventional endpoint software or be updated without testing. Security measures must account for the need to maintain safe services while responding to an incident.
How can operators reduce cyber risk?
- Know what must keep running. Inventory critical services and map their dependence on identity, communications, vendors, cloud applications and OT.
- Control access and separation. Use appropriate multifactor authentication, least privilege and segmentation between corporate IT, vendor pathways and sensitive operational environments.
- Secure compatible endpoints. Deploy appropriate anti-malware tools and monitoring on supported devices; use validated alternative controls for constrained OT equipment.
- Prioritize and test patches. Fix high-risk exposure, but follow operational change controls and vendor guidance for industrial systems.
- Make recovery real. Maintain protected offline or immutable backups where suitable, verify restoration and prepare safe fallback operations. Backups do not prevent data exfiltration.
- Rehearse the response. Include security, operations, engineering, safety and communications teams; define how to report incidents and inform passengers or customers.
- Protect freight workflows. Independently verify payment-account and pickup changes; watch for compromised supplier and carrier identities.
- Train staff in context. Teach phishing reporting and role-specific fraud detection, without treating awareness training as a replacement for technical protections.
The best starting point for a smaller operator is a short, tested plan identifying essential systems, remote-access suppliers, key staff contacts and the fallback method if central software becomes unavailable.
Which U.S. cybersecurity rules and standards apply?
TSA surface transportation: Security-directive series have applied to designated rail, transit and pipeline operators. The November 7, 2024 ‘Enhancing Surface Cyber Risk Management‘ notice was a *proposed* rule. The 2026 regulatory agenda still showed final action as undetermined. Check current directive versions and applicability directly with TSA.
Coast Guard maritime: A maritime cybersecurity final rule took effect July 16, 2025 for covered vessels and facilities. Its phased schedule included reporting from the effective date, initial personnel training by January 12, 2026 and major officer, assessment and plan milestones by July 16, 2027. Existing physical-security waivers do not automatically remove cyber obligations.
FTA transit: Certain rail-transit recipients of federal assistance must certify a process for identifying and reducing cybersecurity risks. The FTA’s Cybersecurity Assessment Tool for Transit (CATT) helps agencies review their preparedness.
CIRCIA: As of October 9, 2026, the implementing final rule was under federal review; a pending review is not an effective final reporting rule. Check for publication and effective dates while complying with any other applicable reporting duties.
Voluntary frameworks: NIST Cybersecurity Framework 2.0 and CISA’s Cross-Sector Cybersecurity Performance Goals help prioritize protection. NIST SP 800-82 Rev. 3 is final OT guidance; the September 2026 Rev. 4 is an initial public draft. NHTSA publishes voluntary vehicle cybersecurity guidance.
Resources for transportation cybersecurity teams
- FTA Cybersecurity Assessment Tool for Transit: structured self-assessment for transit agencies.
- NIST Cybersecurity Framework 2.0: common language for governance and risk priorities.
- NIST SP 800-82 Rev. 3: security measures tailored to operational technology.
- CISA Cybersecurity Performance Goals: voluntary high-impact baseline actions.
- U.S. Coast Guard maritime timeline: sector-specific implementation information.
- NHTSA vehicle cybersecurity: connected-vehicle safety guidance.
For broader background, see the phishing and cyber-incident response guides.
Frequently asked questions
Cyber incidents can expose information, hinder travel and freight processing, and interrupt supporting services. Safety consequences are possible in some operational environments, but they must be assessed on the facts of each case.
Yes. Operators rely on ticketing, dispatch support, employee accounts, websites and cargo-processing applications. Taking those systems offline can disrupt service even when vehicle controls are unaffected.
IT covers enterprise computing and data; OT involves monitoring or affecting physical processes. OT defenses must account for safety, reliability and specialized equipment.
They add wireless, software and supplier interfaces that require secure design, controlled updates, monitoring and protection of safety-relevant systems.
No. TSA directives, Coast Guard rules, transit assistance conditions and voluntary NIST/CISA practices have different scopes. Businesses should confirm which requirements govern their activities.
Sources and references
- CISA | Transportation Systems Sector and subsectors | Accessed October 2026
- CISA | Sector Risk Management Agencies | Accessed October 2026
- Maine Attorney General | Estes Express Lines data-breach filing | Accessed October 2026
- DP World Australia | Cybersecurity incident update | Accessed October 2026
- Port of Seattle | Cyberattack archive and subsequent data-breach notice | Accessed October 2026
- Pittsburgh Regional Transit | Notice of cyber incident | Accessed October 2026
- Atlanta News First | Airport statement on March 28, 2025 DoS | Accessed October 2026
- FTA | Cybersecurity Resources for Transit Agencies (including 2026 bulletin) | Accessed October 2026
- FTA | Cybersecurity Assessment Tool for Transit (CATT) | Accessed October 2026
- Federal Register | TSA Enhancing Surface Cyber Risk Management proposed rule, 89 FR 88488 (2024) | Accessed October 2026
- Office of Information and Regulatory Affairs | TSA rulemaking agenda (2026) | Accessed October 2026
- U.S. Coast Guard | Cybersecurity in the Marine Transportation System implementation timeline | Accessed October 2026
- U.S. Coast Guard | July 2026 guidance on existing maritime security waivers | Accessed October 2026
- OIRA | CIRCIA final-rule review record received October 1, 2026 | Accessed October 2026
- NIST | Cybersecurity Framework 2.0 (final, February 2024) | Accessed October 2026
- NIST | Guide to Operational Technology Security, SP 800-82 Rev. 3 | Accessed October 2026
- NIST | Guide to Operational Technology Security, SP 800-82 Rev. 4 | Accessed October 2026
- CISA | Cross-Sector Cybersecurity Performance Goals | Accessed October 2026
- NHTSA | Vehicle Cybersecurity Resources | Accessed October 2026
- TSA rail security-directive ratification and scope | Federal Register (2025) | Accessed October 2026
- Federal Register | Coast Guard marine transportation cybersecurity final rule, 90 FR 6298 | Accessed October 2026