Ensuring Compliance with Business Continuity Regulations

Most business continuity regulations ask for the same few things. A written plan grounded in a business impact analysis (BIA). A senior person accountable for it. Training, testing on a schedule, and updates when the business changes. Evidence that all of it happened.

The details differ by industry, and the details are what examiners check. Ensuring compliance with business continuity regulations starts with knowing which rules apply to you and what each one actually says.

Here is what the major business continuity regulations require by sector, the standards auditors measure you against, and the challenges that trip up regulated enterprises trying to keep a compliant program. This is a practitioner’s map, not legal advice. Confirm your obligations with counsel.

Old View New View
Compliance is the goal of the program Compliance is the floor the program stands on
Build a separate plan for each regulation Build one program and map each regulation to it
A clean audit means we’re ready A tested capability means we’re ready
“Because the regulator said so” wins support Protecting revenue and customers wins support

Business Continuity Regulations by Industry

Financial services in the US

Banks, broker-dealers, and insurers face the most detailed business continuity regulations in the US.

  • FFIEC Business Continuity Management booklet. The Federal Financial Institutions Examination Council (FFIEC) released it in November 2019, replacing the 2015 Business Continuity Planning booklet. The shift in the name is the point: examiners now look at how you manage continuity across the enterprise, not just whether you wrote plans. The booklet covers governance, BIA and risk assessment, strategies, plans, training, exercises and tests, maintenance, and reporting to management and the board.
  • Interagency operational resilience and third-party guidance. The Federal Reserve, OCC, and FDIC published Sound Practices to Strengthen Operational Resilience in October 2020 for the largest banks, and final interagency guidance on third-party risk management in June 2023. If a vendor runs a critical service, its continuity is your problem.
  • FINRA Rule 4370. FINRA Rule 4370 requires every member firm to keep a written business continuity plan for emergencies and significant business disruptions, covering minimum elements such as data backup and recovery, mission critical systems, and alternate communications with customers. A senior manager who is a registered principal must approve it and review it every year, and firms must disclose to customers how the plan addresses significant disruptions.
  • New York DFS cybersecurity regulation. The 2023 amendment to 23 NYCRR 500.16 requires covered entities to maintain both an incident response plan and a business continuity and disaster recovery plan, train the employees who carry them out, and test both plans, including restoring critical data from backups, at least once a year.

Our financial services practice works inside these requirements every day.

Financial services in the UK and EU

  • UK operational resilience. The Bank of England, PRA, and FCA required firms to identify important business services and set impact tolerances by March 31, 2022, and to be able to stay within those tolerances by March 31, 2025.
  • DORA. The EU’s Digital Operational Resilience Act (Regulation (EU) 2022/2554) has applied to financial entities since January 17, 2025. If you serve EU financial institutions, expect their DORA requirements to show up in your contracts.

Healthcare

  • CMS Emergency Preparedness Rule. Enforced since November 2017 for 17 provider and supplier types. It has four core elements: an emergency plan based on an all-hazards risk assessment, policies and procedures, a communication plan, and a training and testing program.
  • The Joint Commission. Its revised Emergency Management chapter took effect July 1, 2022 for hospitals and critical access hospitals, with dedicated standards for continuity of operations (including succession and delegation of authority), disaster recovery, and exercise evaluation.
  • HIPAA Security Rule. The contingency plan standard, 45 CFR 164.308(a)(7), requires a data backup plan, a disaster recovery plan, and an emergency mode operation plan. Testing and an applications and data criticality analysis are “addressable.” It applies to covered entities and business associates.
  • HITRUST. The HITRUST CSF’s business continuity controls expect continuity built into the security program, a risk assessment tied to continuity, documented and tested plans, and evidence of maintenance.

More on how we support hospitals, health systems, and health insurers on our healthcare industry page.

Public companies

The SEC doesn’t require a business continuity plan. It does put a clock on your crisis process. Under Form 8-K Item 1.05, a public company has four business days after it determines a cybersecurity incident is material to disclose it, and the materiality determination must be made without unreasonable delay after discovery. If your crisis team can’t get that determination in front of the right executives quickly, your continuity program has a regulatory gap even if every plan is current.

Government and federal contractors

  • Federal continuity policy. Continuity of operations (COOP) rests on Presidential Policy Directive 40 (2016) and FEMA’s August 2024 Federal Continuity Directives, which replaced FCD 1 and FCD 2. Executive branch agencies must be able to perform essential functions no later than 12 hours after activation and sustain them for at least 30 days, or until normal operations resume.
  • NIST SP 800-34 Rev. 1. The Contingency Planning Guide for Federal Information Systems (2010) sets out how federal agencies plan for information system recovery, and many contractors and state agencies use it as their reference.

See our government industry page for how we support public agencies.

Power and utilities

North American Electric Reliability Corporation (NERC) standard CIP-009 requires registered entities to have documented and implemented recovery plans for their bulk electric system (BES) Cyber Systems. More on our power and utilities page.

The Standards Auditors Measure You Against

Standards aren’t law. Regulators, auditors, customers, and insurers use them as the yardstick anyway.

  • ISO 22301:2019 sets the requirements for a business continuity management system. It is the standard you can certify against, and the one most examiners recognize.
  • ISO/TS 22317:2021 is the international guidance on business impact analysis.
  • ISO 22361:2022 provides guidelines for crisis management. Our post on implementing ISO 22361 covers how to put it to work.
  • ISO/IEC 27031:2025 covers ICT readiness for business continuity, the IT disaster recovery side.
  • The BCI Good Practice Guidelines are the practitioner’s body of knowledge. Our summary of the BCI Good Practice Guidelines 2023 walks through them.

Use the standard as a blueprint, not a manual. You don’t need to implement every clause to the letter. You do need to document the choices you made and why.

What Every Business Continuity Regulation Asks For

Line the rules up and the same requirements keep appearing. Build these once and you can map almost any regime to them:

  1. Governance and accountability. A policy, a named senior owner, and reporting to executives and the board. FINRA requires a senior principal to approve the plan. The FFIEC expects board reporting.
  2. A business impact analysis and risk assessment. The foundation for every recovery decision. Our guide to conducting a business impact analysis covers the process.
  3. Plans people can use. Business continuity, IT disaster recovery, crisis management, and crisis communications, connected to each other.
  4. Third-party continuity. Your critical vendors’ recovery capability, backed by contract terms and evidence.
  5. Training. CMS, the Joint Commission, and New York DFS all call it out. Train people before you test them.
  6. Testing on a schedule. Annual at minimum under FINRA’s review requirement and New York DFS’s testing requirement, with documented results and fixes.
  7. Maintenance and evidence. Updates when the business changes, and a record that shows the program ran all year, not just the week before the exam.

Challenges in Maintaining a Compliant Business Continuity Program

Regulated enterprises rarely fail an exam because they didn’t know a rule existed. They struggle with the work of keeping a program compliant year after year:

  • Overlapping regimes. A financial services firm with a broker-dealer subsidiary and EU customers can answer to HIPAA, HITRUST, FINRA, and DORA at once. Separate plans for each multiply the work and drift apart. Map every requirement to one program instead.
  • Plans written for auditors. Long plans pass reviews and fail in the first hour of a real disruption. Write for the person using the plan at 2 AM, then show the auditor how it meets the requirement.
  • BIA drift. The business reorganizes, buys a company, or moves a process to a vendor, and the BIA doesn’t follow. Every downstream plan inherits the error.
  • Evidence decay. Exercises happen, but the AAR items never close, and nobody can show what changed.
  • Exercises that test nothing. The same tabletop every year finds the same problems every year. Examiners notice. So do attackers.
  • Compliance as the only argument. If the regulator is the only reason the business participates, participation stops the day after the exam.

Compliance Is the Floor, Not the Program

A clean audit and a resilient organization are not the same thing. As I said on Managing Uncertainty, Episode 326: “Compliance proves what you did in the past. Resilience is what you execute under pressure in the moment and into the future.”

I see the same pattern in program after program. When a business continuity leader leans on compliance to get the business to participate, it usually means the program isn’t aligned to what the business needs. Fix the alignment and the compliance follows. The business will build plans that protect its revenue, its customers, and its commitments, and those plans will satisfy the examiner too.

Our four-step process starts the same way for every regulated client: Diagnose. Design. Deliver. Evolve. Our Resiliency Diagnosis® assesses your program against ISO 22301, ISO 22361, FFIEC, NIST SP 800-53, and ISO/IEC 27031, so you know where you stand before the examiner tells you.

Pass the audit. Then build the program that works when the audit is the last thing on anyone’s mind.

Keep Going

A few ways to go deeper if this was useful.

Bryan Strawser Avatar

About the author

Let’s build your Resilience Roadmap

Our team has spent two decades helping the world’s leading organizations prepare for and navigate disruption. We’ll bring that experience to yours.