Digital resilience is the ability to anticipate failures, maintain priority services, contain their consequences, and restore operations through coordinated, documented, and learning-oriented management.
In everyday language, being well-liked means inspiring trust. In the digital world, the expression can take on a different—though not entirely dissimilar—meaning: that something can fail without everything falling apart.
For a long time, cybersecurity has been built around a seemingly simple goal: preventing incidents from occurring. Controls are implemented, vulnerabilities are patched, access is secured, backups are taken, and systems are monitored with the aim of preventing anything from failing.
And, of course, prevention remains essential. But no organization can guarantee that it will never suffer an outage, that none of its vendors will encounter a problem, that all its products will be free of vulnerabilities, or that its systems will withstand any attack, human error, technical failure, or external event.
The question, therefore, can no longer be solely about how to prevent a failure.
It is also necessary to ask what will happen when something goes wrong, how long it will take the organization to detect it, who will make the decisions, which services can be maintained, how the consequences will be limited, what information will be communicated, how operations will be restored, and what will be learned from the incident.
This is, to a large extent, the logic underlying some of the most significant European regulations in recent years, such as Directive (EU) 2022/2555 of the European Parliament and of the Council of December 14, 2022, on measures to ensure a high common level of cybersecurity throughout the Union, known as NIS2; Directive (EU) 2022/2557 of the European Parliament and of the Council of December 14, 2022, on the resilience of critical entities, known as CER; and Regulation (EU) 2024/2847 of the European Parliament and of the Council of October 23, 2024, on horizontal cybersecurity requirements for products with digital components, known as the Cyber Resilience Regulation or Cyber Resilience Act (CRA).
Although none of these regulations uses the expression “to be well-liked,” they all stem from a similar idea: a digitally mature organization is not one that promises it will never fail, but one that prepares to prevent reasonably avoidable failures and responds appropriately when others occur.
How does European regulation broaden the concept of cybersecurity and digital resilience?
The new European regulation has broadened the understanding of security.
It is no longer just about implementing technical measures, but about managing risks. It is not just about reacting to an incident, but about having previously defined responsibilities, decision-making processes, continuity mechanisms, and communication channels. Nor is it solely about fixing a problem, but about being able to demonstrate what was done before, during, and after it occurred.
NIS2 requires entities within its scope to adopt appropriate and proportionate technical, operational, and organizational measures to manage their cybersecurity risks. It also strengthens incident reporting obligations and assigns responsibility to management bodies for approving and overseeing risk management measures.
The CER broadens the perspective.
Its concern is not limited to digital systems but extends to the ability of certain entities to continue providing essential services in the face of natural, human, physical, technological, or hybrid risks. Therefore, it requires identifying critical entities, assessing risks, and adopting technical, organizational, and security measures to strengthen their resilience.
The CRA, for its part, applies this same logic to products with digital elements. Products with digital elements falling within the CRA’s scope of application must comply with the cybersecurity requirements set forth in the Regulation throughout the relevant phases and periods. Security thus ceases to be an afterthought and becomes an integral part of the product’s lifecycle.
The three regulations address different realities but share a common evolution. Cybersecurity and resilience are no longer issues reserved for technical teams but have also become matters of governance, organization, and compliance.
How does NIS2 strengthen incident management and corporate governance?
NIS2 is based on an obvious observation: our operations depend on networks, information systems, cloud services, technology providers, electronic communications, and interconnected platforms.
When one of these elements fails, the problem does not always remain confined to the IT department. It can paralyze processes, prevent the delivery of services, affect customers, lead to contractual breaches, trigger notification obligations, and require urgent decisions from management.
For this reason, NIS2 does not merely require security tools. The Directive incorporates measures related to risk analysis, incident management, business continuity, disaster recovery, crisis management, supply chain security, system development and maintenance, access control, training, and the evaluation of the effectiveness of the measures adopted.
The question is no longer simply whether the organization has a particular control in place, but whether there is a governance model capable of coordinating the response.
When an incident occurs, someone must determine its severity, activate the appropriate procedures, bring together the affected departments, assess legal obligations, decide whether notifications are required, and ensure that the information reaches those who need to make decisions.
An organization that knows how to manage its failures does not improvise when it comes to determining what information senior management needs, which services must be restored first, or how to coordinate with its vendors. These decisions have been prepared, rehearsed, and documented before a crisis strikes.
This is where one of the key contributions of NIS2 comes into play: placing cybersecurity within the framework of corporate governance. Management bodies do not need to become technical specialists, but they must understand the relevant risks, approve management measures, and oversee their implementation.
This requires translating technical information into language that enables decision-making. It is not enough to simply report that a critical vulnerability exists or that a system is unavailable. It is necessary to explain which functions depend on that system, what impact might result, what alternatives exist, what resources are needed, and which decisions cannot be delayed.
Being effective, therefore, means not losing organizational control, even if control over part of the technology has been temporarily lost.
How does the CER Directive protect the continuity of essential services?
The CER adds another essential dimension: the continuity of services that are indispensable to society and the economy.
An entity may have technically secure systems and yet not be truly resilient. It may depend on a single facility, a provider that is difficult to replace, a person with critical expertise, a vulnerable physical connection, or a logistics chain with no alternatives.
Resilience requires looking beyond the specific incident and understanding the dependencies that underpin service delivery.
For this reason, the CER adopts a risk-based approach that is not limited to digital threats. Critical entities must prepare for events of various kinds and adopt measures that are appropriate and proportionate to the identified risks.
From this perspective, “resilience” means that a disruption does not automatically lead to a collapse.
A facility may be temporarily rendered inoperable, but an alternative must exist. A provider may be unable to continue providing the service, but the organization must understand the degree of dependency and have mechanisms in place for substitution or recovery. A crisis may force a change in operations, but priority services and the minimum levels that must be maintained must be clearly defined.
Implementing the CER requires a coordinated approach to areas that, in many organizations, may be managed separately: business continuity, physical security, cybersecurity, crisis management, infrastructure protection, supplier relations, and communication with authorities.
This connection is particularly important because real-world incidents rarely respect a company’s internal divisions.
A cyberattack can cause a physical disruption. A malfunction can render digital systems inoperable. An energy problem can affect communications. A technology outage can prevent staff from accessing facilities, serving customers, or managing essential services.
Resilience begins when an organization stops analyzing these risks in isolation and starts to understand how they are interconnected.
What does the Cyber Resilience Act require of digital products?
The CRA approaches the problem from a different angle: the digital products we use.
A connected device, an app, a computer program, or a software component may contain vulnerabilities that are not always visible to the purchaser. Furthermore, many products rely on libraries, modules, services, and components developed by third parties, which multiplies the interconnections and dependencies within the supply chain.
The CRA aims to make cybersecurity an integral part of product development and maintenance, not just a reaction after a problem arises.
This involves assessing risks from the design phase, reducing vulnerabilities, providing secure configurations, managing third-party components, facilitating security updates, maintaining vulnerability management procedures, and providing sufficient information to users and authorities. The Regulation also allocates obligations among manufacturers, importers, and distributors, according to the role each plays in the value chain.
From the CRA’s perspective, being realistic does not mean accepting that products are insecure. It means acknowledging that, even when applying sound design and development practices, vulnerabilities may be discovered during a product’s lifecycle.
Maturity lies not only in having avoided the initial error, but also in the ability to detect it, analyze it, correct it, distribute the update securely, inform those who may be affected, and learn for future versions.
A product does not end when it is placed on the market. It continues to exist as long as it is used, maintained, updated, and connected to other systems.
That is why the CRA introduces a lifecycle approach. For operators and products falling within its scope, certain obligations extend beyond the point of market release and include aspects related to support and vulnerability management during the applicable periods.
Furthermore, its timeline already establishes specific obligations. The obligations to report actively exploited vulnerabilities and serious incidents apply as of September 11, 2026, while the Regulation’s main obligations will apply as of December 11, 2027.
This means that preparing for the CRA is not just about reviewing finished products. It requires reviewing development models, internal responsibilities, supplier relationships, update processes, support periods, and notification mechanisms.
In other words, to be able to respond effectively tomorrow, you need to start getting organized today.
What does implementing digital resilience mean in practice?
Being prepared means having thought about failure before it occurs.
It means knowing which services are truly critical, which systems and suppliers they depend on, and how long they can remain disrupted before the consequences become unacceptable.
It means that everyone knows their role and that key decisions do not depend solely on whoever is available at the time.
It means that management receives clear information, can monitor risks, and understands which decisions fall under their purview.
It means that the organization does not assume its providers will always function, but rather assesses its dependencies, incorporates contractual requirements, monitors services, and prepares alternatives.
It means that digital products are designed with security in mind, that their components are known, that vulnerabilities can be managed, and that updates will reach those who need them.
It means communicating transparently, without rushing, but also without hiding or delaying information that needs to be disclosed.
And it means retaining evidence. Because in the regulatory sphere, it is not enough to have acted correctly. It is also necessary to be able to explain which risks were identified, which decisions were made, who approved them, and why they were considered proportionate.
Why doesn’t digital trust depend on promising that there will never be any failures?
NIS2, the CER, and the CRA represent a profound shift in European digital regulation.
Organizations are no longer evaluated solely on the measures they implement to prevent incidents, but also on their ability to anticipate them, contain them, continue providing services, recover, fix vulnerabilities, and learn.
Resilience is not invulnerability. Nor is it resignation.
It is the ability to accept that zero risk does not exist and, even so, to build organizations, services, and products that do not turn every error into a crisis.
Therefore, the true goal cannot simply be to demonstrate that policies, controls, and procedures are in place. Rather, it is for the organization to be prepared to use them when they are truly needed.
In an environment where digital technologies underpin essential services, relationships, and activities, trust depends as much on access as it does on security, continuity, and responsiveness.
In the digital world, building trust isn’t about claiming that an outage will never happen. It’s about demonstrating that, when it does, we’ll know how to handle it well.
Frequently Asked Questions
What is digital resilience?
It is an organization’s ability to anticipate incidents, limit their consequences, maintain priority services, resume operations, and learn from what happened.
What is the difference between cybersecurity and digital resilience?
Cybersecurity seeks to protect networks, systems, and products from threats. Digital resilience also incorporates the readiness to respond, maintain operations, and recover when an incident or disruption does occur.
What does the NIS2 Directive provide?
NIS2 strengthens cybersecurity risk management, incident response and notification, supply chain security, business continuity, and the accountability of management bodies.
What does the CER Directive address?
The CER addresses the resilience of critical entities and their ability to continue providing essential services in the face of various types of risks.
Which products does the Cyber Resilience Act (CRA) target?
The CRA establishes horizontal cybersecurity requirements for products with digital components that fall within its scope.
Why is the supply chain important for resilience?
Because an organization or a product may depend on suppliers, components, libraries, services, facilities, or connections whose unavailability could affect business continuity.
What role do management bodies play in NIS2?
Management bodies must understand the relevant risks, approve management measures, and oversee their implementation.
When do the CRA’s obligations take effect?
The obligations to report actively exploited vulnerabilities and serious incidents take effect on September 11, 2026, while the main obligations of the Regulation will take effect on December 11, 2027.Digital Resilience: Key Aspects of NIS2, CER, and CRA







