AWS securityagent documentation change
Summary
Expanded remediation scope to include code review findings alongside penetration test findings
Security assessment
Documentation now includes code review findings in remediation workflows. While security-related, there's no indication this change addresses a specific disclosed vulnerability or security incident.
Diff
diff --git a/securityagent/latest/userguide/remediate-finding.md b/securityagent/latest/userguide/remediate-finding.md index 52d645b64..c9fd39a7a 100644 --- a//securityagent/latest/userguide/remediate-finding.md +++ b//securityagent/latest/userguide/remediate-finding.md @@ -13 +13 @@ When viewing the findings for a penetration test, you can request AWS Security A -You must enable finding remediation in the AWS Management Console. (See [Enable users to start remediation of penetration test findings](./enable-remediate-findings.html).) Users can start remediation for a specific finding from the AWS Security Agent Web App. +You must enable finding remediation in the AWS Management Console. (See [Enable users to start remediation of penetration test and code review findings](./enable-remediate-findings.html).) Users can start remediation for a specific finding from the AWS Security Agent Web App. @@ -74 +74 @@ Provide authentication credentials for penetration testing -Review code security findings in GitHub +Review code security findings in GitHub pull requests