OT Cybersecurity Assessment: What Should an Industrial Site Actually Check?

OT Cybersecurity Assessment: What Should an Industrial Site Actually Check?

An OT cybersecurity assessment should do more than identify vulnerable devices. It should establish what is connected, how industrial systems communicate, who can access them, where trust boundaries exist, and which weaknesses could affect safe and reliable operations.

Operational technology environments are different from conventional enterprise networks. A PLC, SCADA server, engineering workstation or industrial network device may directly support a physical process. Security decisions therefore need to account for availability, reliability, safety and operational continuity alongside traditional cybersecurity concerns.

A useful assessment connects technical evidence with operational risk. The result should help engineers and decision makers understand what needs attention first, why it matters, and what can realistically be changed without creating unnecessary disruption.

What Is an OT Cybersecurity Assessment?

An OT cybersecurity assessment is a structured review of the technology, architecture, connectivity, access controls, vulnerabilities and security practices surrounding an operational technology environment.

The objective is not simply to produce a list of weaknesses. A useful assessment should establish the organization’s current exposure, identify important security gaps, examine existing controls and provide a practical path toward reducing the most significant risks.

NIST describes operational technology as programmable systems and devices that interact with the physical environment or manage systems that do so. Its scope includes industrial control systems, transportation systems, building automation, physical access control and other operational environments.

That physical relationship changes the security assessment. A security action that is routine in an office environment can have very different consequences when applied to a production control system.

Why OT Security Assessment Is Different From an IT Security Audit

A conventional IT security assessment may focus heavily on endpoints, servers, applications, identity systems and known vulnerabilities. OT requires a wider view because the environment can contain systems with different owners, maintenance cycles, operating requirements and safety implications.

A typical industrial environment may include PLCs, RTUs, HMIs, SCADA servers, historians, engineering workstations, industrial switches, firewalls, remote access systems and legacy equipment.

The assessment therefore needs to understand not only whether a technical weakness exists, but also where the affected asset sits in the operational architecture and whether an attacker could realistically reach it.

1. Start With the OT Asset Inventory

You cannot make a reliable security assessment if the organization does not know what it has.

An OT inventory should go beyond a list of IP addresses. Where the information is available, each important asset should be associated with its manufacturer, model, software or firmware version, location, function, owner, criticality and relevant communication relationships.

Depending on the environment, the inventory may include:

  • PLCs
  • RTUs
  • HMIs
  • SCADA servers
  • DCS components
  • Engineering workstations
  • Historians
  • Industrial switches
  • Firewalls
  • Remote access systems
  • Servers supporting OT operations
  • Backup systems
  • Safety related systems

Asset visibility is foundational because vulnerability management, incident response and security architecture all depend on knowing which systems exist and what role they perform.

2. Understand the Network Architecture

An asset list tells you what exists. The network architecture tells you how those assets interact.

The assessment should identify the major network zones, communication paths and trust boundaries within the environment.

Depending on the architecture, this may include enterprise networks, an industrial DMZ, operations networks, control networks, cell or area networks, engineering environments, remote maintenance connections and third party connections.

The important question is not whether the network diagram looks sophisticated. It is whether communication between security boundaries is intentional, documented and appropriately controlled.

3. Review Internet and External Exposure

An industrial environment should not be assumed to be isolated simply because it is described as an internal network.

External exposure can occur through remote access systems, VPN gateways, cloud services, vendor infrastructure, management interfaces or connections between business and operational environments.

An external review can use passive sources such as DNS information, certificate records, IP intelligence and authorized Internet exposure searches to identify systems that deserve further investigation.

The important distinction is between visibility and vulnerability. Finding a service exposed to the Internet does not by itself prove that the service is exploitable.

4. Examine Remote Access

Remote access deserves specific attention because it can connect people outside the facility to systems inside the operational environment.

The assessment should establish:

  • Who can access the environment?
  • Which systems can they reach?
  • How is identity verified?
  • Is multi factor authentication used where appropriate?
  • Is access permanent or time limited?
  • Can vendor accounts be disabled quickly?
  • Are remote sessions logged?
  • Can remote users reach sensitive control systems directly?
  • Are remote connections separated from critical control networks?
  • Are third party connections documented?

Vendor and maintenance access deserves particular attention because these relationships can introduce access paths that are outside the direct control of the plant.

5. Review Network Segmentation

Segmentation is not simply a matter of drawing separate boxes on a network diagram. The assessment needs to determine whether the intended boundaries are actually enforced through architecture, firewall policy, access controls and communication rules.

Important questions include:

  • Can enterprise systems communicate directly with control systems?
  • Is there an appropriately controlled industrial DMZ?
  • Which systems can communicate across security boundaries?
  • Are firewall rules documented?
  • Are unnecessary services permitted?
  • Can engineering workstations reach more systems than required?
  • Can remote access bypass intended segmentation?

Good segmentation reduces unnecessary trust relationships and makes communication between different parts of the environment easier to control and monitor.

6. Examine Industrial Network Traffic

Architecture diagrams describe intended communication. Network traffic can show what is actually happening.

A controlled packet capture can provide evidence about communication between industrial systems and help establish whether observed traffic matches the expected operational baseline.

Depending on the environment, an analyst may examine:

  • Source and destination relationships
  • Industrial protocols
  • Unexpected communication
  • Unknown endpoints
  • Repeated connection attempts
  • Cleartext administrative traffic
  • Unexpected external communication
  • Changes from an established communication baseline

Wireshark can be useful for packet level investigation, but the value comes from interpreting traffic in the context of the industrial process.

An unusual packet is not automatically a security incident. The analyst needs to understand which system generated it, whether the communication is expected and what operational function it supports.

7. Review Vulnerabilities in Operational Context

An OT vulnerability assessment should not become a spreadsheet containing hundreds of vulnerability identifiers with little operational context.

A useful assessment connects vulnerability information to the actual environment.

QuestionWhy It Matters
What asset is affected?Establishes the actual scope of the issue.
Where is the asset located?Shows its position within the operational architecture.
Is the vulnerable service reachable?A weakness without a realistic attack path can have a different risk profile.
What controls already exist?Segmentation and access controls can reduce exposure.
What is the operational role?The consequences depend partly on the function and criticality of the asset.
Can remediation be performed safely?Production constraints may affect patching or configuration changes.

This approach produces a risk based assessment rather than a vulnerability catalogue.

8. Review Authentication and Privileged Access

Access control should be reviewed across both human users and technical accounts.

The assessment should look for:

  • Shared administrator accounts
  • Unused accounts
  • Former employee access
  • Vendor accounts that remain active
  • Excessive privileges
  • Weak credential management
  • Uncontrolled service accounts
  • Inadequate authentication for sensitive access

Older industrial systems may have technical limitations that prevent modern identity controls from being deployed directly. The assessment should document those limitations and identify appropriate compensating controls instead of applying enterprise IT requirements without considering the operational environment.

9. Review Logging and Security Monitoring

An organization cannot investigate an incident effectively if it has little evidence of what happened.

The assessment should identify which security relevant events are available and where those records are stored.

  • Firewall logs
  • Remote access logs
  • Authentication records
  • Engineering workstation activity
  • Network monitoring data
  • Industrial protocol monitoring
  • System alarms

The objective is not to collect every possible log. It is to retain enough relevant evidence to detect, investigate and respond to meaningful events.

10. Review Backup and Recovery Capability

Prevention is only one part of resilience.

The assessment should determine whether critical configurations, programs and operational data can be recovered after equipment failure, malware, accidental change or a security incident.

  • Are PLC programs backed up?
  • Are HMI and SCADA configurations protected?
  • Are backup copies isolated from production systems?
  • Are backups tested?
  • Are restoration procedures documented?
  • Does the organization know which systems must be restored first?

A backup that has never been tested should not be treated as a proven recovery capability.

11. Review Third Party and Vendor Dependencies

Industrial environments often depend on equipment manufacturers, system integrators, maintenance contractors and technology vendors.

These relationships can introduce additional access paths and operational dependencies.

  • Who maintains each critical system?
  • Who can access it remotely?
  • Which vendor accounts exist?
  • How are credentials managed?
  • What happens when a contract ends?
  • Are vendor connections documented?
  • Are responsibilities defined during a security incident?

12. Do Not Start With Aggressive Scanning

One of the most important differences between OT security work and ordinary network testing is the potential operational impact of active testing.

Tools such as Nmap can support network discovery and security assessment, but active scanning of production OT systems should depend on authorization, architecture, asset criticality and controlled testing conditions.

NIST specifically warns that active scans introduce traffic and directly interact with devices within the scan scope. Depending on the equipment, this can create instability or affect device and process state. NIST recommends extreme caution and advises scheduling active scans during planned OT outages where possible.

A safer assessment sequence is often:

  1. Understand the industrial process.
  2. Collect existing documentation.
  3. Build an initial asset inventory.
  4. Review the network architecture.
  5. Review external exposure.
  6. Review remote access.
  7. Use passive evidence where practical.
  8. Validate findings.
  9. Perform controlled active testing only when appropriate.
  10. Prioritize remediation according to operational risk.

What Should an OT Cybersecurity Assessment Deliver?

A useful assessment should produce more than a technical findings list. It should give the organization a clear picture of its current exposure and a prioritized path forward.

  • OT asset inventory or inventory gap analysis
  • Network architecture review
  • External exposure findings
  • Remote access review
  • Segmentation review
  • Vulnerability and configuration findings
  • Security monitoring observations
  • Backup and recovery observations
  • Third party access findings
  • Risk prioritized remediation plan

How to Prioritize OT Security Findings

Not every finding deserves the same response.

A practical prioritization method should consider the affected asset, exposure, attack path, operational criticality, existing controls and potential consequences.

PriorityTypical SituationRecommended Response
CriticalHigh consequence asset with a realistic and insufficiently controlled attack path.Immediate risk reduction and management attention.
HighImportant weakness with meaningful exposure or inadequate compensating controls.Prioritized remediation plan.
MediumSecurity weakness with limited exposure or stronger existing controls.Address through planned improvement.
LowLimited practical exposure or low consequence issue.Track and address during normal maintenance.

These categories should not replace the organization’s own risk methodology. They provide a practical way to communicate technical findings in operational terms.

What a Good OT Assessment Should Answer

At the end of an assessment, decision makers should be able to answer a small number of important questions.

  1. What OT assets do we actually have?
  2. Which assets are most important to operations?
  3. How are those assets connected?
  4. Where can external or third party users reach the environment?
  5. Which communication paths cross important trust boundaries?
  6. Which vulnerabilities or configuration weaknesses matter most?
  7. Can we detect suspicious activity?
  8. Can we recover critical systems after an incident?
  9. Which risks should be addressed first?
  10. What can be improved without unnecessarily disrupting production?

If an assessment cannot answer these questions, it may have produced technical data without producing enough decision value.

Final Perspective

An OT cybersecurity assessment should begin with understanding the industrial environment, not with a scanning tool.

The strongest assessment combines asset visibility, architecture analysis, exposure review, remote access analysis, segmentation review, controlled technical testing, vulnerability context and operational risk.

The objective is not to make an industrial network look secure on paper. It is to identify the weaknesses that matter, understand how they could affect operations, and give the organization a practical sequence for reducing those risks.

For smaller industrial organizations, an independent assessment can provide a practical starting point before investing in a larger cybersecurity program. The assessment should leave the organization with clearer visibility, better priorities and evidence that can support future engineering and security decisions.

Need an Independent OT Security Assessment?

Cautivra provides focused remote security assessments for organizations that need a practical review of their OT exposure, architecture, remote access, asset visibility and security risks.

The engagement can be scoped around available documentation, network information, approved evidence and operational constraints.

Request an OT Security Assessment

Sources and Further Reading

  • NIST SP 800-82 Rev. 3, Guide to Operational Technology Security
  • CISA, Foundations for OT Cybersecurity: Asset Inventory Guidance
  • NIST Operational Technology Security resources

Leave a Reply