TSA Security Directive Pipeline-2021-02F

What the authority record establishes

The directive continued performance-based requirements covering cyber risk assessment, plans, architecture, access, monitoring, incident response, testing, and related evidence for notified pipeline operators.

Was binding for notified covered owner/operators during its stated effective period

The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.

Why it matters to this market

The expired date and separate proposed-rule path make status verification essential; vendor pages must not present an old mapping as proof of current obligation or compliance.

Affected operating stages

• Governance
• Risk Assessment
• Architecture
• Access
• Monitoring
• Response
• Testing

Capabilities to examine

Asset Criticality And Operational Context

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for asset criticality and operational context.

Network Segmentation Policy Modeling

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for network segmentation policy modeling.

Secure Remote Access And Vendor Session Control

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for secure remote access and vendor session control.

Privileged Access, Credential, And Identity Governance

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for privileged access, credential, and identity governance.

Anomaly And Behavioral Detection

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for anomaly and behavioral detection.

Incident Response And Recovery Support

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for incident response and recovery support.

Compliance Mapping And Control Evidence

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for compliance mapping and control evidence.

Multi-Site Sensor, Data, And Policy Management

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for multi-site sensor, data, and policy management.

Affected buyer audiences

• covered pipeline operators
• OT security leaders
• legal and compliance teams
• incident-response leaders

Implementation questions

• Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
• What is binding, what is guidance, and what is a technical or consensus standard?
• Which publication, adoption, effective, application, transition, and enforcement dates differ?
• Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
• How will a source revision affect open work and historical decisions?

Interpretation boundary

The publication does not determine current applicability after the stated expiration and does not expose security-sensitive implementation detail.