Plausible Scenarios: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 12: | Line 12: | ||
'''''Note (3)''''': is a realistic event that could disrupt the delivery of [[Critical Business Services |critical business services]], leading to unacceptable impacts. | '''''Note (3)''''': is a realistic event that could disrupt the delivery of [[Critical Business Services |critical business services]], leading to unacceptable impacts. | ||
'''''Note (4 | '''''Note (4)''''': requires the board of directors to consider a broad range of [[Severe but Plausible Scenarios| severe but plausible scenarios]], including: | ||
* lockdown due to pandemic | * lockdown due to pandemic | ||
* cyber security incidents including credential and identity theft; data theft and manipulation; disruptive and destructive malware; emerging technologies: blockchain, cryptocurrency and artificial intelligence; and disinformation | * cyber security incidents including credential and identity theft; data theft and manipulation; disruptive and destructive malware; emerging technologies: blockchain, cryptocurrency and artificial intelligence; and disinformation |
Revision as of 12:50, 12 October 2024
1. Plausible Scenario is a realistic event that could disrupt the delivery of critical business services, leading to unacceptable impacts.
Note (1): is used within operational resilience to stress test the impact tolerances that have been developed for critical business services and to identify weaknesses, vulnerabilities, and associated mitigating actions. Note (2): includes risk resulting from disruption to cyber, technology, people, third-party dependency, pandemics and disasters. Note (3): is a realistic event that could disrupt the delivery of critical business services, leading to unacceptable impacts. Note (4): requires the board of directors to consider a broad range of severe but plausible scenarios, including:
|