Page 1 of 1

SME Questionnaire Form - December 1

Publication Target Date: December 1

Submission Deadline: October 20

Article Working Title: From vulnerable assets to operational consequences: Shift in how industrial organizations define cyber risk

Editorial Brief: Industrial cybersecurity has solved the inventory problem. Organizations know which assets they own, which ones are connected, which patches are missing, which systems are exposed to known threats. The tools work. The findings pile up. The gap that remains is not technical. It is operational.

A critical vulnerability in a nonsense asset is not a critical risk. A path into the control system does not automatically translate into a path into the physical process. A segmented network may depend on systems outside the segment. An incident response decision that looks correct from a security perspective can create new operational or safety consequences that nobody considered. The hard work is not identifying what could be compromised. It is understanding what that compromise would actually cause, which safeguards remain available after compromise, and who has authority to decide what happens next.

The ICD Focus event pairs new research from Takepoint on how organizations are approaching cyber-physical risk with straight talk from practitioners about how they are actually making these decisions. The research provides data on how organizations are assessing risk, prioritizing investment, quantifying consequence, and preparing for the moment when preventive controls fail. The practitioners provide the part that surveys cannot capture: the politics, the uncertainty, the dependencies that nobody mapped, the conversations that happen when cyber reaches operations.

This coverage should examine the maturity shift in industrial cybersecurity from asset and vulnerability inventory to consequence-based risk thinking. It should look at where traditional severity measures fail, how organizations are learning to distinguish between technical exposure and material operational risk, what evidence separates justified investment from wasted effort, and what happens when cybersecurity teams discover they cannot answer the question that actually matters: "If we get compromised here, what would actually happen?"

The article should also examine the decision-making problem at the operational level. When a cyber incident reaches industrial operations, the choices rarely look like best practice. Isolation removes visibility. Continued operation increases exposure. Shutdown introduces its own consequences. The practitioners at the event will discuss who makes these calls, what evidence they rely on, and what it takes to restart with confidence when the trustworthiness of process information is in question.

About you

First Name

Last Name

Company/Organization

Job Title/Designation (to be used in feature)

Business Email

Short Bio

Upload headshot (JPG/PNG up to 5MB; Square 500×500px, 300 DPI recommended)

Question Set

When organizations complete vulnerability assessments or penetration tests, how do they determine which findings represent a material operational risk rather than simply a technical exposure?

How are industrial organizations connecting asset criticality and vulnerability severity to potential operational consequences? Where do existing risk assessment models fall short?

When a cyber incident affects industrial operations, who has the authority to decide whether to isolate affected systems, continue operating in a degraded state, or shut down? How are these responsibilities established in advance?

Following a compromise, how can operators establish whether process data and control system information remain trustworthy, particularly while an incident is still unfolding?

With cyber threats evolving faster than budgets can accommodate, how are organizations deciding which cyber-physical risks to accept or defer, and what evidence supports those decisions?

Thank you for your response!