🎓 Lesson 4
D3
Conducting OT Asset Inventory in Mixed-Vendor Environments
An OT asset inventory is a complete, accurate list of all physical and software devices—like PLCs, sensors, and HMIs—that control mining equipment and processes, especially when those devices come from different manufacturers.
🎯 Learning Objectives
- ✓ Identify and classify OT assets across at least three vendor ecosystems (e.g., Siemens, Rockwell, ABB) using standardized taxonomy
- ✓ Analyze asset metadata (IP, firmware version, protocol, criticality rating) to assign risk-weighted priority for vulnerability remediation
- ✓ Apply NIST SP 800-53 AC-17 and ISA/IEC 62443-2-1 asset discovery requirements to design a repeatable inventory workflow
- ✓ Explain how inconsistent vendor data models (e.g., missing SNMP MIBs or undocumented REST APIs) introduce gaps in automated discovery
📖 Why This Matters
In a modern mine, automation systems integrate legacy PLCs from 2005 with new AI-driven fleet management platforms—all speaking different 'languages'. Without a complete, up-to-date OT asset inventory, cybersecurity teams cannot know what they’re protecting, leading to blind spots where ransomware or unauthorized remote access can halt production. A single unpatched, forgotten RTU controlling a conveyor belt has caused multiple unplanned stoppages in Tier-1 mining operations—costing over $2M/hour in lost throughput. This lesson equips you to build inventories that survive vendor lock-in and technology churn.
📘 Core Principles
OT asset inventory is not just 'network scanning'—it’s a convergence of asset management, industrial networking, and cybersecurity governance. First, it relies on multi-modal discovery: passive (traffic analysis), active (SNMP, Modbus polling), and manual (vendor documentation, site surveys). Second, normalization is essential: mapping vendor-specific identifiers (e.g., Rockwell’s 'Controller Name' vs. Siemens’ 'Device Name') to a common schema like ISO/IEC 19984 or NIST’s CISA OT Asset Inventory Template. Third, context determines criticality: an identical temperature sensor is low-risk on a ventilation duct but mission-critical on a SAG mill bearing—requiring linkage to process safety layers (e.g., SIL ratings) and operational impact metrics (downtime cost, safety consequence). Finally, sustainment matters: unlike IT, OT assets change rarely—but when they do (e.g., firmware upgrade), inventory must be version-aware and auditable.
📐 Criticality Scoring Index (CSI)
The Criticality Scoring Index quantifies the operational impact of an OT asset failure by combining safety, production, and environmental consequences. It enables objective prioritization in mixed-vendor environments where asset importance isn’t self-evident from model numbers alone.
Criticality Scoring Index (CSI)
CSI = (S × wₛ) + (P × wₚ) + (E × wₑ) + (M × wₘ)Weighted composite score representing the operational criticality of an OT asset, used to prioritize inventory validation and remediation efforts.
Variables:
| Symbol | Name | Unit | Description |
|---|---|---|---|
| S | Safety Impact Score | dimensionless (1–5) | Ordinal score reflecting potential for injury or fatality if asset fails or is compromised |
| P | Production Impact Score | dimensionless (1–5) | Ordinal score reflecting financial and throughput loss due to asset failure |
| E | Environmental Impact Score | dimensionless (1–5) | Ordinal score reflecting potential for soil, water, or air contamination |
| M | Maintainability Score | dimensionless (1–5) | Ordinal score reflecting difficulty/time to restore function (e.g., spare part lead time, vendor support responsiveness) |
| wₛ | Safety Weight | dimensionless | Predefined weight (typically 0.4) reflecting organizational risk tolerance policy |
| wₚ | Production Weight | dimensionless | Predefined weight (typically 0.35) reflecting economic exposure |
| wₑ | Environmental Weight | dimensionless | Predefined weight (typically 0.15) reflecting regulatory liability |
| wₘ | Maintainability Weight | dimensionless | Predefined weight (typically 0.1) reflecting operational resilience posture |
Typical Ranges:
High-criticality assets (e.g., SIS logic solvers): 3.8 – 5.0
Medium-criticality assets (e.g., conveyors, pumps): 2.0 – 3.7
Low-criticality assets (e.g., non-safety lighting controls): 1.0 – 1.9
💡 Worked Example
Problem: Asset: ABB AC500 PLC controlling primary crusher feed rate. Safety impact = 3 (moderate injury risk), Production impact = 5 (full line shutdown, $1.8M/hr loss), Environmental impact = 2 (localized dust release), Maintainability score = 1 (spare parts lead time > 4 weeks).
1.
Step 1: Assign ordinal scores (1–5) per dimension using mine-specific consequence matrices aligned to ISO 31000.
2.
Step 2: Apply weighted CSI formula: CSI = (S × 0.4) + (P × 0.35) + (E × 0.15) + (M × 0.1).
3.
Step 3: Calculate: (3 × 0.4) + (5 × 0.35) + (2 × 0.15) + (1 × 0.1) = 1.2 + 1.75 + 0.3 + 0.1 = 3.35.
Answer:
The result is 3.35, which falls within the high-priority range of 3.0–5.0—triggering mandatory inclusion in quarterly vulnerability validation and firmware update planning.
🏗️ Real-World Application
At Rio Tinto’s Pilbara Operations, a 2022 OT inventory initiative discovered 1,247 unique assets across 11 vendor families—including legacy Honeywell TDC 3000 DCS nodes, modern Komatsu HMI tablets, and third-party vibration monitors using custom MQTT brokers. Automated discovery missed 38% of field devices due to disabled SNMP and proprietary serial-to-IP gateways. The team deployed a hybrid approach: passive NetFlow analysis to map traffic flows, vendor-specific CLI scripts (e.g., Rockwell's Logix Designer export), and on-site QR-code scanning of nameplates linked to a CMDB. This revealed 217 undocumented assets—including 43 air compressor controllers with default passwords—leading to a 6-month remediation plan aligned to ISA/IEC 62443-2-1 Annex A.
🔧 Interactive Calculator
🔧 Open Mine Automation Cybersecurity Framework Calculator📋 Case Connection
📋 Autonomous Haulage System (AHS) Cybersecurity Upgrade – Iron Ore Mine, Pilbara
Legacy CAN bus interfaces exposed to lateral movement; lack of secure firmware update mechanism
📋 IIoT Sensor Network Security for Tailings Monitoring – Copper Mine, Chile
Use of consumer-grade LoRaWAN gateways with default credentials; no sensor identity attestation
📋 Blasting Control System Zero Trust Pilot – Limestone Mine, Indiana
Single-factor authentication for blast engineers; no session timeout or command replay protection