AWS prescriptive-guidance documentation change
Summary
Added asterisks (formatting emphasis) after colons in multiple sections including scoring scales, prioritization guidelines, and mitigation strategies.
Security assessment
Changes are purely cosmetic formatting adjustments (adding **** for emphasis) without modifying any technical content, risk scores, or security recommendations. No vulnerabilities, security controls, or incidents are referenced.
Diff
diff --git a/prescriptive-guidance/latest/failure-mode-effects-analysis/implementation-guidelines.md b/prescriptive-guidance/latest/failure-mode-effects-analysis/implementation-guidelines.md index 221603c5c..5324a1817 100644 --- a//prescriptive-guidance/latest/failure-mode-effects-analysis/implementation-guidelines.md +++ b//prescriptive-guidance/latest/failure-mode-effects-analysis/implementation-guidelines.md @@ -17 +17 @@ The scoring scales and templates in this guide are a starting point. They are no - 1. **Customize for your environment** : Adjust severity, occurrence, and detection scores based on your specific business context and technical environment. + 1. **Customize for your environment** :**** Adjust severity, occurrence, and detection scores based on your specific business context and technical environment. @@ -19 +19 @@ The scoring scales and templates in this guide are a starting point. They are no - 2. **Prioritize by RPN** : Focus first on failure modes with RPN greater than 200, then work down to lower-priority items. + 2. **Prioritize by RPN** :**** Focus first on failure modes with RPN greater than 200, then work down to lower-priority items. @@ -21 +21 @@ The scoring scales and templates in this guide are a starting point. They are no - 3. **Validate assumptions** : Test the likelihood (occurrence) and detection difficulty in your environment through controlled experiments or historical analysis. + 3. **Validate assumptions** :**** Test the likelihood (occurrence) and detection difficulty in your environment through controlled experiments or historical analysis. @@ -23 +23 @@ The scoring scales and templates in this guide are a starting point. They are no - 4. **Update regularly** : Review and update RPN scores based on implemented mitigations and real-world experience. + 4. **Update regularly** :**** Review and update RPN scores based on implemented mitigations and real-world experience. @@ -34 +34 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **1-2** : Minimal impact, no customer effect + * **1-2** :**** Minimal impact, no customer effect @@ -36 +36 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **3-4** : Minor impact, limited customer effect + * **3-4** :**** Minor impact, limited customer effect @@ -38 +38 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **5-6** : Moderate impact, noticeable customer effect + * **5-6** :**** Moderate impact, noticeable customer effect @@ -40 +40 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **7-8** : Major impact, significant customer effect + * **7-8** :**** Major impact, significant customer effect @@ -42 +42 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **9-10** : Critical impact, severe customer effect or business disruption + * **9-10** :**** Critical impact, severe customer effect or business disruption @@ -49 +49 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **1-2** : Very rare (less than once per year) + * **1-2** :**** Very rare (less than once per year) @@ -51 +51 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **3-4** : Rare (once per year) + * **3-4** :**** Rare (once per year) @@ -53 +53 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **5-6** : Occasional (monthly) + * **5-6** :**** Occasional (monthly) @@ -55 +55 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **7-8** : Frequent (weekly) + * **7-8** :**** Frequent (weekly) @@ -57 +57 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **9-10** : Very frequent (daily) + * **9-10** :**** Very frequent (daily) @@ -64 +64 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **1-2** : Very easy to detect (automated alerts, immediate visibility) + * **1-2** :**** Very easy to detect (automated alerts, immediate visibility) @@ -66 +66 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **3-4** : Easy to detect (monitoring dashboards, quick identification) + * **3-4** :**** Easy to detect (monitoring dashboards, quick identification) @@ -68 +68 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **5-6** : Moderate detection (requires investigation, some delay) + * **5-6** :**** Moderate detection (requires investigation, some delay) @@ -70 +70 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **7-8** : Difficult to detect (manual investigation required, significant delay) + * **7-8** :**** Difficult to detect (manual investigation required, significant delay) @@ -72 +72 @@ Use the following scales when scoring each dimension of a failure mode. Each fac - * **9-10** : Very difficult to detect (often discovered by customers, major delay) + * **9-10** :**** Very difficult to detect (often discovered by customers, major delay) @@ -81 +81 @@ After you've identified and scored a failure mode, the next step is choosing how - * **Prevention** : Eliminate or reduce the likelihood of failure occurrence + * **Prevention** :**** Eliminate or reduce the likelihood of failure occurrence @@ -83 +83 @@ After you've identified and scored a failure mode, the next step is choosing how - * **Detection** : Improve ability to detect failures quickly + * **Detection** :**** Improve ability to detect failures quickly @@ -85 +85 @@ After you've identified and scored a failure mode, the next step is choosing how - * **Scope of impact** : Reduce the impact when failures occur + * **Scope of impact** :**** Reduce the impact when failures occur @@ -87 +87 @@ After you've identified and scored a failure mode, the next step is choosing how - * **Recovery** : Improve speed and effectiveness of failure recovery + * **Recovery** :**** Improve speed and effectiveness of failure recovery