Privus Month Insights · No. 3 · September 2026

Business continuity: the obligation the GDPR implies and ISO 22301 formalises

Availability, resilience and recovery are more than technical controls. Integrated with business continuity, they become demonstrable operational capability.

GDPR · Business continuity · ISO 2230112-minute readPublished on 1 September 2026

The implicit obligation

The General Data Protection Regulation requires availability, resilience and the ability to restore access in a timely manner. It does not, however, expressly use the term “business continuity”.

Although this requirement is implicit, the terminology gap has a real cost: it leads many organisations to treat Article 32 as a collection of disconnected technical requirements, often reduced to backups and limited redundancy, instead of recognising what it entails: a systemic obligation embedded in the organisation's operating model.

The legal basis is sufficiently clear. Guidelines 9/2022 of the European Data Protection Board confirm that a temporary loss of availability of personal data can, in itself, constitute a personal data breach, even without any compromise of confidentiality or integrity. Data availability is therefore a compliance requirement in its own right.

The Board itself uses examples such as a power failure or a denial-of-service attack that makes personal data unavailable. These events may constitute a personal data breach, with the notification obligation under Article 33 depending on the subsequent assessment of the risk to individuals' rights and freedoms.

Another common misconception is that information security maturity fully resolves the continuity problem. It does not, at least not on its own.

ISO/IEC 27001:2022 already includes continuity-related controls in Annex A. However, these form part of a broader set of security measures whose applicability must be determined and justified through risk assessment and reflected in the Statement of Applicability (SoA). ISO 22301 reverses this logic: continuity ceases to be one control among many and becomes the very purpose of the management system, with specific requirements for impact analysis, strategy development, preparedness, response, testing, exercises and continual improvement.

An organisation may therefore demonstrate a high level of information security compliance while remaining operationally unable to restore critical services within the required timeframes when an incident occurs. The depth of requirements under the two instruments is not the same.

From theory to practice

The theory is clear. Practice, as the following examples show, tends to fall short.

Recent years provide clear examples of this gap, across different geographies and without any direct connection between them.

In February 2022, a Portuguese telecommunications operator suffered an outage that affected mobile services, SMS and customer support channels for several days, with cascading effects on emergency services, payments and other organisations that depended on that infrastructure without redundancy of their own.

In July 2026, an Angolan operator with more than 20 million customers suffered a nationwide network outage close to its stock market debut. The episode was another reminder that an operational failure in infrastructure with a highly concentrated market position can quickly extend beyond technology and become a matter of continuity, reputation and systemic dependency for customers, partners and dependent services.

In the United Kingdom, TSB Bank was fined £48.65 million in 2022 following serious governance and operational risk management failures associated with a systems migration that left millions of customers without adequate access to their accounts and banking services. The regulator itself described the success of the migration as critical to the bank's ability to maintain continuity of its critical functions. The same requirement appears in the GDPR through availability and resilience.

In Brazil, Lojas Renner, a victim of ransomware in 2021, managed to restore a substantial part of its commercial operations within a relatively short period, after around 48 hours of unavailability across its digital channels. The case demonstrates the practical importance of recovery capability when an incident starts to affect operations directly.

Exposure in numbers

The figures reinforce the scale of the problem.

In Portugal, CERT.PT recorded 2,758 cybersecurity incidents in 2024, an increase of approximately 36% over the previous year. Around 78% of recorded incidents occurred in private entities.

In Africa, the data for 2025 show particularly high exposure. INTERPOL's African Cyberthreat Assessment Report 2026 ranks Angola first for botnet detections in Africa that year, accounting for 37.95% of the detections considered in the report.

Globally, according to the Cost of a Data Breach Report 2025 by IBM and the Ponemon Institute, 65% of the organisations studied had not yet fully recovered from their data breach. Even among those reporting a full recovery, 76% took more than 100 days to achieve it. This is precisely the opposite of the timely restoration that the GDPR seeks to secure.

The real risk

The real risk is not simply experiencing an incident. It is discovering, during the incident, that the organisation has never defined how long it can afford to be offline.

From the GDPR to NIS2

This development also extends beyond the GDPR. For essential and important entities covered by NIS2, particularly in sectors such as telecommunications, energy and digital infrastructure, business continuity is already formalised as a distinct category of cybersecurity risk management measures. European regulation increasingly points towards documented plans, clear responsibilities, recovery capability, testing, exercises and coordination between continuity, backup, crisis management and incident response.

What largely appears in the GDPR through requirements for availability, resilience and recovery is becoming an explicit governance and audit requirement for a growing number of sectors. The direction of regulatory development is clear, even though its scope is not universal.

The fragmentation problem

What these cases and figures have in common is the fragmentation of compliance frameworks within organisations. The GDPR, ISO 27001 and ISO 22301 are frequently treated as parallel exercises: each has its own audit, owner and documentation, without a common system connecting them. This is also where most traditional consulting approaches fall short: they treat each framework as an isolated project, with its own team, deadlines and deliverables, instead of designing them as a single system from the outset.

This is precisely where exposure arises. An organisation can have a security policy, backups, an incident response plan and extensive documentary evidence, yet still be unable to answer three basic questions when a critical service stops working.

The benefit of integrating the three frameworks therefore goes beyond avoiding fines or reducing the reputational damage of a poorly managed incident: it is also operational and competitive. It means recovering faster, reducing financial impact, demonstrating maturity to customers, partners, insurers and investors, and turning what many organisations still treat solely as a compliance cost into a verifiable source of trust and, consequently, a competitive advantage.

Questions for every board

The questions for any board of directors are straightforward:

01
Has the organisation carried out a Business Impact Analysis (BIA)?
02
What is its Recovery Point Objective (RPO)?
03
What is its Recovery Time Objective (RTO)?
04
And beyond that: has your company mapped the intersections between the compliance frameworks that apply to it?

If these answers do not exist, have not been approved or have never been tested, the organisation may be compliant on paper while remaining operationally exposed.

“Evidence is the soul of compliance.”

Privus Kuzola audits the integration of the GDPR, ISO 27001 and ISO 22301, identifying where your organisation is compliant on paper but operationally exposed.

Explore Privus's ISO 22301 services.

Sources

General information only. This content does not constitute a legal opinion, audit, certification or recommendation applicable without an assessment of the specific circumstances.