Cyber Fusion Center Series

Change Your Roadmap

The CFC Baseline Assessment That Reveals Where Your OT Program Actually Stands

Organizations with comprehensive OT visibility contain ransomware incidents in an average of five days. The industry-wide average is 42 days. That difference isn't luck or budget. It reflects whether an organization accurately knows what it has, can see what's happening, and has tested what it would do when something goes wrong.

5 Days Average ransomware containment with comprehensive OT visibility
vs.
42 Days Industry-wide average containment time

Those three things are exactly what a structured CFC maturity assessment measures. And they're exactly what most organizations discover they've overestimated.

The 81% Problem

According to the Fortinet 2025 State of Operational Technology and Cybersecurity report, 81% of organizations self-assess their OT security maturity at Level 3 or 4 on a five-level scale. IEC 62443 defines Level 3 as processes that are practiced, repeatable and supported by evidence of consistent execution. Level 4 requires metrics demonstrating continuous improvement.

Independent data tells a different story. The SANS 2025 State of ICS/OT Security survey found that only about 12.6% of organizations have full visibility across the ICS Cyber Kill Chain. At the SCADA and HMI layer, where most OT attacks must operate to cause physical effects, just 10% report full visibility. Nearly one in three organizations still has no dedicated OT incident response plan.

Compliance confirms that policies exist. A structured maturity assessment confirms whether the program behind those policies actually works. Compliance scores are often a primary driver of the maturity gap -- we'll examine that dynamic specifically when we address the compliance trap in Article 8.

The CFC baseline assessment is designed to close the gap between reported and actual maturity. Executive sponsorship established the mandate. The accountability map identified who owns what. The maturity assessment is what comes next: establishing where the program actually stands before any further investment is made.

Four Domains, Four Gaps: What the CFC Assessment Reveals

The assessment covers four domains, each measured against IEC 62443 and NIST SP 800-82 Rev. 3 benchmarks. They represent the foundational capabilities every OT security program requires before investing in advanced detection or response technology.

The vCISO series covers why an honest external baseline matters from a leadership perspective -- what it changes about investment priorities and strategy decisions. This article covers the operational mechanics: what the CFC assessment actually does, what each domain reveals, and how findings drive roadmap sequencing.

Asset Inventory: Knowing What You Have

The assessment starts here because everything else depends on it. CISA's OT asset inventory guidance, published in August 2025, emphasizes that unmanaged and undocumented assets represent one of the most common and consequential gaps in critical infrastructure defenses. CISA published that guidance specifically because maintaining accurate inventories remains unsolved across critical infrastructure sectors.

OT asset discovery requires different methodology than IT discovery. Industrial environments use proprietary protocols -- Modbus, DNP3, EtherNet/IP and IEC 61850 -- that standard IT scanning tools cannot identify. Active scanning can disrupt operational devices, as NIST 800-82r3 explicitly warns. Field engineers frequently hold knowledge that documentation doesn't capture: the contractor's test device never removed from the network, the firmware updated during a maintenance window but never recorded.

The CFC assessment combines passive network monitoring, project file analysis, physical walkdowns of unmonitored segments and reconciliation with existing documentation. Common findings include assets in wrong segments, undocumented connections and firmware inconsistent with records. Those undocumented assets and connections are exactly the gaps the Shadow Current series describes -- the channels attack paths flow through when nobody is watching. The CFC assessment maps where they exist before an adversary finds them first.

Network Visibility: Seeing What's Happening

With an accurate asset picture established, the assessment evaluates whether the organization can see what those assets are doing. While 49% of organizations report having OT-specific detection capabilities, only about 12.6% have visibility across the full ICS Cyber Kill Chain. Visibility at the supervisory layer is even thinner, just 10%.

Fortinet's research adds a counterintuitive finding: since 2022, the percentage of organizations claiming 100% OT visibility has been steadily declining as programs improve and actual gaps become visible. That declining confidence is a sign of maturity, not weakness. The most confident organizations are often the ones that haven't looked closely enough.

The CFC visibility review evaluates monitoring coverage across Purdue Model levels one through three, zone and conduit mapping accuracy, wireless coverage gaps and whether a defined baseline of normal operations exists to detect against.

Governance and Accountability: Owning the Program

The governance domain evaluates whether the organizational structure supporting OT security is sound enough to actually act on what the assessment finds. According to PwC's 2026 Global Digital Trust Insights report, 39% of organizations lack clear governance and defined responsibility for OT cybersecurity. Another 40% report gaps in understanding the scope of their OT cyber risk.

The CFC governance review doesn't simply evaluate whether policies exist. It evaluates whether they're practiced, whether accountable people have the authority to act on findings, and whether compliance documentation reflects operational reality rather than audit-cycle reality. The accountability map built earlier in the engagement provides the baseline; the governance assessment validates whether it reflects how decisions actually get made.

Incident Response and Recovery: Ready When It Matters

The 2025 SANS survey found 57% of organizations have a dedicated OT incident response plan, a minor increase over prior years, but still leaving 43% without one. These are largely organizations that self-assess at Level 3 or 4.

The CFC IR evaluation examines whether the plan is OT-specific, whether it covers the boundary decisions a real incident requires, whether engineering teams hold response authority, and whether it has been tested against OT-specific scenarios -- not just a generic tabletop. Recovery capability is assessed separately: backup validation, tested restoration procedures and recovery time objectives defined by system criticality.

The cost consequences of weak recovery maturity are measurable. OT system recovery is three to four times more costly and time-consuming than IT recovery, according to Rockwell Automation. The average ICS/OT ransomware incident cost $4.73 million in 2025, per RunSafe Security. The five-day vs. 42-day containment split that opened this article traces directly to this domain.

How Findings Drive Roadmap Sequencing

The assessment produces a risk-scored gap map across all four domains. Prioritization is driven by risk score, asset criticality, operational impact and exploitability -- not by compliance calendar or audit deadline. Organizations that sequence investment by regulatory urgency frequently build advanced detection capabilities on top of open foundational gaps. Those capabilities don't hold.

Case Study: Kudelski Security

A Kudelski Security assessment of a mid-sized manufacturer with legacy control systems across multiple production lines shows the pattern clearly. Before the engagement, leadership was making investment decisions on an incomplete picture of their environment. After it, they could prioritize investments, improve governance and accelerate compliance against a realistic baseline.

The deliverable from the CFC assessment is not a maturity score or a compliance certification. It is a prioritized improvement roadmap that reflects where the program actually is, not where internal stakeholders estimated it to be. And this baseline isn't a one-time exercise -- the continuous validation loop covered in Article 12 requires repeating this assessment on a defined cadence, using the original baseline as the benchmark for measuring how far the program has come.

An honest baseline isn't an indictment. It is the starting point that makes every subsequent investment decision accurate rather than optimistic.

What an Honest Baseline Makes Possible

The Red Team series covers the adversarial counterpart to this structured assessment: testing whether the capabilities the CFC identifies as present actually hold under realistic attack conditions. But before adversarial validation, the program needs something else -- an accurate picture of who it is defending against.

An honest baseline shows where the program stands. OT-specific threat intelligence shows what it's standing against. Most organizations are missing both. In our next article, we'll examine what threat intelligence looks like when it's actually built for OT environments -- and how it feeds into the CFC operational model.

What Comes Next

Learn more about the OT vCISO role in The Missing Leadership Layer in Industrial Cybersecurity -- an executive brief covering why the CFC baseline changes both investment sequencing and organizational accountability.

An accurate baseline is the starting point every subsequent investment decision depends on.

81% of organizations overestimate their OT security maturity.
The gap between where your program is and where you think it is — that's where attacks live.

81% Self-assess OT maturity at Level 3 or 4
5 Days Containment with full OT visibility (vs. 42-day average)
43% Organizations without a dedicated OT incident response plan
$4.73M Average ICS/OT ransomware incident cost in 2025
📊 The Maturity Gap

81% claim Level 3+. Only 12.6% have full kill chain visibility. The gap between self-assessment and independent data is where attack paths are built.

Click to explore →

Fortinet 2025 shows 81% at Level 3 or 4. SANS 2025 found only 12.6% with full ICS Kill Chain visibility -- and just 10% at the SCADA and HMI layer. These are largely the same organizations. Compliance validates policies. The assessment validates whether the program works.

🗼 Asset Inventory

Everything else depends on knowing what you have. Most organizations find assets and connections their documentation never captured.

Click to explore →

OT discovery requires passive monitoring, project file analysis, and physical walkdowns. Standard IT tools miss Modbus, DNP3, and EtherNet/IP. Common findings include assets in wrong segments, undocumented connections, and firmware inconsistent with records. These are the Shadow Current channels attackers find first.

👁️ Network Visibility

49% report OT-specific detection. 12.6% have full kill chain visibility. The most confident organizations often haven't looked closely enough.

Click to explore →

The visibility review covers Purdue Model levels 1-3, zone and conduit mapping, wireless gaps, and whether a defined operational baseline exists to detect against. Since 2022, programs claiming 100% visibility have been declining -- a sign of maturity, not weakness.

🏛️ Governance

39% lack clear OT governance. The assessment evaluates whether policies are practiced -- not just documented.

Click to explore →

The governance review tests whether accountable people have authority to act on findings, and whether compliance documentation reflects operational reality vs. audit-cycle reality. 40% of organizations report gaps in understanding the scope of their own OT cyber risk (PwC 2026).

🚨 IR and Recovery

57% have a dedicated OT IR plan. 43% do not. These are largely the same organizations self-assessing at Level 3 and above.

Click to explore →

The evaluation tests OT-specific scenarios, boundary decisions, engineering response authority, and tested restoration procedures. OT recovery is 3-4x more costly than IT recovery. The 5-day vs 42-day containment split traces directly to this domain.

The 81% Problem: Data vs. Self-Assessment Why reported maturity rarely matches operational reality

Fortinet's 2025 report shows 81% of organizations self-assessing at IEC 62443 Level 3 or higher. Level 3 is not aspirational -- it requires processes that are practiced, repeatable, and supported by evidence of consistent execution. Level 4 requires continuous improvement metrics.

SANS 2025 independently measured what those programs actually look like from the outside:

  • Only 12.6% have full visibility across the ICS Cyber Kill Chain
  • At the SCADA and HMI layer, just 10% report full visibility
  • 43% have no dedicated OT incident response plan
  • These are largely the same organizations self-reporting Level 3+

The gap isn't dishonesty. Compliance scores are the primary driver -- policies are documented, audits are passed, and maturity scores are calculated against documentation rather than operational capability. The CFC baseline assessment tests the program against operational reality, not the audit record.

Inside the Four Domains Methodology and common findings across asset inventory, visibility, governance, and IR

Asset Inventory -- The CFC combines passive network monitoring, project file analysis, physical walkdowns of unmonitored segments, and reconciliation with existing documentation. Standard IT scanning tools miss proprietary OT protocols including Modbus, DNP3, EtherNet/IP, and IEC 61850. Active scanning can disrupt operational devices, as NIST 800-82r3 explicitly warns. Common findings include assets in wrong network segments, undocumented vendor connections, and firmware inconsistent with maintenance records.

Network Visibility -- The review evaluates monitoring coverage across Purdue Model levels 1-3, zone and conduit mapping accuracy, wireless coverage gaps, and whether a defined baseline of normal operations exists. Most organizations find visibility thinner than reported, especially at the field device layer where attacks must operate to cause physical effects.

Governance and Accountability -- The review tests whether accountable owners have authority to act, not just responsibility on paper. PwC 2026 data: 39% of organizations lack clear OT security governance, 40% report gaps in understanding their OT risk scope. The accountability map built earlier in the engagement is the baseline for this evaluation.

Incident Response and Recovery -- The IR evaluation examines OT-specific plan coverage, boundary decisions, engineering team authority, and whether the plan has been tested against OT scenarios rather than generic tabletops. Recovery assessment covers backup validation, restoration procedures, and recovery time objectives defined by system criticality.

From Assessment to Roadmap How findings drive sequencing, and what the Kudelski case study demonstrates

The assessment produces a risk-scored gap map across all four domains. Prioritization is driven by risk score, asset criticality, operational impact, and exploitability. Not by compliance calendar. Not by audit deadline.

Organizations that sequence investment by regulatory urgency frequently build advanced detection capabilities on top of open foundational gaps. Those capabilities don't hold because the visibility and inventory gaps that feed them are unsolved.

A Kudelski Security assessment of a mid-sized manufacturer with legacy control systems across multiple production lines illustrates the pattern. Before the engagement, leadership was making investment decisions on an incomplete picture of their environment. After the assessment, they could prioritize investments, improve governance, and accelerate compliance against a realistic baseline -- rather than an optimistic one.

The CFC baseline is not a one-time exercise. The continuous validation loop covered in Article 12 requires repeating this assessment on a defined cadence, using the original baseline as the benchmark for measuring how far the program has actually moved. An honest baseline isn't an indictment. It is the starting point that makes every subsequent investment decision accurate rather than optimistic.

Visibility Determines Velocity

The 5-day vs. 42-day containment split is not random. It traces directly to whether an organization can see what its assets are doing and has tested its response. Visibility is the prerequisite for every other capability.

Sequence by Risk, Not Compliance

Advanced detection built on foundational gaps doesn't hold. The assessment maps what's actually open -- and prioritizes closure by risk score and operational impact, not by the next audit deadline.

Honest Beats Optimistic

An accurate baseline changes every subsequent investment decision. Organizations that know where their program actually stands make better sequencing decisions than those operating on self-assessed maturity scores.

An honest baseline isn't an indictment. It is the starting point that makes every subsequent investment decision accurate rather than optimistic.

An accurate baseline is the starting point every subsequent investment decision depends on.

Scroll to Top