Support
CASE STUDY
ELECTRIC UTILITIES • EUROPE

Strengthening OT Cybersecurity for a European Electric Utility

How a major European electric distribution operator improved visibility, compliance, and operational resilience across 96,000 km of grid infrastructure.

8M+
Customers Served
63,000+
Substations
96,000 km
Grid Infrastructure
The Decision

What changed in the July 2024 revision (SD-2021-02E)

TSA renewed and revised its pipeline cybersecurity directive in July 2024. The core requirements — Cybersecurity Implementation Plan, Incident Response Plan, and annual Cybersecurity Assessment Plan — remain in force. The 2024 revision adds several compliance-relevant clarifications pipeline operators should be aware of:

MSSP liability is now explicit. If you've delegated any security measures to a Managed Security Service Provider, you retain sole compliance responsibility. TSA will hold the owner/operator accountable regardless of who's doing the work.

Authorized Representatives carry joint liability. Contractors or agents acting on your behalf — coordinating or executing CIP requirements — are now formally defined, and both parties are liable for non-compliance.

Assessment cadence clarified. At least one-third of your TSA-approved CIP must be assessed each year, with 100% coverage over any rolling three-year period. Annual CAP submissions and reports are due no later than 12 months from TSA's approval of the previous CAP.

"Operational disruption" redefined. The directive now ties disruption to "business critical functions" — your own determination of the capacity and capabilities needed to meet operational and supply chain obligations. This gives operators more definitional control but also more documentation responsibility.

The directive is still performance-based — not prescriptive. TSA continues to inspect against your approved CIP, not a fixed checklist. That means the depth and accuracy of your asset inventory, change records, and traffic snapshots are the actual evidence base at inspection time.

The Decision

What TSA inspectors can request — and how Industrial Defender delivers it

TSA may request to inspect or copy any of the following at any time. Industrial Defender surfaces each item directly on the intuitive platform.

OT asset inventory

Hardware and software inventory including SCADA systems, PLCs, RTUs, and HMIs — with firmware versions, OS, open ports, and PLC key switch positions captured actively, not inferred from network traffic.

Firewall rules

Complete firewall ruleset collection from OT network perimeters, including rule-by-rule visibility and change history to demonstrate ongoing configuration management.

Network architecture documentation

Network diagrams, switch and router configurations, architecture diagrams, publicly mutable IP addresses, and VLAN documentation — maintained as a living record, not a one-time snapshot.

Policy and procedure evidence

Documentation supporting your Cybersecurity Implementation Plan, Incident Response Plan, and Assessment Program — with audit trail evidence of actual implementation, not just written policy.

Log files

Endpoint and OT system logs collected automatically and stored with historical context. No manual log collection required at inspection time

On-demand traffic snapshots
Network traffic captures (PCAPs), up to 24 hours as directed by TSA
East-West traffic within OT environments — lateral movement between systems within your control network
North-South traffic between IT and OT systems, including perimeter boundary visibility
The Decision

Why pipeline operators choose active OT collection over passive-only monitoring

Passive network traffic analysis tells you what's communicating. It cannot tell you:

What's installed
What's changed
Whether a PLC configuration matches its approved baseline

Industrial Defender actively communicates with your OT assets at the device level — the same way your engineering tools do — so you get the configuration data, firmware versions, firewall rules, and user accounts that passive-only tools miss entirely.

Industrial Defender has been actively collecting OT device data safely since 2006, across the largest critical infrastructure operators in the United States. Active collection is operationally safe — your pipeline does not need to go offline for ID to do its job.

INDUSTRIAL DEFENDER — ACTIVE + PASSIVE

Deep asset data from every device

Network visibility, not asset data

Software versions, firmware, open ports, user accounts, firewall rules, PLC key switch positions, and configuration baselines — collected via SSH, SNMP, agents, and passive NTA depending on what each device supports.

COMPLIANCE

Out of the Box Compliance Reporting

Industrial Defender includes pre-built, audit-ready report templates designed for TSA's pipeline Security Directive, as well as the other frameworks your OT security program operates under.

No custom report development required — reports are available on demand, on the same timeline TSA inspectors work on.

Compliance Frameworks
TSA Pipeline Security Directive
 NERC CIP
ISA/IEC 62443
NIST CSF 2.0
Get Started

Built for pipeline and LNG environments

Industrial Defender supports the full range of OT assets common to midstream and downstream pipeline operations — including assets that are air-gapped, remote, or sensitive to network communication.

For environments where persistent agents aren't practical, ID Reach is a portable Windows executable that collects the same depth of data with no installed service and no footprint left behind.

Platform is deployed on-premises only. No data leaves your environment.
All collection, monitoring, and reporting runs within your infrastructure.

See your TSA compliance posture in 30 days