Definition of IT BCP and DRP
The expression IT BCP and DRP brings together two plans that an organisation prepares for the day its information system is hit. The business continuity plan (BCP) gathers the arrangements that maintain essential activities during the disruption, in degraded mode if need be. The disaster recovery plan (DRP) gathers those that bring the system back into service after an incident that has interrupted it.
These definitions reflect common usage, and the split varies. Depending on the organisation, the DRP is a chapter of the BCP or a separate document, and the IT part of the BCP is sometimes called the IT continuity plan.
Two standards address the subject. According to their AFNOR records, consulted on 12 November 2026, both are in force: NF EN ISO 22301 (November 2019) is titled “Sécurité et résilience - Systèmes de management de la continuité d’activité - Exigences” (Security and resilience, business continuity management systems, requirements), and NF ISO/IEC 27031 (July 2025) “Cybersécurité - Préparation des technologies de l’information et de la communication pour la continuité d’activité” (Cybersecurity, information and communication technology readiness for business continuity).
What the two plans are for
They settle in advance what can no longer be decided calmly during an incident: the activities to maintain, the restart order, the person authorised to trigger the plan.
They also meet regulatory requirements, worded in other terms. Article 11 of the DORA Regulation, Regulation (EU) 2022/2554, requires financial entities, outside the simplified framework of its Article 16, to have an “ICT business continuity policy” and “ICT response and recovery plans”. Article 21 of the NIS2 Directive, Directive (EU) 2022/2555, lists among the expected measures “business continuity, such as backup management and disaster recovery, and crisis management”.
What each plan contains
| BCP | DRP | |
|---|---|---|
| Purpose | Carry on essential activities during the disruption | Bring the information system back into service |
| Content | Priority activities, substitute procedures, fallback resources, roles | Restart order, backup architecture, restore and failover procedures |
| Triggered | As soon as the business loses its usual tools | By decision, when the service cannot be restored on site within the accepted time |
| Proven by | An exercise run with the business | A timed restore or failover test |
Both plans start from the same piece of work, the business impact analysis, which ranks activities and sets their recovery objectives. These objectives are defined in our entry on RTO and RPO. The DRP also relies on restorable backups, of which the immutable backup is a protected form.
BCP, DRP, high availability, crisis management: not to be confused
High availability is an architectural property: one component fails, another takes over without any human decision. The DRP begins where it stops, when the site, the data or the whole system are lost.
The crisis management set-up addresses another question: who decides, and who informs. It activates both plans without containing them, as explained in our article on cyber crisis management.
Example: a wholesaler’s warehouse
Consider a wholesaler whose warehouse management software becomes unavailable one Monday morning. The BCP provides for pickers to work from the order lists printed the day before, priority customers first. Activity continues, at a slower pace.
The DRP, for its part, guides the IT team: rebuild the directory, restore the database, restart the application, then reopen the interfaces with the carriers. The last test showed that this sequence takes longer than the printed lists allow the business to hold out. The gap goes back to management, which either extends how long degraded mode can last or funds a faster recovery.
Building these plans with the business and the tests that put them to the proof are presented on our cyber resilience page.