AWS prescriptive-guidance documentation change
Summary
Added 'CSPM' to Security Hub control reference
Security assessment
Emphasizes CSPM context for security controls but shows no evidence of patching vulnerabilities. Improves clarity about security best practices implementation.
Diff
diff --git a/prescriptive-guidance/latest/vulnerability-management/application-team-example.md b/prescriptive-guidance/latest/vulnerability-management/application-team-example.md index 2c105ced1..b068c3f3a 100644 --- a//prescriptive-guidance/latest/vulnerability-management/application-team-example.md +++ b//prescriptive-guidance/latest/vulnerability-management/application-team-example.md @@ -7 +7 @@ -The following are some controls from the Security Hub [Foundational Security Best Practices (FSBP)](https://docs.aws.amazon.com/securityhub/latest/userguide/fsbp-standard.html) security standard that the application or development team might be responsible for: +The following are some controls from the Security Hub CSPM [Foundational Security Best Practices (FSBP)](https://docs.aws.amazon.com/securityhub/latest/userguide/fsbp-standard.html) security standard that the application or development team might be responsible for: @@ -30 +30 @@ Another important efficiency can be gained in this example. When an application -Each finding associated with a Security Hub control contains details about the finding and a link to the instructions for remediating the issue. Although cloud teams might encounter findings that require manual, one-time remediation, when appropriate, we recommend building proactive checks that identify issues as early as possible in the development process. +Each finding associated with a Security Hub CSPM control contains details about the finding and a link to the instructions for remediating the issue. Although cloud teams might encounter findings that require manual, one-time remediation, when appropriate, we recommend building proactive checks that identify issues as early as possible in the development process.