Difference between revisions of "Impact Tolerance"
| Line 11: | Line 11: | ||
'''''Notes (3):''''' focus on setting the limit of the impact the organisation can tolerate from a single disruption. | '''''Notes (3):''''' focus on setting the limit of the impact the organisation can tolerate from a single disruption. | ||
| − | '''''Notes (4):''''' is different from the [[Recovery Time Objective (RTO)| recovery time objective]], and the maximum acceptable outage | + | '''''Notes (4):''''' is different from the [[Recovery Time Objective (RTO)| recovery time objective]], and the maximum acceptable outage as defined in [[Business Continuity Planning (BCP)| business continuity planning]] as these are time-based. Impact tolerance is focused on outcome-based objectives, which are about how much, when, and for how long. |
{{Template:BL-OR-5 banner}} | {{Template:BL-OR-5 banner}} | ||
Revision as of 10:56, 21 June 2022
| 1. Impact Tolerance determines the maximum tolerable level of disruption to an important business service.
Impact Tolerance: Notes (1): represents the point beyond which the harm caused by an operational disruption to the business service becomes intolerable. Notes (2): do not factor in the frequency at which operational disruptions are likely to occur. Notes (3): focus on setting the limit of the impact the organisation can tolerate from a single disruption. Notes (4): is different from the recovery time objective, and the maximum acceptable outage as defined in business continuity planning as these are time-based. Impact tolerance is focused on outcome-based objectives, which are about how much, when, and for how long.
| ||||||||||||||||||||||||||||||||||||
