Critical Infrastructure Protection: Converged IT/OT Threat Containment

Segmentation Strategy

A robust segmentation strategy is the foundation of OT security. This involves defining network zones based on process criticality, grouping similar systems together. Access between these zones must be strictly brokered through identity-aware gateways that enforce protocol-specific allowlists, ensuring that only expected and authorized communication can occur. This "zero-trust" approach for OT networks is critical for preventing an adversary from moving laterally from a less-critical system to a highly sensitive one. This is also crucial for Medical Device Security.

Telemetry Augmentation

Given the lack of native telemetry in many OT systems, security teams must augment their visibility with specialized tools. Passive network analysis, which monitors traffic without interacting with the OT devices themselves, is essential for understanding normal communication patterns. This can be supplemented with tuned canary assets—decoy systems designed to attract and detect attackers—and OT-specific anomaly baselines that can identify subtle deviations from normal operational behavior, providing an early warning of a potential incident.

Response & Recovery

In an OT environment, response and recovery procedures must be carefully planned to ensure patient safety and operational continuity. This includes creating isolated runbooks for each zone, detailing the specific steps to contain an incident within that segment. It is also critical to pre-stage a manual override decision matrix. This matrix should be developed in collaboration with engineering and operations teams to define the exact conditions under which a safety-critical process can be manually overridden, ensuring that security responses do not inadvertently create a more dangerous situation.

Metrics

To measure the effectiveness of the OT security program, track metrics that reflect real-world risk reduction. Key indicators include the dwell time for lateral movement (how long an attacker can move undetected within the network), the number of unauthorized protocol attempts blocked by segmentation gateways, the duration of zone isolation drills (a measure of response readiness), and the percentage of high-criticality assets covered by the inventory. These metrics provide a clear picture of the program's maturity and its ability to protect critical operations.

Sources & Further Reading

NIST SP 800-82 Rev.3 (ICS security).

ISA/IEC 62443 Series.

CISA Shields Up & OT Advisories.

MITRE ATT&CK for ICS.

NERC CIP Standards (energy sector).

ENISA Threat Landscape for ICS/OT.

Konteks Praktis untuk Organisasi di Indonesia

Topik ot paling efektif jika diposisikan sebagai program lintas fungsi, bukan hanya proyek tim IT. Tim leadership perlu menetapkan objective yang jelas, misalnya penurunan risk exposure, peningkatan detection quality, dan percepatan decision cycle saat terjadi incident.

Dalam praktik di Indonesia, hambatan umum biasanya ada di konsistensi data, tata kelola akses, dan adopsi proses oleh tim operasional. Karena itu, pendekatan terbaik adalah delivery bertahap dengan milestone yang terukur, sambil menjaga kesinambungan operasi harian.

• Selaraskan scope dengan target bisnis dan compliance sejak awal
• Gunakan baseline metric yang bisa dipantau bulanan (MTTD, MTTR, coverage, quality)
• Pertahankan workflow sederhana agar tim non-teknis tetap bisa mengeksekusi

Roadmap Implementasi 30-60-90 Hari

Model 30-60-90 hari membantu tim menjaga fokus pada outcome, bukan sekadar checklist. Gunakan fase awal untuk baseline dan prioritas risiko, fase tengah untuk implementasi control utama, lalu fase akhir untuk validasi, tuning, dan handover operasional.

• 30 hari: baseline assessment, mapping dependency, dan prioritas quick wins
• 60 hari: implementasi control utama + playbook incident response
• 90 hari: simulation, tuning detection rule, dan KPI review untuk iterasi berikutnya

Kesalahan Umum yang Perlu Dihindari

Banyak program gagal menghasilkan dampak karena terlalu cepat menambah tools tanpa memperkuat governance dan operating model. Fokus utama sebaiknya pada konsistensi eksekusi, kualitas evidence, dan pengambilan keputusan berbasis metric.

• Mengukur sukses dari jumlah tools, bukan penurunan risk yang nyata
• Mengabaikan change management untuk user non-teknis
• Tidak menyiapkan ownership yang jelas untuk sustainment setelah go-live