Operational technology involves systems that monitor or control physical processes. NIST explains that securing OT requires attention to its particular performance, reliability, and safety needs. That context helps explain why an OT project needs an understanding of operations before measures are defined.
Identify the people who need to participate
In addition to IT or security, the discussion may need operations, maintenance, and system providers. Knowing who understands the systems and who authorizes changes makes subsequent work easier to organize.
Define the environment
Prepare an overview of the installations, networks, and assets to be addressed. Include relevant connections and third-party access needs. The initial conversation can help identify missing information.
Explain how work can take place
Share the conditions affecting testing, implementation, and validation. The team needs to understand how tasks are coordinated with the installation's activities and which responsibilities each party will take on.
Separate implementation from recurring operation
Define the expected project outcome and the tasks that continue afterward. Maintenance, administration, monitoring, or response should be described when they are included.
Agree on deliverables and validation
Ask what documentation will be provided, what will be validated, and how knowledge will be transferred. A clear proposal supports both technical work and collaboration between teams.
Vanguard's specialist team implements Fortinet OT solutions. The initial discussion helps define the combination and scope suited to each environment.
Source: NIST SP 800-82, Guide to Operational Technology Security.
