Access Official Technical PDF

Share Summary:LinkedInEmail

Industrial control systems (ICS) support processes where reliability and availability matter alongside cybersecurity. As these environments become more connected, industrial control system cybersecurity requires more than identifying technical weaknesses: organizations also need to understand which vulnerabilities could have the greatest operational impact and how they will coordinate a response. Research and discussions spanning industrial control security, vulnerability assessment and incident readiness point to a practical direction: combine structured risk analysis with closer cooperation between IT and operational technology (OT) teams.

Why industrial control system cybersecurity needs operational context

A vulnerability finding does not, by itself, explain the risk to an industrial operation. The severity of a weakness can be influenced by environmental factors, the probability of an attack exploiting it and the function of the affected host within the wider system. In a connected control environment, components may also depend on one another. A weakness in one system could therefore matter because of the role that system plays, not only because of its technical rating.

A proposed probabilistic Multi-Attribute Vulnerability Criticality Analysis (MAVCA) model addresses this challenge by combining three attributes: vulnerability severity as influenced by environmental factors, attack probability associated with the vulnerability, and functional dependencies of the affected host components. The purpose is to estimate impact and support prioritised remediation. A miniature ICS testbed was used to illustrate the model’s usability for identifying a weakest link and setting security priorities.

For engineering and security teams, the important principle is to assess vulnerabilities in relation to the system they affect. A list of findings can help identify known weaknesses, but prioritization also needs to consider how components contribute to operations and how a compromise might propagate through dependencies. This provides a more useful basis for deciding what to address first than treating every finding as an isolated issue.

Turn vulnerability findings into defensible priorities

Risk assessments can be affected by human subjectivity, which may lead to inconsistent or difficult-to-repeat findings. A separate approach described in research on automated vulnerability and risk analysis uses network and host information to build a model of a network, generate an attack graph and examine individual attack paths toward a defined objective. The system was tested in a virtual environment to demonstrate its practicality and usability.

Attack graphs represent possible paths through connected systems rather than viewing each vulnerability independently. Used as part of an assessment, this type of analysis can help teams consider how weaknesses might combine across a network. It also supports a more repeatable process when inputs and analytical steps are clearly defined. Automation does not remove the need for expert judgement, particularly when interpreting operational consequences, but structured analysis can make the basis for decisions clearer.

In practice, organizations can use this reasoning to connect vulnerability management with asset and dependency knowledge. Security and engineering teams should be able to discuss:

  • Which component or host is affected, and what function does it serve?
  • What other systems depend on it?
  • What attack paths or conditions could make exploitation possible?
  • How should the finding be prioritized in the context of operational impact?

These questions help translate technical findings into remediation decisions that can be understood across cybersecurity, controls engineering and operations.

Coordinate incident response across IT and OT

Incident response capacity is another part of industrial security. A study of cyber incident readiness in the Norwegian petroleum industry examined Computer Emergency Response Team (CERT) capacity for incidents involving industrial control and safety systems, with a focus on OT. Interviewees from petroleum companies were relatively satisfied with their current capacity while recognizing that it could improve. The study also identified a need for better coordination between IT and OT security.

That need reflects differences in terminology, the maturity of technical solutions and organizational culture. When IT and OT teams use different assumptions or response processes, it can be harder to establish a shared picture of an incident and coordinate action. Preparing for incidents therefore involves more than defining a technical escalation path. Organizations need clear contacts, shared understanding of relevant systems and communication between the people responsible for cybersecurity and operations.

The study also found that companies and drilling organizations shared information and experience through meetings and forums, but that systematic sharing of incident experience received less attention, particularly among smaller companies. CERT participants pointed to the value of stronger contact with key people in companies and identified a petroleum-sector information-sharing and analysis centre (ISAC) as a possible way to support coordination.

Make information sharing part of readiness

For plant managers and operations leaders, information sharing is useful when it improves preparedness without blurring responsibility for local decisions. Organizations can review how incident information reaches control-system owners, engineering teams, security personnel and external response contacts. They can also clarify what information can be shared, who is authorized to share it and how lessons from incidents feed into risk assessment and remediation.

Smaller organizations may have fewer dedicated resources for formal response structures. Regular contact with relevant CERT actors and participation in appropriate industry forums can help establish communication channels before an incident occurs. The available findings do not suggest a single response model for every organization; they emphasize the need to strengthen coordination and make information exchange more systematic.

Conclusion: connect risk analysis with response capability

Effective industrial control system cybersecurity links technical vulnerability analysis to operational context and incident readiness. Assess vulnerabilities alongside attack likelihood and system dependencies, and use structured methods to make prioritization more consistent. At the same time, build working relationships between IT and OT teams, establish clear response contacts and improve the sharing of incident experience. Together, these practices give industrial organizations a more grounded basis for deciding what to protect, what to remediate first and how to coordinate when a cyber incident affects control or safety systems.

Access Official Technical PDF

About The Author