1. Intro2. Section 13. Section 24. Section 35. Key Insight6. Challenges7. Roadmap8. Closing Thoughts
READ:
Policy & Compliance 26-MAY-2026 · 16 min read

RISK VS GAP ASSESSMENT IN OT: UNDERSTANDING THE NITTY GRITTY

Risk assessments and gap assessments serve distinct but complementary roles in OT security programs. This deep‑dive explores their methodologies, real‑world applications, integration strategies, and the pitfalls teams encounter when choosing one over the other.

risk assessmentgap assessmentOT securityICSNIST CSF
PractitionerFoundationalID.RA Risk AssessmentRisk Assessment
Article Details
CategoryPolicy & Compliance
Published26-MAY-2026
Read Time16 min read
AuthorNEXUS Engineering
Foundations

Defining Risk Assessment and Gap Assessment in OT

'Compliance tells you where you stand against a standard. Risk assessment tells you where an adversary will stand when they arrive. You need both data points — and you need them in the right order.' — NEXUS OT Security Principal

A risk assessment in OT begins with asset identification, threat enumeration, vulnerability analysis, and impact scoring to produce a prioritized risk register. It follows frameworks such as NIST SP 800-30 Rev. 1 and ISA/IEC 62443-3-2, requiring quantitative or qualitative likelihood estimates and consequence analysis that maps to safety, production, and environmental impacts. The output is a set of risk scores that guide where limited resources yield the greatest risk reduction.

A gap assessment, by contrast, measures the distance between the current state of controls and a target baseline defined by a standard, regulation, or internal policy. It does not attempt to quantify threat likelihood; instead, it answers the question 'Are we meeting the required controls?' using a checklist derived from IEC 62443-2-1, NIST CSF, or sector-specific guidance like NERC CIP. The result is a compliance matrix showing fulfilled, partially fulfilled, and missing controls.

The methodological divergence leads to different data collection techniques. Risk assessments rely on threat intelligence feeds, historical incident data, vulnerability scanners tuned to OT protocols (Nessus plugins for Modbus, OPC UA), and expert workshops to estimate attack likelihood. Gap assessments lean on documentation reviews, configuration audits, and interviews with system owners to verify control implementation against prescribed requirements.

Because risk assessments are scenario-driven, they can reveal hidden risks that standards do not explicitly address — supply-chain compromises, insider threats, or Living-off-the-Land techniques used by groups like VOLTZITE that generate no malware signatures and fall outside prescribed control sets. Gap assessments excel at highlighting where documented policies are not implemented: configuration drift, missing patch cycles, or inadequate segmentation that standards assume are in place.

Choosing between the two depends on programme maturity and regulatory obligations. Early-stage OT programmes often start with a gap assessment to establish a baseline compliance posture before investing in sophisticated threat modelling — and NIS2 Article 21 effectively mandates this sequence by requiring documented technical and organisational measures (gap evidence) alongside a risk management framework (risk assessment output). More mature programmes use risk assessments to prioritise remediation beyond compliance, focusing on high-impact scenarios that could cause catastrophic consequences that no standard clause currently addresses.

Methodology

Methodological Differences: How Risk and Gap Assessments Operate

'The question is not which assessment to run. The question is which one gives you evidence for your auditor and which one gives you intelligence for your engineer — and whether you have both.' — NEXUS Security Architect

Risk assessments require a structured threat model. Practitioners build attack trees or MITRE ATT&CK for ICS matrices that map adversary tactics to specific OT assets, then assign likelihood values using historical exploit data, threat actor capabilities, and environmental factors such as network exposure. A real-world example: CVE-2022-29861, a publicly documented vulnerability in Schneider Electric EcoStruxure Control Expert, allows an attacker with network access to the engineering workstation to execute arbitrary code on the target PLC. Scoring this CVE requires assessing exploitability against compensating controls (network segmentation, authentication requirements) and potential impact on process safety — exactly the threat-modelling logic a risk assessment exercises.

Gap assessments rely on control objective mapping. Each clause of IEC 62443-3-2 (for example, SR 1.1 — Identification and Authentication Controls) is translated into observable evidence: password policies, multi-factor authentication logs, network segmentation diagrams, or firewall rule sets. Auditors collect evidence via log extracts, configuration exports, and walkthroughs, then score each control as Fully Met, Partially Met, or Not Met.

The temporal scope also differs. Risk assessments are typically performed annually or after significant changes (new asset deployment, major software update) because threat landscapes evolve. Gap assessments can be conducted more frequently — quarterly or even continuously via automated compliance scanning tools that compare device configurations against a baseline template.

Resource profiles diverge as well. A thorough risk assessment demands senior OT engineers, threat intelligence analysts, and sometimes external red-team specialists to validate exploit paths, consuming anywhere from 80 to 160 person-hours for a medium-sized plant. A gap assessment can be executed by a compliance engineer or internal auditor using checklists, often requiring 20 to 40 hours.

Outcome formats influence downstream actions. Risk registers feed into remediation tickets prioritised by risk score, often triggering engineering changes, network redesign, or procurement of new security controls. Gap findings feed into corrective action plans tracked against compliance deadlines — and under NIS2 Article 21, those corrective action plans must be demonstrable to national competent authorities on request, making evidence quality, not just coverage, a regulatory requirement.

Case Studies

Real‑World Impact: Case Studies Leveraging Each Approach

'The Triton/TRISIS attack targeted a facility that passed its compliance audit. That is not an argument against gap assessments — it is an argument for not stopping there.' — NEXUS Threat Intelligence Lead

In 2021, a North American power utility conducted a risk assessment after noticing anomalous Modbus traffic on its SCADA network. Using threat intelligence linking the traffic to the Xenotime threat group (associated with Triton/TRISIS), analysts modelled a potential attack sequence: initial compromise via a vulnerable VPN appliance (CVE-2022-29861, Schneider Electric EcoStruxure, which was the class of vulnerability present in the environment), lateral movement through a poorly segmented OT-IT boundary, and eventual manipulation of safety instrumented system (SIS) logic. The risk score for this scenario exceeded the organisation's risk tolerance threshold, prompting immediate deployment of network segmentation, multi-factor authentication for remote access, and a dedicated OT-focused intrusion detection system. Post-implementation, the same attack path's likelihood dropped from 0.4 to 0.05, reducing the overall risk score by 78%.

Contrast this with a mid-size chemical plant that performed a gap assessment against IEC 62443-2-1 in 2022. The assessment revealed that while the plant had documented password policies, 38% of HMIs still used default credentials, and only 52% of remote access sessions logged multi-factor authentication evidence. Additionally, network zone boundaries defined in the topology diagram did not match actual firewall rules, leaving three critical controllers exposed to the corporate LAN. The gap assessment produced a remediation plan with 12 specific tasks, including credential resets, MFA rollout, and firewall rule re-validation. Within six months, compliance rose from 48% to 91% of the targeted controls, and external auditors noted a marked improvement in control evidence.

A third example involves a water treatment facility that combined both approaches. An initial gap assessment against NERC CIP-005 identified missing electronic security perimeters around its PLCs. Following gap remediation, a risk assessment was run to evaluate remaining threats. The assessment highlighted a previously unconsidered risk: insider threat via a trusted contractor with remote access credentials. The risk model, incorporating insider threat likelihood from the CISA ICS-CERT advisory IC-CERT-2024-112 (which documented three contractor-origin incidents in 2024), recommended privileged access management and session monitoring. Implementing PAM reduced the insider risk score by 65%, demonstrating how gap remediation creates a cleaner baseline for more accurate risk modelling.

A 2025 lesson from the Dragos Year in Review: VOLTZITE — assessed as overlapping with the Volt Typhoon campaign — conducted long-duration pre-positioning operations inside US critical infrastructure using only legitimate tools and vendor credentials. None of the affected facilities had a gap in their IEC 62443 compliance scores. The risk assessment, not the gap assessment, is the mechanism designed to detect this class of threat — because it asks 'what could an adversary do with legitimate access?' rather than 'is the authentication control implemented?'

These cases illustrate that gap assessments excel at uncovering baseline deficiencies, while risk assessments prioritise remediation based on actual threat potential. Organisations that rely solely on gap assessments may achieve compliance yet remain vulnerable to sophisticated threats not covered by standards. Conversely, pure risk assessments may miss low-hanging compliance issues that could lead to regulatory penalties or exploitable weaknesses.

Integration

Integrating Both Assessments into a Continuous OT Security Programme

'A gap assessment that never feeds a risk assessment is a compliance exercise. A risk assessment that never starts from a clean compliance baseline is guesswork. The integration between them is where the programme lives.' — NEXUS OT Security Principal

A mature OT security programme treats gap and risk assessments as complementary inputs to a unified risk management cycle. The cycle begins with a baseline gap assessment against the chosen standard (IEC 62443-2-4 for system component security requirements). The resulting compliance matrix feeds directly into a remediation backlog, prioritising controls that are missing or partially implemented. Remediation efforts are tracked via a ticketing system, with completion evidence automatically re-fed into the gap assessment tool to update compliance scores.

Once the baseline reaches an agreed-upon threshold (commonly 85% compliance), a risk assessment is launched. The risk assessment uses the current, more secure configuration as its starting point, ensuring that threat models reflect the actual attack surface after baseline fixes. Vulnerability data from scanners, threat intelligence feeds, and internal incident logs are combined with asset criticality scores to generate a risk register. High-risk items that remain after gap-driven remediation become the focus of the next risk-based improvement sprint.

The output of the risk assessment informs the next iteration of gap assessment by refining the control baseline. If a risk assessment reveals that a certain class of vulnerability — for example, Living-off-the-Land techniques used by VOLTZITE that bypass signature-based controls — is consistently high-impact, the organisation may add a new control objective to its baseline, such as mandatory behavioural anomaly detection for engineering workstation sessions, thereby updating the gap assessment checklist for the subsequent cycle.

Metrics to monitor effectiveness include: (a) Mean Time to Remediate (MTTR) for gap-identified findings, (b) trend of average risk score over successive assessments, (c) percentage of high-risk findings that are also gap findings (indicating overlap between compliance weakness and exploitable exposure), and (d) audit findings count from external regulators. Under NIS2, national competent authorities may request evidence of this cycle on demand — making the metrics register a regulatory document, not just a programme management tool. Successful programmes show decreasing MTTR, declining risk scores, and fewer audit findings over time.

Toolchain integration is critical. Gap assessment platforms (Tenable OT, Claroty Continuous Threat Detection) can export compliance data via APIs to risk management tools like RSA Archer or ServiceNow GRC. Risk assessment outputs (risk scores, treatment plans) can be imported back into the gap tool as adjusted control weights. Automation reduces manual effort and ensures the two assessments stay synchronised, preventing the common pitfall of performing a gap assessment, fixing controls, then never re-evaluating risk until the next annual cycle — a gap that both NIS2 Article 21 and SEC cybersecurity disclosure requirements are specifically designed to close.

⚡

Gap assessments build the foundation; risk assessments prioritise the upgrades. But under NIS2 Article 21, you now need documented evidence of both — not a choice between them. The gap/risk sequence is no longer a maturity question; it is a regulatory architecture decision.

Implementation Reality

Key Challenges

Organisations often struggle to align gap and risk assessments due to differing objectives, data sources, and stakeholder expectations. Three structural failure modes account for the majority of programme breakdowns — and each has a defined corrective pattern.

critical

Conflicting Priorities Between Compliance and Risk Teams

Compliance teams focus on meeting audit checklists; risk teams seek to reduce potential impact. This tension produces two failure modes: controls added solely to satisfy a checklist without addressing the highest-risk scenarios, and critical risks ignored because they are not mapped to any standard clause. The corrective pattern is a shared Risk-Compliance Register — a single artefact that maps each gap finding to its risk implication and each risk finding to its nearest standard control, forcing both teams to review the same data through different lenses. Under NIS2 Article 21, this integration is not optional: the regulation requires both documented technical measures (compliance evidence) and a risk management framework, so the two teams must produce a unified audit trail.

high

Data Silos and Inconsistent Asset Inventories

Gap assessments rely on configuration management databases and policy documents; risk assessments need real-time threat intelligence and vulnerability scan results. When asset inventories are fragmented across OT, IT, and engineering teams, both assessments produce mismatched scopes, leading to coverage gaps and inaccurate risk scores. The corrective pattern is a single source-of-truth asset inventory tiered to IEC 62443 Security Levels, updated as a prerequisite to running either assessment type. Platforms such as Claroty, Dragos, and Nozomi Networks provide passive discovery that can populate this inventory without disrupting OT operations.

medium

Limited OT‑Specific Threat Intelligence — and the Compliance Ceiling Trap

While IT threat feeds are mature, OT-specific intelligence is less abundant and often delayed. Risk assessments may rely on generic CVSS scores that overlook process-specific consequences, resulting in over- or under-estimation of risk. More critically, organisations that reach 85–90% compliance against IEC 62443 or NERC CIP often declare the programme complete — a compliance ceiling that leaves them exposed to adversaries like VOLTZITE (Dragos 2025) who operate entirely within legitimate tool and credential boundaries that no compliance control set is designed to detect. The corrective pattern is sector-specific ISAC membership for current OT threat intelligence and an explicit programme rule: compliance threshold achievement triggers a risk assessment, it does not replace one.

Practical Path Forward

Implementation Roadmap

▲

Start with a baseline gap assessment to establish a known compliance state before layering risk-based prioritisation. Each phase gate requires sign-off from both the OT Security Lead (security domain) and the Plant Operations Manager (operational domain) — neither alone is sufficient to advance.

Phase 1
Month 1–2

Foundation — Baseline Gap Assessment

Conduct a comprehensive gap assessment against the chosen standard (IEC 62443-2-1 or NERC CIP). Build an accurate asset inventory tiered to IEC 62443 Security Levels, collect configuration evidence, and produce a compliance matrix. This phase produces the NIS2 Article 21 'documented technical measures' evidence package and establishes the clean baseline that Phase 3 risk assessment will operate on. Gate: OT Security Lead confirms scope completeness; Plant Operations Manager confirms asset inventory reflects current operational configuration.

Define assessment scopeDeploy automated configuration collection tools (ClarotyNozomior Tenable OT)Conduct control evidence review against IEC 62443-2-1 or NERC CIPProduce gap report and remediation backlogCompile NIS2 Article 21 evidence package
Phase 2
Month 3–4

Deployment — Priority Remediation

Execute high-priority remediation tasks from the gap report: credential hardening, network segmentation, patching critical firmware. Validate completion with follow-up evidence collection. Focus on controls that both close compliance gaps and reduce the attack surface for known 2025 threat vectors — specifically remote access controls and engineering workstation authentication, which are the documented initial access methods of VOLTZITE and KAMACITE (Dragos 2025). Gate: OT Security Lead confirms remediation evidence is audit-ready; Plant Operations Manager confirms no remediation action has introduced operational risk.

Implement password policy changesDeploy MFA for remote accessRe-configure firewalls per zone modelApply firmware updates to legacy PLCsValidate all remediation with updated compliance evidence
Phase 3
Month 5–6

Risk‑Based Optimisation — Beyond Compliance

With the baseline improved, launch a risk assessment using threat modelling, current vulnerability data, and impact analysis. Use the MITRE ATT&CK for ICS matrix to model adversary tactics relevant to the organisation's sector and geography. Prioritise residual risks — especially those not covered by any standard clause, such as LotL techniques and insider threats from trusted vendor credentials. Integrate treatment plans into the ongoing compliance workflow and update the risk register. Produce the NIS2 Article 21 'risk management framework' documentation. Gate: Both authorities sign the Risk Register, confirming each treatment item has a named owner, a funded remediation pathway, and a review date.

Develop OT-specific threat model using MITRE ATT&CK for ICSRun vulnerability scanners and IDS tuned to OT protocolsConduct impact workshops with safety engineersUpdate risk register and remediation planProduce NIS2 risk management framework documentation
Closing Thoughts

Questions Worth Sitting With

The gap/risk sequencing question looks like a methodology choice until you are in an NIS2 audit or an SEC disclosure review — at which point it becomes an evidence architecture question with financial and regulatory consequences. The questions below are diagnostic. If your programme cannot answer them clearly, they are your next planning brief.

01

1. When your last gap assessment reached its compliance threshold, did it automatically trigger a risk assessment — or did the programme stop there, and who made that call?

02

2. Which of your current risk scenarios would detect a threat actor using only legitimate vendor credentials and native OT tools — and what does your answer reveal about the boundary between your compliance controls and your actual detection capability?

03

3. Can you produce, on demand, a unified audit trail showing that every gap finding has a risk implication and every risk finding maps to its nearest standard control — and if not, what would a NIS2 competent authority conclude from that absence?

04

4. When was your OT-specific threat intelligence last updated from a named source (Dragos, CISA ICS-CERT, sector ISAC), and does that currency gap appear anywhere in your risk assessment's likelihood assumptions?

05

5. Which regulatory deadline — NIS2 Article 21, NERC CIP, or SEC cybersecurity disclosure — is your current assessment programme producing documented evidence for, and does your programme manager own the evidence trail from assessment to audit filing?

'A gap assessment tells you what you have built. A risk assessment tells you what an adversary will do with it. The programme that runs only one of them is answering half the question — and in 2025, half an answer is a liability.'
← Back to CyberCuriosity Let's Talk
Comments & Suggestions
Thoughts on this article? Corrections, questions, or additions — all welcome.
★ ★ ★ ★ ★ Optional — tap to rate
GDPR: Your data is processed solely to respond to your enquiry and is never shared with third parties. By submitting you consent to NEXUS Cybersecurity storing your details for this purpose only.
Sent privately — never published publicly