Impact due to FAIR-MAM at Group Level
  • 3 Minutes to read
  • PDF

Impact due to FAIR-MAM at Group Level

  • PDF

Article summary

Group Level FAIR MAM


In order to allow simpler management of FAIR MAM, the loss categories and drivers will now be available at the Group level and apply to all the risk scenarios of the Group. This will make it easier to manage any overrides of loss drivers at the group level instead of doing that for each risk scenario. Note that the ability to tune cost drivers at a Risk scenario will remain available.

With this change, 7 loss drivers have been split into scenario specific loss drivers and their benchmarks values updated to reflect current industry data. This allows end users to use leverage more specific benchmarks SAFE provides for risk scenario outcomes, as well as allowing end users to tune those benchmarks. This allows more accurate loss magnitudes to be calculated. As a result of these more specific benchmark values, this may result in overall Loss magnitude and ALE change for some risk scenarios that use these benchmark values.

The loss drivers have been removed and replaced with split drivers two modules as these drivers showed a high coherence with risk scenario parameters. They are under:

  1. Business Interruption

  2. Network Security

The following tables detail the categories that have been modified:

1. Business Interruption

Deleted

Added

Number of days (direct BI gross profit loss)

  • Number of days (direct BI gross profit loss) - [Ransomware]

  • Number of days (direct BI gross profit loss) - [Wiper]

Number of days (direct BI revenue delayed)

  • Number of days (direct BI revenue delayed) - [Ransomware]

  • Number of days (direct BI revenue delayed) - [Wiper]

Number of days (direct BI OpCost)

  • Number of days (direct BI OpCost) - [Ransomware]

  • Number of days (direct BI OpCost) - [Wiper]

Number of hours (direct BI PR revenue)

  • Number of hours (direct BI PR revenue) - [Ransomware and Wiper]

Number of days (revenue generated for 3P)

  • Number of days (revenue generated for 3P) - [Ransomware]

  • Number of days (revenue generated for 3P) - [Wiper]

Impact


The addition or deletion of these drivers should have no default impact. However, if any deleted drivers were tuned in the existing model, their tuned effect would be removed, and the replacement driver’s default effect would apply.

Exceptions being


  1. The default max value in old model for Number of days (direct BI gross profit loss) is 21 when the revenue is greater than 5B, whereas it 10 for Number of days (direct BI gross profit loss) - [Ransomware] in the new model

  2. The default max value in old model for Number of days (direct BI revenue delayed) is 21 when the revenue is greater than 5B, whereas it 10 for Number of days (direct BI revenue delayed) - [Ransomware] in the new model

  3. The default max value in old model for Number of days (direct BI OpCost) is 21 when the revenue is greater than 5B, whereas it 10 for Number of days (direct BI OpCost) - [Ransomware]

  4. The default max value in old model for Number of days (revenue generated for 3P) is 21 when the revenue is greater than 5B, whereas it 10 for Number of days (revenue generated for 3P) - [Ransomware] and Number of days (revenue generated for 3P) - [Wiper] in the new model

At a high level, the above driver’s max value gets impacted when the revenue is greater than 5 Billion.

2. Network Security


Deleted

Added

Number of hours (IR forensic)

  • Number of hours (IR forensic) - [Ransomware]

  • Number of hours (IR forensic) - [Wiper]

  • Number of hours (IR forensic) - [DDoS]

  • Number of hours (IR forensic) - [System Outage-Malicious]

  • Number of hours (IR forensic) - [System Outage-Accidental]

  • Number of hours (IR forensic) - [Data Exfilltration-Malicious]

  • Number of hours (IR forensic) - [Data Exfilltration-Accidental]

  • Number of hours (IR forensic) - [Cryptomining]

Number of hours (Network IR legal)

  • Number of hours (Network IR legal) - [Ransomware]

  • Number of hours (Network IR legal) - [Wiper]

  • Number of hours (Network IR legal) - [DDoS]

  • Number of hours (Network IR legal) - [System Outage-Malicious]

  • Number of hours (Network IR legal) - [System Outage-Accidental]

  • Number of hours (Network IR legal) - [Data Exilfiltration-Malicious]

  • Number of hours (Network IR legal) - [Data Exilfiltration-Accidental]

  • Number of hours (Network IR legal) - [Cryptomining]

Impact


The addition or deletion of these drivers should have no default impact. However, if any deleted drivers were tuned in the existing model, their tuned effect would be removed, and the replacement driver’s default effect would apply.

Exceptions being


  1. Defaults for old model - Number of hours (IR forensic) - [0,0,0] System Outage scenarios. New model - the defaults for DDoS and System Outage-Malicious has been updated to [15, 40, 85]

  2. Defaults for old model - Number of hours (Network IR legal) - [0,0,0] System Outage scenarios. New model - the defaults for DDoS and System Outage-Malicious has been updated to [15, 40, 85]

At a high level, System Outage - Malicious will have an increase in loss numbers, on enabling this feature.

Note - The newly added Loss drivers listed above should be reviewed for their new values, when they are applicable in a risk scenario.


Was this article helpful?