An OT security program review is a structured check of how well an organization governs, operates and improves cybersecurity for its industrial control systems. An OT security audit asks a narrower question: does the organization do what its own policies, a chosen standard or a regulation say it should, and can it show evidence? In practice the two overlap, and many teams run them together. This article explains what each one covers, how it differs from a technical assessment, and how to prepare so the result is useful rather than a pile of findings nobody owns.
Program review, audit or assessment: what is the difference?
The terms are often mixed up, so it helps to separate them by the question each one answers.
- OT security program review. Is the overall program fit for purpose? It looks at governance, roles, risk management, policies, resourcing, supplier management and how improvements are tracked. The output is usually a maturity view and a prioritized roadmap.
- OT security audit. Are defined requirements being met, and is there evidence? The reference can be internal policy, IEC 62443-2-1 style program requirements, NIS2 obligations, or a sector rule such as NERC CIP. The output is a list of conformities and nonconformities with evidence references.
- OT cybersecurity assessment. How secure are the actual systems? It reviews assets, architecture, segmentation, remote access, hardening and vulnerabilities on site. Our OT cybersecurity assessment guide walks through that work in detail.
A program review without any technical sampling can miss that a well-written policy is not followed on the plant floor. A technical assessment without a program view can produce fixes that decay because nobody owns them. The most useful engagements combine a program review with targeted technical checks.
What an OT security program review covers
A good review follows the life of the program rather than a single document. Typical areas:
- Governance and accountability. Who owns OT cybersecurity: engineering, IT security, operations or a joint function? Is there a named owner per site and a reporting line to management?
- Scope and asset knowledge. Is there a current inventory of OT assets, sites and systems, and does the program actually cover all of them?
- Risk management. Is there a repeatable method for OT risk assessment, with risk owners, treatment decisions and review dates?
- Policies and procedures. Do OT-specific procedures exist for access, remote access, patching, backup, change management and incident response, and are they realistic for plants with limited maintenance windows? See OT policies and procedures.
- Architecture and access control. Are zones, conduits and the IT/OT boundary defined, documented and reviewed when systems change?
- Supplier and integrator management. Are security requirements included in contracts, and is vendor remote access controlled and logged?
- Vulnerability and patch handling. Is there a documented process to decide, per advisory, whether to patch, mitigate or accept, with compensating controls?
- Detection and response. Is there OT-aware monitoring, an incident response plan that includes operations and safety staff, and recent exercise records?
- Recovery. Are backups of controller programs, configurations and servers taken, stored offline and tested by restoring them?
- Awareness and competence. Do engineers, operators and contractors receive role-based OT security training?
- Measurement and improvement. Are findings tracked to closure, and does management review progress?
What an OT security audit checks
An audit uses the same areas but focuses on evidence. For each requirement in scope, the auditor asks for proof that it is defined, implemented and maintained. Typical evidence includes:
- approved policies with version history and review dates
- asset inventory exports and the date of the last verification
- firewall rule reviews and records of who approved changes
- remote access logs and supplier session approvals
- patch and vulnerability decision records per advisory
- backup restore test results
- incident response exercise reports and lessons learned
- training attendance records
Audits work best when the reference framework is agreed up front. Mixing several frameworks in one audit without a mapping usually produces duplicate findings. If you work with several frameworks, organize requirements and evidence once and map them, as described in our OT compliance readiness approach.
A practical OT security audit checklist
Use these questions as a quick self-check before a formal review:
- Can we name the owner of OT cybersecurity for every site?
- When was the OT asset inventory last verified against the plant?
- Is there a current network diagram showing zones and all external connections?
- Does every remote access path go through one controlled, logged route?
- Do we have a recorded decision for each relevant vendor advisory in the last quarter?
- Have we restored a controller program or HMI server from backup in the last year?
- Has the incident response plan been exercised with operations staff?
- Are open findings from previous reviews tracked with owners and dates?
If several answers are "no" or "not sure", start there. For a faster first view, try the free OT security quick check.
Frameworks to anchor the review
Several public frameworks help structure an OT program review without reinventing the wheel. NIST SP 800-82 Rev. 3 gives guidance on building an OT security program and maps it to the NIST Cybersecurity Framework. The CISA Cross-Sector Cybersecurity Performance Goals offer a short list of baseline practices that are easy to check. The IEC 62443 series addresses requirements for asset owners' security programs and for systems; our overview of IEC 62443 explains how the parts fit together. Standards are obtained from their publishers, and formal certification is issued only by accredited certification bodies.
How to get value from the result
A review is only as useful as what happens after it. Three habits make the difference:
- Prioritize by operational risk, not by number of findings. A single uncontrolled vendor connection can matter more than ten documentation gaps.
- Give every finding an owner and a date. Track findings with the same discipline as maintenance work orders.
- Repeat on a cycle. Many organizations review the program yearly and after major changes such as a new site, a merger or a large system upgrade.
OTVista researchers share methods like this to help teams run their own reviews. If you are preparing for an external audit, our notes on audit readiness cover how to keep evidence traceable.
Cover photo: Ümit Yıldırım on Unsplash, used under the Unsplash License.
Topics: ot security program review, ot security audit, ot cybersecurity audit checklist, ot security maturity assessment
