AWS prescriptive-guidance documentation change
Summary
Updated image paths and modified section headers to emphasize security findings
Security assessment
Enhanced documentation about security findings remediation process without addressing specific vulnerabilities
Diff
diff --git a/prescriptive-guidance/latest/vulnerability-management/define-ownership-of-security-findings.md b/prescriptive-guidance/latest/vulnerability-management/define-ownership-of-security-findings.md index d37bfc54c..a2321aad6 100644 --- a//prescriptive-guidance/latest/vulnerability-management/define-ownership-of-security-findings.md +++ b//prescriptive-guidance/latest/vulnerability-management/define-ownership-of-security-findings.md @@ -17 +17 @@ The following is an example of an ownership model that you can use as a starting - + @@ -23 +23 @@ For multi-account environments that separate applications into dedicated account - + @@ -36 +36 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Triage and remediate +Triage and remediate security findings in your AWS environment @@ -38 +38 @@ Triage and remediate -Assess and prioritize findings +Assess and prioritize security findings