AWS prescriptive-guidance documentation change
Summary
Updated references from 'Security Hub' to 'Security Hub CSPM' in title, content, and documentation links
Security assessment
The change only updates product naming conventions to include CSPM (Cloud Security Posture Management) without addressing vulnerabilities, weaknesses, or incidents. No security implications were introduced or resolved.
Diff
diff --git a/prescriptive-guidance/latest/vulnerability-management/security-team-example.md b/prescriptive-guidance/latest/vulnerability-management/security-team-example.md index 0f2395f19..d75b0146c 100644 --- a//prescriptive-guidance/latest/vulnerability-management/security-team-example.md +++ b//prescriptive-guidance/latest/vulnerability-management/security-team-example.md @@ -5 +5 @@ -# Security team example: Creating a Security Hub automation rule +# Security team example: Creating a Security Hub CSPM automation rule @@ -9 +9 @@ The security team receives findings related to threat detection, including Amazo -For this example, the security team is accepting the level of associated risk for security findings in an AWS account that is used strictly for learning purposes and does not include important or sensitive data. The name of this account is `sandbox`, and the account ID is `123456789012`. The security team can create an AWS Security Hub automation rule that suppresses all GuardDuty findings from this account. They can either create a rule from a template, which covers many common use cases, or they can create a custom rule. In Security Hub, we recommend previewing the results of the criteria to confirm that the rule returns the intended findings. +For this example, the security team is accepting the level of associated risk for security findings in an AWS account that is used strictly for learning purposes and does not include important or sensitive data. The name of this account is `sandbox`, and the account ID is `123456789012`. The security team can create an AWS Security Hub CSPM automation rule that suppresses all GuardDuty findings from this account. They can either create a rule from a template, which covers many common use cases, or they can create a custom rule. In Security Hub CSPM, we recommend previewing the results of the criteria to confirm that the rule returns the intended findings. @@ -40 +40 @@ The following are the parameters used to create this automation rule: -For more information, see [Automation rules](https://docs.aws.amazon.com/securityhub/latest/userguide/automation-rules.html) in the Security Hub documentation. Security teams have many options for investigating and remediating findings for detected threats. For extensive guidance, see the [AWS Security Incident Response Guide](https://docs.aws.amazon.com/whitepapers/latest/aws-security-incident-response-guide/aws-security-incident-response-guide.html). We recommend reviewing this guide to confirm that you have established strong incident response processes. +For more information, see [Automation rules](https://docs.aws.amazon.com/securityhub/latest/userguide/automation-rules.html) in the Security Hub CSPM documentation. Security teams have many options for investigating and remediating findings for detected threats. For extensive guidance, see the [AWS Security Incident Response Guide](https://docs.aws.amazon.com/whitepapers/latest/aws-security-incident-response-guide/aws-security-incident-response-guide.html). We recommend reviewing this guide to confirm that you have established strong incident response processes.