AWS prescriptive-guidance documentation change
Summary
Expanded recommendation phrasing and clarified engagement with AWS Support. No substantive security content changes.
Security assessment
Changes improve clarity and completeness of incident response documentation but do not introduce new security controls or address vulnerabilities.
Diff
diff --git a/prescriptive-guidance/latest/security-controls-by-caf-capability/incident-response-recommendations.md b/prescriptive-guidance/latest/security-controls-by-caf-capability/incident-response-recommendations.md index da254ea72..c2646dc38 100644 --- a//prescriptive-guidance/latest/security-controls-by-caf-capability/incident-response-recommendations.md +++ b//prescriptive-guidance/latest/security-controls-by-caf-capability/incident-response-recommendations.md @@ -7 +7 @@ -Incident response planRunbooks and playbooksEvent-driven automationSupport processAlerts for security events +Define an incident response planCreate and maintain incident response runbooks and playbooksImplement event-driven security automationDocument how operational teams should engage with AWS SupportConfigure alerts for security events @@ -15 +15 @@ With the exception of security controls that notify you about events or automati -###### Recommendations in this section: +Recommendations in this section: @@ -23 +23 @@ With the exception of security controls that notify you about events or automati - * Document how operational teams should engage with Support + * Document how operational teams should engage with AWS Support @@ -83 +83 @@ For more information please see the below resources: -## Document how operational teams should engage with Support +## Document how operational teams should engage with AWS Support