With the business impact analysis (BIA), you define how long a business process can be down before it becomes unacceptable for your organization. The ISMS module uses it to calculate the MTPD (maximum tolerable period of disruption) and automatically passes the availability requirement on to every asset the process depends on. This shows you which systems really need to be back up quickly.
Prerequisites
- The business process exists in the ISMS module.
- You are allowed to manage the process: you are its Owner or you have the Key User or Admin role.
What you assess in the BIA
The BIA is a matrix of scenarios and time periods. For each combination, you choose a level on the impact scale. The guiding question is: "How painful is it if this process fails, and from when on?"
Three scenarios are set up by default. Each looks at an outage from a different angle:
Task fulfilment and service capability
The operational view
How severely does an outage affect key tasks, services, deadlines or operational control?
Protection duties and compliance
The legal view
What are the consequences for legal, contractual or regulatory obligations, data protection or the safety of people?
Economic and external impact
The financial view
What financial damage, follow-up costs, contractual penalties or loss of trust and reputation result?
The default time periods are 8 hours, 24 hours, 72 hours and 14 days. You assess using the impact scale, which has five levels by default:
| Level | Meaning |
|---|---|
| 1 Negligible | No significant damage |
| 2 Low | Minor damage, manageable in normal operations |
| 3 Medium | Noticeable damage, manageable with management effort |
| 4 Severe | Serious damage with significant consequences |
| 5 Catastrophic | Catastrophic damage, survival of the organization at risk |
Perform the BIA for a process
- Open Business processes and select the process.
- In the sidebar, click the pencil icon next to Business impact (BIA). The Business impact analysis dialog opens.
- Choose a level for each scenario and time period. If you cannot assess a cell yet, leave it at Not assessed.
- Use Rationale (optional) to record why you rated it this way. This makes your assessment traceable in an audit.
- Click Finalize assessment.
While you assess, the dialog header already shows the resulting MTPD and the Max impact.
When does a BIA count as done?
As soon as at least one cell is assessed. You can spot processes without a BIA by the BIA pending badge in the list, and they appear under Action required on the dashboard. If you set all cells back to Not assessed, the BIA is reset.
Understand the MTPD
The MTPD is the period from which an outage is no longer acceptable. The ISMS module determines it using the intolerance level: the MTPD is the first time period in which any scenario reaches this level. By default, the intolerance level is Severe.
| Example "Create quotation" | 8 h | 24 h | 72 h | 14 days |
|---|---|---|---|---|
| Economic and external impact | Low | Severe | Severe | Catastrophic |
| Result | The intolerance level is reached at 24 hours: MTPD 24 h. | |||
If no scenario reaches the intolerance level, the ISMS module shows the MTPD as "greater than or equal to" the longest period, for example MTPD ≥ 14 days.
The sidebar of the process shows the BIA as a compact chart. Scenarios are abbreviated there, and a red dashed line marks the MTPD.
What the BIA means for your assets
The BIA produces the process's availability curve: the highest impact per time period across all scenarios. The ISMS module passes this curve on via the dependencies to the assets the process uses. So you don't have to estimate the availability of each system separately, it follows from the business.
| BIA on the process Impact per scenario and period | → | Availability curve Highest impact per period | → | Availability on the asset Inherited via dependencies |
Tips for a robust BIA
- Have the BIA done by the person who really knows the process, for example the head of sales for "Create quotation".
- Think in concrete consequences: missed deadlines, contractual penalties, reporting obligations. This helps you choose the level.
- Use the rationale. In an audit, it lets you show why a system has to be back up within 24 hours.
Related articles
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article