AWS prescriptive-guidance documentation change
Summary
Added asterisks (formatting emphasis) to definitions of Severity, Occurrence, Detection factors and risk categories in FMEA documentation
Security assessment
Changes are purely cosmetic formatting adjustments (adding asterisks) without modifying content. The documentation discusses general risk assessment methodology, not specific security vulnerabilities or security features. No security context was added or modified.
Diff
diff --git a/prescriptive-guidance/latest/failure-mode-effects-analysis/business-use-case.md b/prescriptive-guidance/latest/failure-mode-effects-analysis/business-use-case.md index d4efd8a2c..057a72caa 100644 --- a//prescriptive-guidance/latest/failure-mode-effects-analysis/business-use-case.md +++ b//prescriptive-guidance/latest/failure-mode-effects-analysis/business-use-case.md @@ -19 +19 @@ The core of this methodology is the risk priority number (RPN), a quantitative s - * **Severity (S)** : How much damage would this failure cause? A score of 1 means minimal business impact with no customer effect. A score of 10 means a critical outage or data loss that directly affects customers. + * **Severity (S)** :**** How much damage would this failure cause? A score of 1 means minimal business impact with no customer effect. A score of 10 means a critical outage or data loss that directly affects customers. @@ -21 +21 @@ The core of this methodology is the risk priority number (RPN), a quantitative s - * **Occurrence (O)** : How likely is this failure to happen? Low scores represent rare events (less than once per year), while high scores represent failures that occur daily or weekly. + * **Occurrence (O)** :**** How likely is this failure to happen? Low scores represent rare events (less than once per year), while high scores represent failures that occur daily or weekly. @@ -23 +23 @@ The core of this methodology is the risk priority number (RPN), a quantitative s - * **Detection (D)** : How hard is it to catch this failure before customers are affected? Automated alerts and dashboards score low (easy to detect), while failures that surface only through customer reports score high. + * **Detection (D)** :**** How hard is it to catch this failure before customers are affected? Automated alerts and dashboards score low (easy to detect), while failures that surface only through customer reports score high. @@ -34 +34 @@ Because each factor ranges from 1 to 10, the RPN ranges from 1 to 1,000. A high - * **Critical (800-1000)** : Immediate action required (current sprint) + * **Critical (800-1000)** :**** Immediate action required (current sprint) @@ -36 +36 @@ Because each factor ranges from 1 to 10, the RPN ranges from 1 to 1,000. A high - * **High (400-799)** : Priority action (1-2 sprints) + * **High (400-799)** :**** Priority action (1-2 sprints) @@ -38 +38 @@ Because each factor ranges from 1 to 10, the RPN ranges from 1 to 1,000. A high - * **Medium (200-399)** : Planned action (2-4 sprints) + * **Medium (200-399)** :**** Planned action (2-4 sprints) @@ -40 +40 @@ Because each factor ranges from 1 to 10, the RPN ranges from 1 to 1,000. A high - * **Low (100-199)** : Monitor and track (backlog) + * **Low (100-199)** :**** Monitor and track (backlog) @@ -42 +42 @@ Because each factor ranges from 1 to 10, the RPN ranges from 1 to 1,000. A high - * **Minimal (1-99)** : Accept risk with documentation + * **Minimal (1-99)** :**** Accept risk with documentation