Five questions every CISO should ask about OT cybersecurity
Chief information security officers (CISOs) need to know who is involved in operational technology (OT) cybersecurity and should know why they're getting involved in the first place when beginning this journey.
Companies have been protecting information technology (IT) systems for years, but do they really need to worry about operational technology (OT) security? The answer is a definite yes. Chief information security officers (CISOs) should consider these five questions when getting started.
1. Who should be involved in the OT security program?
This is the first question for a reason. In many information technology (IT) organizations, the answer is clear. Security requires networking, endpoint, cloud, regulatory and other IT partners. In operational technology (OT) security, however, getting the “who” right is critical and often more complex.
Depending on the organization, the who may include the head of process control technology; the SVP/EVP/VP of operations, manufacturing or supply chain; influential plant managers; or quality or similar regulatory personnel. This is on top of the more typical groups involved in IT security.
We have seen many organizations stall if key operations personnel are not included early in the process to identify bottlenecks or technical challenges. Successful chief information security officers (CISO) create a steering committee of IT and OT personnel in addition to the operations leaders who understand the technical challenges of the systems.
Without this joint team, organizations struggle to gain buy-in for the necessary technical changes and required support personnel to achieve success. Together, this group forms the right process for deciding aspirations, technical feasibility and more.
2. Where should you begin your OT cybersecurity journey?
Almost all industrial companies have some level of cybersecurity underway, but often the question is where to focus first to improve the security of the OT systems. Options usually include network protection such as segmentation and separation, endpoint protection, network anomaly detection, asset visibility, and inventory for improved vulnerability management, security event monitoring and analysis.
There is no absolute right answer to this. Some will argue for deploying network protection technology to create a barrier. Others will argue for vulnerability assessment or asset visibility and inventory.
The right answer depends on the organization’s starting point. However, the foundation of all these initiatives is a robust asset inventory with “360-degree” visibility on hardware, software, network connections, users and accounts, vulnerabilities, etc. To make network protection effective, you must know what you are protecting and how it needs to communicate. To make proper vulnerability management decisions, you need clarity of the comprehensive 360-degree risk, because not all assets in OT can be patched or upgraded. Alternative compensating controls may be needed, and prioritization is key. Security event monitoring requires knowledge of the assets to monitor, as well as their operations and asset criticality.
This 360-degree approach provides a comprehensive view of the risks and how they interact. For instance, two devices may have similar vulnerability or patch status, but one has application whitelisting locked down, a robust backup, hardened configuration settings and sits behind a well-configured firewall, whereas another does not. Or one operates critical operational processes, whereas the other does not. Even more so than in IT, these relative priorities are critical in OT given the challenges of taking rapid remediating actions.
3. Why do you need an OT security program?
This is the most obvious question. CISOs have protected IT systems for more than a decade. You likely have dozens of tools at your disposal to address cybersecurity according to Check Point, Gartner and others. So why in the world do you need a specific OT cybersecurity program?
The reality is these systems truly are different but perhaps not in exactly the ways OT folks or original equipment manufacturer (OEM) vendors often say. They are sensitive to change or traditional IT security scanning. They are highly integrated. They do operate many legacy operating systems due to long lifecycles. They include many embedded systems that cannot be scanned or managed in the same way a Windows PC or cloud server can. And the downside risk of acting on a false security alarm can be operationally devastating.
4. What security management actions should be included in the program?
Many organizations become hamstrung with the actions they can take to secure their OT/ICS environments. In part due to the fear, uncertainty and doubt raised by OEM vendors or some in OT, organizations limit what can be done to secure these systems. Perhaps they limit themselves to segmentation or network monitoring because of the fear of managing these sensitive systems.
Our suggestion is to employ OT systems management. These are the same techniques IT conducts on IT systems (and actually represent more than 70% of all IT security tasks). This includes functions such as patching, vulnerability management, configuration management, user and access management, and more.
This comprehensive set of management actions ensures protection and hardening of these devices in advance, as well as the detection of anomalies from ongoing attacks. They also align IT and OT security into consistent practice areas that can be monitored and tracked.
5. How should an OT security program be managed?
There is no one perfect way to manage a cybersecurity program. It depends on the way the organization is structured more broadly. Is the culture top-down with a drive for operational consistency, even if it may take longer to align different parts of the organization? Is the culture one where targets are set, but business units are left to determine how best to hit those targets? Is there a close working relationship between IT and OT? These subquestions inform how best to organize your approach.
There are several key elements regardless of the overall structure:
- Establish a target early on that allows for measurement and tracking. We have seen great success leveraging the Center for Internet Security top 20, but there are other targets and models to use. Selecting one is key.
- Gain alignment between IT and OT and leverage each for the strengths they bring.
- Build traction early with visibility into key risks and by addressing key vulnerabilities and risks.
- Create accountability by adding security into balanced scorecards to ensure results have an impact on performance.
– This article originally appeared on Verve Industrial’s website. Verve Industrial is a CFE Media content partner. Edited by Gary Cohen, Senior Editor/Project Manager, CFE Media and Technology, firstname.lastname@example.org.