Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Cloud and platforms

Cyber resilience: continuity, business recovery and third-party control

A recovery plan that has never been run is a hypothesis. Our consultants start from your critical activities and help your teams measure what they actually know how to restore, then reduce the gap, including at your providers.

Our principles

  • Recovery objectives set by the business
  • Plans proven by tests, not by documents
  • Dependencies on third parties known and controlled
In brief

Cyber resilience is an organisation's ability to continue its essential activities during a digital incident, then to restore normal operation within a controlled time frame. Management Square helps its clients build and test their continuity and recovery plans, control their dependencies on third parties and implement the requirements of DORA and NIS2.

Scope

How we contribute

  1. Business impact analysis

    With the business, identification of essential activities, the interruption times and data losses they can tolerate, and the resources on which they depend.

  2. Dependency mapping

    For each critical activity: applications, data, infrastructure, providers and those providers' subcontractors. The chain is traced back to single points of failure.

  3. Continuity and recovery plans

    Design or revision of the plans, standby architectures and backup strategy, consistent with the objectives set by the business.

  4. Tests and exercises

    Restoration tests, failovers to the standby environment and crisis exercises involving senior management, with a report on gaps and an action plan.

  5. Third-party risk management

    Inventory of providers, concentration analysis, technical requirements to be included in contracts and exit strategies for critical functions.

  6. Alignment with DORA and NIS2

    Gap analysis between your arrangements and the operational requirements of the texts, then a roadmap. The legal assessment of your situation remains the responsibility of your lawyers.

Page contents

Cyber resilience starts from an assumption: the incident will happen

Cybersecurity seeks to prevent the incident. Cyber resilience prepares the organisation to survive it. The two complement each other, but they involve neither the same people nor the same evidence. The first is judged by what does not happen. The second is judged by what you know how to do on the day everything stops.

Yet many continuity arrangements disappoint when they are needed. The plans exist, often voluminous, sometimes old. They describe an infrastructure that has changed, mention people who left long ago and assume backups that nobody has restored in full. The weakness is not in the drafting. It is in the absence of testing.

The move to the cloud adds a misunderstanding. Many teams take it for granted that the high availability promised by the provider amounts to a recovery plan. It covers the failure of a piece of equipment or a site. It covers neither a handling error, nor the encryption of data by an attacker, nor the failure of the provider itself.

Continuity, recovery, crisis: three plans that do not replace one another

The business continuity plan answers a business question: how do you continue to serve customers if the usual tool is unavailable? It provides for degraded modes, manual procedures and priorities.

The disaster recovery plan answers a technical question: in what order and by what means is the information system brought back into service? It relies on two objectives set by the business: the maximum tolerable interruption time and the maximum tolerable data loss.

The crisis management arrangements answer a decision question: who decides, with what information, and who speaks to customers, authorities and employees?

These three plans rest on prior work, the business impact analysis, which ranks activities according to what their interruption costs. The ISO 22301 standard, devoted to business continuity management systems, provides a reference framework for the whole.

In a ransomware attack scenario, two points become decisive. Backups must be out of reach of production administration accounts, otherwise they are encrypted along with everything else. And recovery requires a clean environment: the directory and administration tools are rebuilt first, before the applications.

DORA and NIS2: what the texts require

Two European texts have made digital resilience an obligation for many organisations. They differ in both nature and scope.

DORA NIS2
Reference Regulation (EU) 2022/2554 Directive (EU) 2022/2555
Nature Regulation, directly applicable Directive, to be transposed by each Member State
Scope Financial entities listed in Article 2, and oversight framework for critical third-party ICT service providers Essential and important entities in the sectors listed in Annexes I and II
Application Applicable since 17 January 2025 According to national law
Main areas ICT risk management, management, classification and reporting of incidents, digital operational resilience testing, risks related to third-party ICT service providers, information sharing Governance (Article 20), risk management measures (Article 21), reporting obligations in the event of a significant incident (Article 23)

Three common features directly concern operational management.

  • The responsibility of senior management. Article 5 of DORA places responsibility for the ICT risk management framework on the management body. Article 20 of NIS2 provides that management bodies approve the cybersecurity risk management measures and oversee their implementation.
  • Continuity as an expected measure. Article 21 of NIS2 cites business continuity (for example backup management and disaster recovery), crisis management and supply chain security. Chapter II of DORA deals in particular with response and recovery, backup and restoration.
  • Proof through testing. Chapter IV of DORA is devoted to digital operational resilience testing.

The two texts fit together: Article 1(2) of DORA specifies that, for financial entities identified as essential or important entities under NIS2, the regulation is considered a sector-specific Union legal act within the meaning of Article 4 of that directive. Notification deadlines and thresholds are set by the texts and their implementing acts. We do not summarise them here. Our entries on the DORA regulation and the NIS2 directive present their structure.

Third parties, a dependency to be mapped

A critical activity rarely depends on your teams alone. It relies on a cloud provider, a software-as-a-service vendor, a managed service provider, and on each one’s own subcontractors. Chapter V of DORA organises the management of this risk. Its Article 28 provides in particular for a register of information on contractual arrangements and exit strategies for services supporting critical or important functions.

Beyond the obligation, three questions deserve a written answer for each critical provider. What happens if it stops tomorrow? How many of your critical activities rely on it, directly or indirectly? With what, and under what conditions, could you replace it? When these questions intersect with those of location and applicable law, they connect with our page on sovereign and hybrid cloud.

Our approach: start from activities, prove through exercises

Our consultants work within your teams; decisions remain yours.

Having the business set the objectives. The impact analysis is carried out with the departments concerned. A tolerable interruption time chosen by IT alone commits nobody.

Tracing the chain of dependencies. For each critical activity, we trace the applications, data, infrastructure and third parties, down to single points of failure.

Measuring actual capability. A restoration test, even a partial one, gives an observed duration. That is what we compare with the objective, not the duration announced by the plan.

Closing the gap in order of criticality. Depending on the case, the answer is a standby architecture, an isolated backup, an automated rebuild using infrastructure code, a contractual clause or a business procedure.

Exercising, then doing it again. A crisis exercise involves senior management. Each exercise produces a report, actions and a date for the next one.

Building resilience into the life cycle. Every new application is given a continuity class from its design. Everyday incidents are handled according to the practices of our SRE and observability offering, whose post-incident reviews feed into the plans.

The most common blind spots

  • The plan never run. A document approved in committee says nothing about the actual duration of a restoration.
  • Replication mistaken for backup. Corrupted or encrypted data is replicated as faithfully as sound data.
  • Crisis tools that depend on the disaster. If email and the directory are affected, the crisis unit must have independent means of communication and documents accessible offline.
  • Software-as-a-service applications outside the scope. Their availability and the recovery of your data must appear in the plans in the same way as your own applications.
  • Compliance treated as paperwork. Producing the required documents without changing actual capabilities leaves the risk intact.

What allows you to say an organisation is ready

Together with you, we choose observable indicators, with no promised value:

  • the share of critical activities whose recovery objectives are validated by a business owner;
  • the share of critical applications that have undergone a successful restoration test over the period;
  • the gap between the target recovery time and the time measured during tests;
  • the share of critical providers covered by an exit strategy and reviewed clauses;
  • how long ago the last crisis exercise involving senior management took place;
  • the share of actions arising from exercises closed by their due date.

The third indicator is the most useful to present to senior management: it replaces an assurance in principle with an observation.

Typical work

What our consultants contribute to

Impact analysis and recovery objectives

Critical activities, their tolerable interruption times and data losses, validated by the business departments.

Dependency map and third-party register

The resources and providers supporting each critical activity, with the concentrations identified.

Continuity and recovery plans

Procedures, roles, standby resources and triggering conditions, kept up to date.

Exercise reports

Measured results, gaps against objectives and tracked corrective actions.

See also

Related services

Sovereign and hybrid cloud Not all your data requires the same level of protection, and no single provider meets all your needs. We help you classify your uses, choose the right environment for each and keep the option of changing it. SRE and observability Reliability cannot be decreed and is not measured by the number of green lights. We help you define it from your users' point of view, measure it and make it a criterion for trade-offs between new features and stability. IT architecture A useful architecture can be recognised by the decisions it makes simpler. Our consultants help your teams give the information system a target, a roadmap and integration rules that projects apply because they save them time. AI agents An agent does not just write, it acts in your applications. Our consultants help your teams design it starting from what it is allowed to do, what must remain validated by a human and what must be traced. AI governance Knowing which AI systems you use, what level of risk they fall under and who is accountable for them: this is the foundation of compliance, and the condition for quickly authorising what can be authorised. Data governance Data governance is not judged by the thickness of its charter, but by whether a question about a piece of data finds an owner and an answer. Our consultants help your teams establish it domain by domain, starting from real decisions. Software quality and testing Testing more is not enough: you need to test what matters, at the right level and at the right time. Our consultants help your teams build a risk-based test strategy and automated controls that make every production release more predictable.

Management Square in figures

300+
projects completed
43+
clients supported
Since2015
serving our clients
  • Allianz
  • Euler Hermes
  • Groupe BPCE
  • ODDO BHF
  • Candriam
  • Ledger
  • Saur
  • Veolia
  • Voltalia
  • emeis
  • Bonpoint
  • Legal Suite

FAQ

Frequently asked questions

Another question? Ask us

What is cyber resilience?

Cyber resilience is an organisation's ability to keep carrying out its essential activities during a digital incident, whether a cyberattack, an outage or the failure of a provider, then to return to normal. It complements cybersecurity, which seeks to prevent the incident, by preparing what happens when it occurs nonetheless.

What is the difference between a business continuity plan and a disaster recovery plan?

The business continuity plan describes how the organisation maintains its essential activities during a disruption, including through degraded modes of operation. The disaster recovery plan describes how the information system is brought back into service after a disaster. The first is owned by the business, the second by IT, and each needs the other.

What do RTO and RPO mean?

The recovery time objective (RTO, or DMIA in French) is the time by which an activity must have resumed. The recovery point objective (RPO, or PDMA in French) is the amount of data, expressed as a duration, that you accept losing. These two values are set by the business and determine the standby architecture and backup frequency.

Who does the DORA regulation apply to?

Regulation (EU) 2022/2554, known as DORA, applies to the financial entities listed in its Article 2 and establishes an oversight framework for critical third-party ICT service providers. It has applied since 17 January 2025. Determining whether a specific entity falls within its scope requires a legal analysis.

Does cloud hosting remove the need for a recovery plan?

No. The cloud provider ensures the availability of its infrastructure under the terms of its contract. Configuration, data, backups and the ability to restart your applications remain your responsibility. Spreading an application across several zones improves its availability, but protects neither against accidental deletion nor against malicious encryption of data.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.