Cybersecurity and operational resilience: connecting technology, people and processes

November 16, 2026, by Anna Lisa Di Vincenzo

20blog-cybersecurity-operational-resilience

A school evacuated after a threatening email. A flight diverted following a bomb alert. A refrigeration system compromised remotely.

Recent events in Italy and elsewhere in Europe have brought the everyday consequences of threats and disruption into focus. These incidents differ: a false warning and an intrusion into a digital system require distinct investigations, expertise and responses. Together, they raise a broader question: how prepared are organizations to keep essential activities running when disruption occurs?

For those designing and managing digital products, processes and systems, that question belongs in the work from the beginning.

Understanding the processes behind the technology

Every digital service supports activities, decisions and people: its importance depends partly on what relies on it.

An unavailable system can delay work across several teams, altered information can lead to a poor decision, a compromised control system can affect physical operations. Understanding cybersecurity risk therefore requires a clear view of these relationships.

  • Which activities are essential?
  • What systems support them?
  • What happens if those systems become unavailable or their information can no longer be trusted?

Connecting technical weaknesses to operational consequences helps organizations decide where to act first. It also brings cybersecurity into conversations about service quality, business continuity and organizational responsibility.

Preparing people to make decisions

During an incident, people may have limited time and incomplete information: unclear responsibilities and fragmented communication make their decisions harder.

Preparation means agreeing in advance who assesses the situation, who can authorize action and how essential activities can continue. It also means checking that procedures are practical for the people expected to use them. Communication is part of this preparation. People affected by disruption need to understand what is happening, what they should do and when they can expect an update.

Separating confirmed facts from assumptions helps people navigate uncertainty. Clear responsibilities for sharing and updating information help preserve trust while the situation develops.

How we approach cybersecurity at 20tab

At 20tab, we work on digital products, processes and systems by connecting technology decisions with operational needs.

Our starting point is the context: what the organization needs to keep doing, which dependencies matter and what the consequences of disruption could be. This understanding helps define the scope of the analysis and the priorities for improvement.

Different perspectives are essential: technology specialists understand system architectures and access paths, process owners understand operational constraints, people using a system every day can reveal dependencies and workarounds that documentation alone may miss.

Bringing these perspectives together creates a shared basis for assessing risk and deciding what to address.

Cyber HAZOP: applying this perspective to industrial operations

Cyber HAZOP is one example of this approach in an industrial setting. HAZOP, short for Hazard and Operability Study, is a structured method for examining how an industrial process might deviate from its intended operation. Our proposed Cyber HAZOP approach extends that analysis to include cybersecurity scenarios affecting digital controls, networks and remote access.

The underlying questions are practical: how could a digital compromise affect the process? What consequences could follow? Which safeguards are already in place, and where are the gaps?

The work moves from understanding the plant and reviewing available documentation to interdisciplinary workshops, risk and gap analysis, and a mitigation roadmap. Its scope depends on the specific plant, control architecture and operational requirements.

The aim is to give technical and operational teams a shared basis for prioritizing action.

Building security into digital change

New tools, integrations and ways of working can change an organization’s dependencies and exposure to risk. Security needs to evolve alongside them.

We believe good design considers how a service will behave when something goes wrong: how a problem will be detected, how its consequences can be contained and how people will be supported in making informed decisions.

That is how cybersecurity becomes part of the ongoing work of designing, building and evolving systems, and of protecting the activities people rely on.