PIVTR-D
SSector

Transportation: rail, transit, aviation, maritime and pipelines

First moves
  1. Check train control, positive train control (PTC), signals, supervisory control and data acquisition (SCADA), vessel and airport systems for safety impact.Safety Officer
  2. Record in T1 when the incident was identified; the clock to the Cybersecurity and Infrastructure Security Agency (CISA) starts there.Planning
  3. Page the Transportation Security Administration Cybersecurity Coordinator or the Coast Guard Cybersecurity Officer.Liaison
  4. Confirm with counsel which rows apply; record who decided each clock started.Legal advisor
  5. For a maritime incident, call the National Response Center (NRC) without delay and file a separate CISA report.Liaison

Then work the page: Reporting obligations, Terms, Roles, What changes in each phase, Records, Who you work with.

This page is for responders at railroads, rail transit and bus systems, airports and air carriers, and vessels and facilities under the Maritime Transportation Security Act (MTSA). Pipelines are on the Energy page.

Transportation Security Administration (TSA) directives and security programs send cyber incidents to CISA; the Coast Guard rule sends them to the NRC. Safety comes first. A cyber incident on train control, a vessel or an airfield system is a safety event, and the operations control center (OCC) decides whether service runs.

This page adds to the phase playbooks for scope, contain, eradicate and recover. Use it with the OT scenario. Incident Command seats for this sector are on Command by incident type.

This sector page is an addition to the book. Primary sources: TSA Security Directive (SD) 1582-21-01C, SD 1580/82-2022-01C and TSA's 2026 notices; 49 CFR 1570.203; the Coast Guard final rule and 33 CFR Part 101 Subpart F; the Federal Transit Administration (FTA) two-hour notification guide. Checked November 2026.

Reporting obligations

Counsel confirms which rows apply. Record in T1 who decided each clock started, and when. The notification deadlines table lists other regimes.

ObligationWho reports to whomClockStarts whenWhat the report contains
TSA SD 1580-21-01 series (freight rail) and SD 1582-21-01 series (passenger rail and rail transit)Freight railroads in 49 CFR 1580.101, passenger railroads and rail transit systems in 1582.101, and others TSA designates, to CISA at cisa.gov/forms/report or (888) 282-0870. Bus-only operations are excludedAs soon as practicable, and no later than 72 hoursThe owner/operator identifies a cybersecurity incident, including one still under investigationContact details, affected systems and locations, description, detection dates, indicators, impact and planned response, as available. Say the report satisfies the directive. SD 1582-21-01C (October 2024) said 24 hours; TSA's 2026 notices state 72 hours. Confirm against the current revision
49 CFR 1570.203, significant security concernsFreight rail, passenger rail, rail transit and over-the-road bus owner/operators to TSAAs soon as possible, and within 24 hoursInitial discovery of a potential threat or significant security concern, such as a threat or suspicious activityReporter, affected train, vehicle or facility, route, description, who was notified, action taken, source of any threat
TSA Information Circulars IC 2021-01 and IC Surface-2025-01 (voluntary)Surface owner/operators to the TSA Transportation Security Operations Center (TSOC)12 hours, recommendedDiscovery of an actual or potential significant cybersecurity incidentA voluntary call. The directives do not require it
TSA airport and aircraft operator security programsAirport operators and aircraft operators to CISA24 hoursAs the security program setsThe amendments are Sensitive Security Information (SSI), and this page found no public TSA document that states the clock. Press reports give 24 hours, and a Department of Homeland Security notice of April 19, 2024 says the 24-hour pipeline deadline mirrors the aviation requirement; confirm against your TSA-approved security program
TSA SD Pipeline-2021-01 seriesPipeline owner/operators to CISAAs soon as practicable, and within 24 hoursIdentification of a cybersecurity incidentSee Energy
33 CFR 101.620(b) and 101.650(g), reportable cyber incidentOwners or operators of MTSA vessels, facilities and outer continental shelf facilities to the NRC, 1-800-424-8802Without delayAn incident that leads, or could reasonably lead, to substantial loss of confidentiality, integrity or availability of a covered system, or to a transportation security incidentReporting source, location with address, type of vessel or facility, brief summary and impact. In force since July 16, 2025. Both paragraphs apply to entities that have not reported to the Coast Guard under 33 CFR 6.16-1 or are not subject to it
33 CFR 6.16-1, as amended by Executive Order 14116 (February 21, 2024)Any vessel, harbor, port or waterfront facility to the FBI, CISA and the Captain of the Port (COTP)ImmediatelyEvidence of sabotage, subversive activity, or an actual or threatened cyber incidentNVIC 02-24 Change 1: an NRC report reaches the COTP and the FBI's CyWatch. CISA needs its own report
33 CFR 160.216, hazardous conditionVessel owner, agent, master, operator or person in charge to the nearest Coast Guard Sector Office or Group OfficeImmediatelyA hazardous condition on board a vessel, or caused by a vessel or its operation. The January 17, 2025 final rule added "cyber incident" to the definition (160.202)The Coast Guard's FAQ names the nearest COTP or Officer in Charge, Marine Inspection (OCMI) for this notice. It says foreign vessels also report hazardous conditions on the Notice of Arrival (160.206)
49 CFR 674.33(a), rail transit safety eventsRail transit agency to its State Safety Oversight Agency (SSOA) and FTA, through the DOT Transportation Operations Center2 hoursOccurrence of a listed event, from any cause: fatality, two or more injuries, derailment, certain collisions, evacuation for life safety, unintended train movementAgency, date, time, location, line, casualties, event type

TSA's proposed rule "Enhancing Surface Cyber Risk Management" (89 FR 88488, November 7, 2024) would codify the directives in 49 CFR parts 1500, 1503, 1520, 1570, 1580, 1582, 1584 and 1586. It adds cyber risk management programs and incident reporting for over-the-road bus operators. Comments closed February 5, 2025.

This page found no final rule as of November 2, 2026, and TSA's September 2026 notice still relies on the yearly directives. Check the Federal Register under RIN 1652-AA74.

The Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) final rule went to the Office of Management and Budget (OMB) on October 1, 2026. This page found no publication by November 2, 2026. CIRCIA reporting starts only after the final rule takes effect.

Sources: SD 1582-21-01C, effective October 24, 2024; TSA notices of April 16, 2026 and September 1, 2026 (OMB control number 1652-0074); TSA release of March 7, 2023; The Record, aviation 24-hour rule, August 29, 2022; Transportation Security Oversight Board notice of April 19, 2024 (Emergency Amendment 23-01; Pipeline-2021-01B moved the pipeline clock from 12 to 24 hours, which footnote 8 says mirrors the reporting requirements for other surface and aviation entities); 33 CFR 101.615, 101.620(b)(7), 101.635, 101.650(d), (e) and (g) and 101.655 in the regulatory text of the final rule, 90 FR 6298, January 17, 2025, and in the Cornell Legal Information Institute copy of the current CFR, read November 2026; eCFR 33 CFR 160.202 and 160.216, read November 2026; Executive Order 14116; NVIC 02-24 Change 1, November 12, 2025; Coast Guard rule FAQ, January 9, 2026 (33 CFR 160.206 and 160.216); TSA proposed rule; Paubox, CIRCIA at the White House, October 8, 2026, and Cyber incident reporting rule reaches final White House review, October 14, 2026.

Terms

TermMeaningPIVTR-D equivalent
Cybersecurity incident (TSA)An occurrence that, without lawful authority, jeopardizes or disrupts the integrity, confidentiality or availability of systems. Includes events still under investigationIncident, from identification
Critical Cyber SystemAny IT or OT system or data that, if compromised or exploited, could result in operational disruption (SD 1580/82-2022-01 series)Critical system in the containment triggers
Cybersecurity CoordinatorThe primary and at least one alternate named to TSA. One must be reachable by TSA and CISA 24 hours a dayLiaison
Cybersecurity Implementation PlanThe TSA-approved plan for segmentation, access control, monitoring and patching of Critical Cyber SystemsPreparation
Cybersecurity Assessment PlanThe annual plan and report testing the implementation plan, covering at least one third of the measures each yearPreparation
Cybersecurity Incident Response PlanThe directive plan for Critical Cyber Systems, naming responsible people by position, exercised at least once a yearThis book's plan and response loop
SSISensitive Security Information. 49 CFR 1520.5 lists security programs and security directives as SSI; TSA has published the rail directivesRestricted handling in Evidence
Train controlSystems that set routes, separate trains and enforce speed, including signals, interlockings (route and switch logic), CBTC and PTCOT; see the OT scenario
CBTCCommunications-based train control: train location and movement authority sent by radio between trains and wayside equipment (IEEE 1474)OT
PTCPositive train control, required on certain main lines by 49 U.S.C. 20157 and defined in 49 CFR 236.1003. A Critical Cyber System under the 2022-01 seriesOT
WaysideEquipment along the track: signals, switch machines, track circuits, radios, field cabinetsOT asset in scope
SCADASupervisory control and data acquisition, here for traction power, tunnel ventilation, pumps and station systemsOT
Safety-critical systemA system whose modification would threaten life or safety at once. The American Public Transportation Association (APTA) puts signaling, interlocking and train protection in this zoneSafety Officer review in T3
OCCOperations control center: dispatches trains or vehicles and controls power and ventilationOperations
ROCRail operations center, a name some railroads and transit systems give their OCCOperations
Revenue serviceCarrying passengers or freight for payRecover
Safety certificationVerifying a new or changed rail system is safe before revenue service. A rebuilt safety-critical system may need itT7 pre-restoration sign-off
PTASPPublic Transportation Agency Safety Plan, 49 CFR part 673, with safety risk management and a chief safety officernone
SSOAState Safety Oversight Agency, 49 CFR part 674: oversees rail transit safety and receives event noticesRegulator in T17
Reportable cyber incidentThe Coast Guard trigger; see the reporting tableIncident with an NRC clock
CySOCybersecurity Officer (33 CFR 101.625), responsible for the cyber parts of the security plansCISO
FSO, VSO, CSOFacility, Vessel and Company Security Officers under MTSA security plansLiaison to the COTP; physical security in Operations
Cybersecurity PlanThe cyber part of the vessel or facility security plan, due to the Coast Guard by July 16, 2027Preparation
COTPCaptain of the Port, the Coast Guard officer with authority over a port zoneRegulator and coordination body
Airport security program, aircraft operator security programTSA-approved programs under 49 CFR parts 1542 and 1544, with cyber amendments including Emergency Amendment 23-01 (March 7, 2023)none

Roles

Sector roleWhat they do in an incidentPIVTR-D or Incident Command seat
Cybersecurity Coordinator (TSA)Takes TSA and CISA calls, files the CISA report and supplementsLiaison
Cybersecurity Officer (Coast Guard)Leads the cyber parts of the security plan; records and reports incidents to the owner or operatorCISO, with Liaison filing the NRC report
Facility, Vessel or Company Security OfficerPhysical security measures, MTSA reports, contact with the COTPLiaison; physical security group in Operations
Airport security coordinator (49 CFR 1542.3), aircraft operator security coordinator (1544.215)TSA contact for the security programLiaison
Chief safety officer (49 CFR 673)Safety risk decisions, safety event reports, the SSOASafety Officer
OCC or dispatch superintendent, rail controllersRun trains and vehicles, move to manual operation, stop or restrict serviceOperations, service branch
Signals and train control engineeringApprove every action on train control and wayside systems; verify safe stateOperations, OT branch; approve T3 and T7
Airport operations, airline operations controlRun the airfield, gates, baggage and flights on degraded systemsOperations
Railroad or transit policeScene security, threats, link to the FBILiaison; Intelligence/Investigations for evidence
Emergency managerRuns the incident action plan and the emergency operations centerPlanning
Customer communicationsService alerts and announcementsPublic Information Officer

What changes in each phase

Preparation

#ItemOwner
1Name a primary and alternate Cybersecurity Coordinator to TSA, and report changes within 7 daysCISO
2If a coordinator is not a US citizen, confirm a current NEXUS, Global Entry or comparable membership, per the January 15, 2026 revisionCISO
3Keep the Critical Cyber System list current, with PTC listed where installedCISO
4Exercise the Cybersecurity Incident Response Plan at least once a year with the OCC and signals engineeringPlanning
5Test the manual controls that isolate industrial control systems from IT, and manual operating proceduresOperations
6For MTSA entities, run cyber drills twice each calendar year and an exercise each year, no more than 18 months apart (33 CFR 101.635)Planning
7Train maritime staff with system access each year; train new staff within 5 days of access (101.650(d))Logistics
8Turn off automatic EDR isolation on OCC, wayside and SCADA hostsCISO
9Test CISA, NRC and TSOC reporting access with named staffLiaison
10Join the ISAC for each mode you runLiaison

Identification and verification

#ItemOwner
1Check train control, PTC, signals, SCADA, vessel and airfield systems for safety impact firstSafety Officer
2Record the identification time; an event under investigation can already start the TSA clockPlanning
3Ask the OCC whether service is safe, and record its decisionIncident Commander
4Classify the event against each row: cybersecurity incident, reportable cyber incident, safety eventLegal advisor
5For a maritime incident, call the NRC, then report to CISA, and save both report numbersLiaison
6If an unintended train movement or other listed safety event occurred, notify the SSOA and FTA within 2 hoursSafety Officer
7Mark SSI in notes, tickets and reports before they circulatePlanning

Response loop

#ItemOwner
1Get signals engineering and OCC approval in T3 before containing a train control, PTC, CBTC or SCADA assetIncident Commander
2Record each decision to stop, restrict or restore service, with who made itPlanning
3Send CISA supplements as facts arriveLiaison
4Brief the COTP on vessel movement, cargo operations and facility statusLiaison
5Request logs, images and remote access records from signaling, CBTC and SCADA suppliersIntelligence/Investigations
6Before revenue service, confirm whether a restored safety-critical system needs safety certificationSafety Officer
7Run test trains or a safe-state check before returning a line to serviceOperations

Debrief

#ItemOwner
1Update the Cybersecurity Incident Response Plan and the Critical Cyber System listCISO
2Feed findings into the next Cybersecurity Assessment Plan reportCISO
3Enter safety hazards found into the PTASP safety risk management processSafety Officer
4Update the MTSA Cybersecurity Plan and next year's drill scenariosPlanning

Sources: SD 1582-21-01C; SD 1580/82-2022-01C; 33 CFR 101.635 and 101.650(d); Coast Guard implementation timeline and training guidance; APTA APTA-SS-CCS-RP-002-13 (2013).

Records

RecordWhat changes
T1 Incident recordAdd identification time, CISA and NRC report numbers, affected Critical Cyber Systems and service status
T2 Triage briefAdd safety impact, service impact and hours left on each clock
T3 Containment decisionAdd signals engineering, OCC and Safety Officer approval for OT actions
T7 Pre-restoration sign-offAdd the safety certification decision and test results before revenue service
T13 Law enforcement and insurer contactAdd railroad or transit police, the COTP and FBI CyWatch
T17 Regulator notification worksheetOne worksheet each for CISA, TSA, the NRC, the COTP, and the SSOA and FTA
T18 Interim statement and media inquiry logAdd service alerts. Counsel checks wording for SSI
T19 Vendor evidence and preservation requestSend to signaling, CBTC, SCADA and fare system suppliers
SSOA event report, NRC reportJoin the incident record

Who you work with

BodyWhat they do for youHow to reach them
CISAReceives TSA-required and maritime cyber reports; technical helpcisa.gov/forms/report, (888) 282-0870, or (844) 729-2472 for maritime reports
TSADirectives, security programs, inspections, the TSOCYour TSA inspector; the contact address in the directive
US Coast GuardEnforces MTSA and the cyber ruleNRC at 1-800-424-8802; the local COTP; MTSCyberRule@uscg.mil for rule questions
FTA and SSOAsTransit safety oversight. FTA publishes the Cybersecurity Assessment Tool for Transit; rail transit grantees certify a cybersecurity risk plan process (49 U.S.C. 5323(v))DOT Transportation Operations Center for 2-hour notices; your SSOA
Federal Railroad Administration (FRA)Railroad safety, including PTC under 49 CFR part 236Your FRA regional office
Federal Aviation Administration (FAA)Aircraft and air traffic safety. Its 2024 proposed rule on aircraft network security was not final as of June 2026Your FAA certificate office
Surface Transportation ISAC (ST-ISAC), Public Transportation ISAC (PT-ISAC), Over-the-Road Bus ISACThreat sharing for rail, transit and bus; PT-ISAC issues daily reportsMembership; PT-ISAC through APTA
Aviation ISAC (A-ISAC)Threat sharing for airlines, airports and aerospaceMembership
Maritime Transportation System ISAC (MTS-ISAC)Threat sharing for ports, terminals and vessel operatorsMembership
Area Maritime Security CommitteePort coordinationThrough the COTP
FBIInvestigation; receives NRC maritime reports through CyWatchThe local field office, or the FBI's Internet Crime Complaint Center (IC3)

Sources: FTA, Cybersecurity Resources for Transit Agencies; APTA PT-ISAC page; FAA proposed rule (August 21, 2024), status from Chemical Facility Security News, June 1, 2026.

Watch out
  • TSA reissues each directive every year and changes its text. The rail and transit window moved from 24 hours in the 2024 text to 72 hours in TSA's 2026 notices. Read the revision in force.
  • The TSA clock starts at identification. Events still under investigation count, so file and supplement.
  • An NRC call reaches the COTP and the FBI. CISA needs its own report under 33 CFR 6.16-1.
  • Containing train control, PTC or SCADA is a safety decision. Signals engineering and the OCC approve it, and EDR auto-isolation on those hosts can stop trains.
  • Runbooks that cite TSA's 2024 proposed rule or the FAA's 2024 proposal as law are wrong. This page found neither final.
Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.