Platform

What is Business Impact Analysis (BIA) in Acuna GRC?

Direct answer

Business impact analysis in Acuna GRC sits in the Operate workspace. Every process in BIA scope gets recovery objectives (RTO, RPO and MTPD) chosen from a shared Time Threshold list, impact scenarios that describe what happens as an outage lengthens, each with a severity and a time threshold, and the assets, staff, third parties and suppliers it depends on.

Each supplier gets a criticality for the process, suggested from its exposure and tier. The BIA Overview lists the processes in scope with their RTO and earliest impact, and the SPOF analysis lists assets that support several critical processes, so you can prioritise redundancy.

What is a business impact analysis for?

A business impact analysis (BIA) tells you which processes matter most when something stops, how fast each one must come back, and what it depends on. It is the starting point of business continuity: recovery strategies, backup design and continuity plans are sized from its results, not the other way round.

ISO 22301, the international standard for business continuity management systems, places the BIA alongside risk assessment in clause 8.2. Regulation asks for it too:

  • DORA (Regulation (EU) 2022/2554) requires financial entities, as part of their ICT risk management, to conduct a business impact analysis of their exposures to severe business disruptions (Article 11(5)). The analysis uses quantitative and qualitative criteria and considers the criticality of business functions, support processes, third-party dependencies and information assets. ICT assets and services must then be designed and used in line with the BIA, in particular to ensure redundancy of critical components.
  • NIS2 (Directive (EU) 2022/2555) lists business continuity, such as backup management and disaster recovery, and crisis management among the measures of Article 21(2)(c).

What does a BIA need to contain?

  • The processes in scope, with an owner and a criticality.
  • Impact scenarios: what happens to customers, revenue, legal obligations and reputation as an outage lasts one hour, one day, one week.
  • Recovery objectives for each process: MTPD, the point where impact becomes unacceptable, and the RTO and RPO set within it. See RTO, RPO and MTPD.
  • Dependencies: the systems, data, people, premises and suppliers each process needs to run.
  • Single points of failure: dependencies whose loss alone would stop a critical process.

The BIA is then reviewed when processes, systems or suppliers change, and its recovery assumptions are tested. Under DORA, ICT business continuity and response and recovery plans are tested at least once a year and after substantive changes to ICT systems supporting critical or important functions (Article 11(6)).

What are the most common BIA mistakes?

  • Assessing systems instead of business processes, so the analysis says what IT runs but not what the business loses.
  • Recovery objectives in free text, different for every team, that cannot be compared.
  • Leaving suppliers out. A process that depends on one outsourced provider inherits that provider’s recovery time.
  • Missing shared dependencies: one asset that quietly supports several critical processes.
  • A BIA done once for an audit and never updated when the organisation changes.

How does a BIA run in Acuna GRC?

In Acuna GRC, every process starts in BIA scope until someone turns it off; out-of-scope processes leave the list, the counts and the SPOF analysis, and keep their BIA. Each process in the process register carries its owner, criticality and CIAT classification, and its BIA records RTO, RPO and MTPD from the Time Threshold list, impact scenarios with a severity and a time threshold, and the assets, staff, third parties and critical assets it depends on.

Suppliers linked to a process get a criticality for that process, suggested from the supplier’s risk exposure and tier, and they are the same links you see on the supplier in TPRM. Issues linked to a process appear in its BIA. The SPOF analysis lists assets that support several critical processes above a threshold you set, to prioritise redundancy, cross-training and supplier diversification. It all sits in the Operate workspace, beside the risks and treatment plans that draw on the same assets and processes.

How Acuna GRC handles it

Sources

  1. Regulation (EU) 2022/2554 (DORA), Article 11(5) and (6)
  2. Directive (EU) 2022/2555 (NIS2), Article 21(2)(c)
  3. ISO 22301:2019, Business continuity management systems, clause 8.2

This page explains the rules in general terms and is not legal advice.

Frequently asked

What is the difference between a BIA and a risk assessment?

A BIA measures the consequences of a disruption over time, whatever its cause. A risk assessment looks at what could cause the disruption and how likely it is. You need both: the BIA says what to protect and how fast to recover, the risk assessment says what to protect it from.

Does DORA require a business impact analysis?

Yes. Article 11(5) of DORA requires financial entities to conduct a business impact analysis of their exposures to severe business disruptions, as part of their ICT risk management.

How often should a BIA be updated?

Review it at least yearly and whenever processes, systems or key suppliers change, since recovery objectives and dependencies move with them.

See how Acuna GRC runs this.

Tell us your frameworks and your team. We show you how Acuna GRC runs the program.

Hosted in Switzerland, the EU or the US