AWS securityhub documentation change
Summary
Clarified workflow status behavior and simplified CSPM reference wording
Security assessment
The changes refine existing documentation about workflow status functionality without introducing new security concepts. The clarification about suppression not preventing new findings is an operational detail rather than a security fix or vulnerability disclosure.
Diff
diff --git a/securityhub/latest/userguide/findings-workflow-status.md b/securityhub/latest/userguide/findings-workflow-status.md index 04bd368ce..74b01c1f4 100644 --- a//securityhub/latest/userguide/findings-workflow-status.md +++ b//securityhub/latest/userguide/findings-workflow-status.md @@ -9 +9 @@ Setting the workflow status of findings -Workflow status tracks the progress of your investigation into a finding. Workflow status is specific to an individual finding. In addition, it doesn't affect the generation of new findings. For example, if you change the workflow status of a finding to `SUPPRESSED` or `RESOLVED`, your change doesn't prevent AWS Security Hub Cloud Security Posture Management (CSPM) from generating a new finding for the same issue. +Workflow status tracks the progress of your investigation into a finding. Workflow status is specific to an individual finding and doesn't affect generation of new findings. For example, if you change the workflow status of a finding to `SUPPRESSED` or `RESOLVED`, your change doesn't prevent Security Hub CSPM from generating a new finding for the same issue.