This episode explains how to map OT assets into a CMDB in a way that supports security decisions without forcing IT-centric data models that ignore plant reality. You’ll learn which attributes belong in a CMDB record for OT, including stable identifiers, location context down to cabinets or lines, ownership, vendor support boundaries, criticality, and interface exposure, so the CMDB becomes useful for vulnerability response and incident scoping. We then focus on relationships, such as controller-to-I/O dependencies, HMI-to-controller communications, historian data paths, remote access pathways, and shared services like identity and time synchronization, because many OT failures cascade through relationships, not individual devices. Drift control is treated as the key success factor, covering change triggers, validation cycles, and reconciliation practices that detect “silent” changes introduced by maintenance, contractors, or upgrades. You’ll also learn how to use CMDB outputs during troubleshooting and incidents, such as quickly identifying affected zones, confirming support ownership, and producing defensible evidence for audits and post-incident reviews. Produced by BareMetalCyber.com, where you’ll find more cyber audio courses, books, and information to strengthen your educational path. Also, if you want to stay up to date with the latest news, visit DailyCyber.News for a newsletter you can use, and a daily podcast you can commute with.