One reason is an increased attack surface due to increase connectivity due to digitalization.
As the number and capability of threat actor targeting OT increases, so too does the need for robust cyber security controls. However, the complexity, scale, and long-standing nature of OT systems often means organizations can lack a holistic view of their environment, which undermines their ability to implement effective cyber security measures.
To that end, CISA, in collaboration with the Federal Bureau of Investigation, the United Kingdom’s National Cyber Security Centre, and other international partners released new joint cybersecurity guidance, entitled, “Creating and Maintaining a Definitive View of Your Operational Technology (OT) Architecture.”
This guidance explains how organizations can leverage data sources, such as asset inventories and manufacturer-provided resources like software bill of materials to establish and maintain an accurate, up-to-date view of their OT systems.
Increased Connectivity
Traditionally, OT networks lived in an isolated environment away from the Internet and external systems. However, modern operational demands led to increased connectivity as networks now integrate with enterprise systems, third-party vendors and cloud services. This makes designing appropriate security controls increasingly critical, to reduce the risks to previously isolated systems.
To design appropriate and effective controls, a holistic system understanding is required. In this guidance, the term definitive record describes a continually updated, accurate and up-to-date view of the system. A definitive record is an evolving collection of information that will change over time, with all system changes recorded to maintain its accuracy and authority.
Establishing a definitive record of your organization’s OT will allow you to effectively assess risks and implement the proportionate security controls. Rather than focusing solely on individual assets, a holistic approach enables you to consider the broader context which leads to a better assessment of the criticality and potential impacts of compromises.
Your organization should aim to create a definitive record of all OT systems it owns and operates. Since this task can be complex and time-consuming, you should prioritize systems based on:
- The impact of the system to either your business function or the potential of national impact.
- Third party connections, particularly where these connections can change the configuration of system components (or have direct control over the process).
- The overall exposure of the system, taking into account how many connections the system has to external services where your organization does not set the configuration of security controls.
This guidance outlines the principles that organizations should aim to achieve when documenting their OT. They are goals rather than minimum requirements.
Record of Systems
Cybersecurity professionals should use these principles as a framework to develop a comprehensive record of their systems. This will require time and may present complexities, particularly in brownfield deployments. However, much of the information necessary to establish a definitive record is likely already available within your organizations.
This information may be in configuration files, existing documentation, or through monitoring and security tools. Identifying these existing resources is crucial for minimizing the burden of ongoing maintenance of the record.
Integrators and device manufactures should make these principles easier for organizations to achieve, through freely providing comprehensive documentation for supplied systems and offering tools that enable effective asset and configuration management.
It is especially important for operators to understand the design and implement appropriate security controls throughout the system’s lifecycle.
A definitive OT record enables organizations to conduct more comprehensive risk assessments, prioritize critical and exposed systems, and implement appropriate security controls. The guidance also addresses managing third-party risks, securing OT information, and designing effective architectural controls.
Key recommendations include:
- Collaborating across teams: Foster coordination between OT and IT teams
- Aligning with standards: Follow international standards such as IEC 62443 and ISO/IEC 27001
Organizations are encouraged to use this guidance to strengthen their OT security posture and reduce risks. Click here for more information on the guidance.

