← Frameworks / TSA Pipeline SD / Coverage Analysis

TSA Pipeline Security Directives (SD-1 and SD-2) โ€” SP 800-53 Coverage

How well do NIST SP 800-53 Rev 5 controls address each TSA Pipeline SD requirement? This analysis maps from framework clauses back to SP 800-53, with expert coverage weightings and gap identification.

Coverage Distribution
Full (85-100%): 2 Substantial (65-84%): 10 Partial (40-64%): 0 Weak (1-39%): 0

Clause-by-Clause Analysis

Sorted by clause
SD-1 Sec 1 Cybersecurity Coordinator

Rationale

PM-01 establishes the information security program requiring a designated program manager. PM-02 assigns security roles and responsibilities including coordination duties. PM-10 security authorization process provides governance structure for security oversight. Together these controls establish organizational security leadership and coordination roles.

Gaps

SD-1 requires a primary and at least one alternate Cybersecurity Coordinator at corporate level, with one of them reachable by TSA and CISA at all times, including when the US government is closed. At least one coordinator must be a US citizen eligible for a security clearance, who receives any information restricted to US persons. Since 01F a non-US citizen may also serve as primary or alternate, and since 01G only as a current member of NEXUS, Global Entry or a comparable program TSA accepts. Owner/operators send each coordinator's name, title and contact details to TSA and update them within seven days of a change. SP 800-53 assigns security roles in general terms and sets none of these conditions.

Mapped Controls

SD-1 Sec 2 Incident Reporting

Rationale

IR-01 establishes incident response policy and procedures including reporting requirements. IR-06 addresses incident reporting to designated authorities and external organizations. PM-15 covers contacts and information sharing with security groups and external organizations including government agencies.

Gaps

SD-1 requires a report to CISA as soon as practicable and no later than 72 hours after the owner/operator identifies a cybersecurity incident, through CISA's Incident Reporting System or by phone. Directive 01F lengthened the window from 24 hours and added the earliest known date of compromise and the date of detection to the report. Supplemental information is due within 24 hours of it becoming available. The directive defines the incidents to report, from unauthorized access and malware to physical attacks on network infrastructure and anything that could disrupt operations, and the content of each report. SP 800-53 leaves the time limit, the recipient and the content to the organisation.

Mapped Controls

SD-1 Sec 3 Vulnerability Assessment

Rationale

RA-03 provides comprehensive risk assessment methodology. RA-05 addresses vulnerability monitoring and scanning across IT systems. CA-02 establishes security assessment processes including assessment plans and evidence collection. CA-08 penetration testing validates vulnerability identification through active testing.

Gaps

TSA requires a TSA-specific assessment methodology tailored to pipeline infrastructure. Pipeline architecture review requirements covering SCADA, DCS, and field device networks are not addressed. OT/IT convergence assessment examining the security boundary between pipeline operational technology and enterprise IT systems is a pipeline-sector requirement not captured in SP 800-53.

SD-1 Sec 4 Remediation Measures

Rationale

CA-05 establishes plan of action and milestones (POA&M) for tracking remediation of identified weaknesses. PM-04 provides the plan of action and milestones process at the organizational level. RA-07 addresses risk response actions including remediation, mitigation, acceptance, and transfer decisions.

Gaps

For each gap the vulnerability assessment finds, SD-1 requires remediation measures and a timeline for them, sent to TSA by email with any Sensitive Security Information protected. Since 01F the owner/operator must also carry out the measures and tell TSA at once if it cannot meet a deadline. SP 800-53 tracks remediation in general terms, without the submission to TSA or its handling rules. Keeping pipeline operations running and safe while remediating is a sector-specific concern that SP 800-53 does not address.

Mapped Controls

SD-2 Sec A Network Segmentation

Rationale

SC-07 provides boundary protection including managed interfaces and traffic filtering between network segments. SC-32 addresses system partitioning into separate physical or logical domains. AC-04 enforces information flow control policies between interconnected systems. SC-46 provides cross-domain policy enforcement for managing data flows across security domains.

Gaps

Pipeline-specific IT/OT segmentation requirements covering SCADA networks, distributed control systems (DCS), and remote terminal units (RTU) are not addressed. Gas and liquid pipeline operational zones with distinct safety and process control requirements need sector-specific segmentation architectures. Segmentation of compressor stations, pump stations, and regional control centers is a pipeline-specific requirement beyond generic boundary protection.

SD-2 Sec B Access Control Measures

Rationale

AC-02 provides account management including account types, creation, modification, and removal. AC-03 enforces access control policies on system resources. AC-05 implements separation of duties. AC-06 enforces least privilege. AC-07 limits unsuccessful login attempts. AC-17 addresses remote access controls including MFA requirements. IA-02 provides identification and authentication for organizational users including multi-factor authentication. IA-05 manages authenticators including password policies. IA-08 addresses identification and authentication of non-organizational users.

Gaps

Pipeline SCADA operator access constraints where operators need immediate access to safety-critical controls during emergencies are not addressed. Shared HMI accounts in pipeline control rooms, common in OT environments, conflict with individual accountability requirements. Emergency access procedures during pipeline events such as pipeline ruptures or pressure excursions require sector-specific bypass mechanisms not covered in SP 800-53.

SD-2 Sec C Continuous Monitoring and Detection

Rationale

SI-04 provides system monitoring including intrusion detection, malware detection, and unauthorized connection identification. CA-07 establishes continuous monitoring strategy with defined metrics and frequencies. AU-02 defines auditable events for logging pipeline-relevant security events. AU-06 provides audit review, analysis, and reporting capabilities. SC-48 supports sensor relocation for adaptable monitoring deployment. IR-04 addresses incident handling including detection and analysis of anomalous activity.

Gaps

Pipeline-specific OT protocol monitoring for Modbus, DNP3, OPC-UA, and other industrial protocols requires deep packet inspection capabilities not addressed in SP 800-53. SCADA process variable anomaly detection identifying abnormal pressure, flow, temperature, or valve positions is a pipeline-specific monitoring requirement. Compressor station and pump station monitoring for cyber-physical anomalies is not captured in generic continuous monitoring controls.

SD-2 Sec D Patch Management

Rationale

SI-02 addresses flaw remediation including patch identification, testing, and installation. CM-03 provides configuration change control processes for managing patches as system changes. CM-04 requires impact analysis before implementing changes including patches. RA-05 covers vulnerability scanning to identify missing patches. SA-22 addresses unsupported system components requiring compensating controls when patches are unavailable.

Gaps

Pipeline OT patching constraints where pipelines cannot be shut down for patching of safety-critical control systems are not addressed. Compensating controls for unpatched legacy SCADA systems that cannot accept modern patches require pipeline-specific guidance. Vendor patch qualification for safety instrumented systems (SIS) where improper patches could compromise pipeline safety functions is a sector-specific requirement beyond generic patch management.

SD-2 Sec E Cybersecurity Implementation Plan

Rationale

PL-01 establishes planning policy and procedures for security planning activities. PL-02 defines system security and privacy plans documenting implemented controls. PM-01 provides the organizational information security program plan. PM-09 establishes risk management strategy and implementation approach. CA-05 provides plan of action and milestones for tracking implementation progress. SA-09 external system services covers the oversight of managed security service providers that carry out measures in the plan.

Gaps

TSA review and approval process requiring the implementation plan to be submitted to and approved by TSA before execution is not captured. Pipeline-specific implementation milestones with TSA-mandated timelines for achieving compliance are sector-specific. Compliance reporting to TSA including periodic status updates and evidence of implementation progress is a regulatory oversight requirement beyond SP 800-53. Since 02E, an owner/operator that hands any measure in the plan to a managed security service provider keeps sole responsibility for it, and owner/operators and their authorized representatives are both liable for the representative's non-compliance. SA-09 covers overseeing such providers, but not this allocation of liability.

SD-2 Sec F Cybersecurity Architecture Design Review

Rationale

PL-08 provides security and privacy architecture guidance for information system design. SA-08 establishes security and privacy engineering principles for system development. SA-17 addresses developer security and privacy architecture and design documentation. SC-07 provides boundary protection architecture requirements. SC-32 addresses system partitioning into security domains.

Gaps

Pipeline-specific architecture patterns covering regional control centers, field sites, compressor stations, and pump stations are not addressed in SP 800-53. SCADA communication architecture review including telemetry networks, satellite links, and microwave communications used in pipeline operations requires sector-specific expertise. The integration of safety instrumented systems (SIS) with cybersecurity architecture for pipeline operations is a critical sector-specific gap.

SD-2 Sec G Cybersecurity Testing

Rationale

CA-08 provides penetration testing requirements including scope, methodology, and reporting. CA-02 establishes security assessment processes including independent assessments. RA-05 addresses vulnerability scanning and analysis. SA-11 covers developer testing and evaluation including security testing methodologies.

Gaps

The directive's Cybersecurity Assessment Plan uses methods such as penetration testing and red and purple team testing. It must assess at least one third of the measures in the TSA-approved implementation plan each year, so that all are assessed over any three years. The plan goes to TSA for approval each year, no later than 12 months after the last approval, with a report on the assessments of the previous 12 months. Directive 02E set these terms. SP 800-53 sets no such cycle. Pipeline OT penetration testing constraints prohibiting active testing on live SCADA and safety systems due to risk of pipeline disruption or safety incidents are not addressed. Tabletop exercises for pipeline cyber-physical scenarios such as ransomware affecting compressor station control or valve manipulation are sector-specific testing requirements. Testing of emergency shutdown systems and safety instrumented systems requires pipeline-specific test protocols not captured in SP 800-53.

SD-2 Sec H Cybersecurity Training

Rationale

AT-01 establishes training policy and procedures for security awareness and training programs. AT-02 provides security literacy training for all personnel. AT-03 delivers role-based security training for personnel with assigned security responsibilities. AT-04 maintains training records documenting completion and competency. PM-13 establishes the organizational security workforce including skills development and training requirements.

Gaps

Pipeline-specific OT security training covering SCADA system security, industrial control system threats, and pipeline-specific attack scenarios is not addressed. SCADA operator cyber awareness training addressing social engineering targeting control room operators and recognizing anomalous system behavior is sector-specific. Field technician device handling procedures for secure configuration and deployment of RTUs, flow computers, and other pipeline field devices require specialized training content.

Methodology and Disclaimer

This coverage analysis maps from TSA Pipeline SD clauses/requirements back to NIST SP 800-53 Rev 5 controls, assessing how well the SP 800-53 control set addresses each framework requirement.

Coverage weighting represents an informed estimate based on control-objective alignment, not a definitive compliance determination. Weightings consider whether SP 800-53 controls address the intent of each framework requirement, even where terminology and structure differ.

This analysis should be validated by qualified assessors for use in compliance or audit activities. The authoritative source for any compliance determination is always the framework itself.