The BIA does not ask about the cause
Basic terms, part 11: business impact analysis and risk analysis are often mixed up in one workshop. BSI Standard 200-4 separates them clearly: the BIA assesses impact without asking about causes, the BCM risk analysis looks for causes, but only for what the BIA has identified as time-critical. Why the order is not negotiable.
First workshop on business continuity. IT arrives with a list: ransomware, power failure, flooding in the basement, outage of the data centre provider. The question to the business department is: which of your processes do we need to protect against all of this? The business department asks back: how are we supposed to know, as long as nobody has said which processes may be down for how long?
Both are right, and both are in the wrong step. The workshop mixes two analyses that BSI Standard 200-4 deliberately separates and puts in a fixed order.
The BIA: impact, not causes
According to 200-4, the business impact analysis establishes whether a business process is time-critical and how long it may be down before intolerable damage occurs. Its guiding question is, in translation: if a business process fails, what damage potential is to be expected in each time horizon?
And then the sentence that resolves the workshop confusion. In German:
„Die BIA betrachtet nur die potenziellen Auswirkungen eines Geschäftsprozessausfalls, nicht dessen Ursachen.“
That is: the BIA only considers the potential impact of a business process failure, not its causes. Whether the building is on fire, the power is out or the business application is down does not matter to the BIA. It assumes total failure and only asks how the damage develops over time. Its result is the time-critical business processes, their maximum tolerable periods of disruption and the resources they need to restart.
The step in between: target/actual comparison
Before asking about causes, 200-4 has a step that is often skipped: the target/actual comparison establishes whether the required resources are already sufficiently protected. Can the service provider actually deliver the required recovery time? Is the restore of the business application within the time the process can tolerate? The gaps from this comparison go to management together with the overview of time-critical processes and resources.
The BCM risk analysis: causes, but only for what is time-critical
Only then comes the risk analysis, and 200-4 explicitly describes it as the counterpart. While the BIA examines the possible impact of business interruptions, the BCM risk analysis looks at the possible causes of the failure of business operations.
What matters is what it looks at. All time-critical business processes and resources identified beforehand in the BIA must be considered systematically as target objects. Without a BIA, the risk analysis has no subject. The ransomware list from the workshop is not wrong, it just comes too early: only once it is clear that billing becomes intolerable after four hours and needs a particular server and a particular service provider does it make sense to ask which threats endanger exactly these resources.
Methodologically, the BCM risk analysis in 200-4 follows BSI Standard 200-3. But it is not the same as the risk analysis in the ISMS: there, it is about confidentiality, integrity and availability of information, here about the interruption of business operations. Existing results may be used if the time-critical resources are fully covered.
How often, and at which level
200-4 recommends carrying out the risk analysis as soon as possible after the BIA and the target/actual comparison and repeating it just as often, for example annually. If a year lies between them, the risk analysis examines resources that may no longer be time-critical and misses new ones.
And not every level needs it: according to 200-4, the BCM risk analysis belongs to the build-up and standard BCMS. In the reactive BCMS, the need for action after the target/actual comparison is derived directly through business continuity planning.
The test question
In your last risk analysis, were the threats assessed for the resources your BIA identifies as time-critical, or for the list that existed beforehand?
In isidaten, the BCM view of the risk analysis only shows the risks of processes marked as BCM-relevant.
Sources
BSI Standard 200-4, Business Continuity Management (German), version 1.0 (2023), chapter 7 (business impact analysis), chapter 8 (target/actual comparison) and chapter 9 (BCM risk analysis).
Next Sunday in Basic terms: processing on behalf, joint controllership and transfer. The previous part: The recovery time is not the downtime.
Questions about this update?
Talk to us – we are happy to show you this feature in a demo.


