Simply put, metadata is data about data. It describes and provides information about other data.
In the context of “Discovering asset metadata of OT devices,” we are talking about metadata within operational devices that reside on SCADA networks, DCS networks, or OT networks as a whole. Take for example an Allen-Bradley PLC. Metadata about this type of device may simply be its make, model, and its manufacturer. A step deeper, and we may find metadata about its IP and MAC address, its OS and build numbers, as well as data around potential software flaws.
A step even deeper may reveal:
1. Connections these devices are making to peer devices
2. Ports and protocols in use
3. Services being leveraged to make these connections
4. Activities and commands used to control and configure these devices
Put into practice, properly tracking and reporting on metadata about a controller and its fans’ revolution speed may reveal an anomaly that would have left a critical system in jeopardy. The metadata in this instance is the hidden detail found when examining actual revolutions per second, and their deviations from normal. What may not be visible to the naked eye is clearly apparent when examining the metadata.
Within OT networks, metadata can be consumed to:
1. Schedule planned maintenance
2. Optimize asset performance
3. Track compliance
4. Provide valuable data for upstream analytics
5. Improve the overall safety posture of our plants and facilities
6. Identify potential anomalies in controls and subsystems
As OT systems and components become more advanced and interconnected, the possibilities of mining this metadata to make our operations more efficient, safer, and compliant are endless. In the boardroom, OT metadata can help to deliver information to avoid cost overruns, highlight potential savings, and costly downtime avoidance can help drive improved margins, reputation, and higher returns across the enterprise.