AWS Security ChangesHomeSearch

AWS prescriptive-guidance documentation change

Service: prescriptive-guidance · 2025-04-11 · Documentation low

File: prescriptive-guidance/latest/resilience-analysis-framework/mitigation-strategies.md

Summary

Updated quotation marks in human error discussion

Security assessment

Formatting change to quotes in existing content about human error prevention, no new security information added

Diff

diff --git a/prescriptive-guidance/latest/resilience-analysis-framework/mitigation-strategies.md b/prescriptive-guidance/latest/resilience-analysis-framework/mitigation-strategies.md
index 002d66072..e38b5bba7 100644
--- a//prescriptive-guidance/latest/resilience-analysis-framework/mitigation-strategies.md
+++ b//prescriptive-guidance/latest/resilience-analysis-framework/mitigation-strategies.md
@@ -49 +49 @@ In addition to mitigation techniques that apply to each failure mode category, y
-Finally, you should always assume that humans are going to make mistakes as you develop your mitigation strategy. Although modern DevOps practices seek to automate operations, humans still have to interact with your workloads for various reasons. Incorrect human action could introduce a failure in any of the SEEMS categories, such as removing too many nodes during maintenance and causing an overload, or incorrectly setting a feature flag. These scenarios are really a failure in preventative guardrails. A root cause analysis should never end with the conclusion that “a human made a mistake.” Instead, it should address the reasons why mistakes were possible in the first place. Therefore, your mitigation strategy should consider how human operators can interact with workload components and how to prevent or minimize the impact from human operator mistakes through safety guardrails.
+Finally, you should always assume that humans are going to make mistakes as you develop your mitigation strategy. Although modern DevOps practices seek to automate operations, humans still have to interact with your workloads for various reasons. Incorrect human action could introduce a failure in any of the SEEMS categories, such as removing too many nodes during maintenance and causing an overload, or incorrectly setting a feature flag. These scenarios are really a failure in preventative guardrails. A root cause analysis should never end with the conclusion that "a human made a mistake." Instead, it should address the reasons why mistakes were possible in the first place. Therefore, your mitigation strategy should consider how human operators can interact with workload components and how to prevent or minimize the impact from human operator mistakes through safety guardrails.