AWS guardduty documentation change
Summary
Updated tester script to include AttackSequence:EKS/CompromisedCluster generation alongside existing S3 finding type
Security assessment
This change enhances documentation for security testing tools but doesn't indicate a specific security issue being addressed. It expands testing capabilities for security features rather than responding to vulnerabilities.
Diff
diff --git a/guardduty/latest/ug/guardduty_findings-scripts.md b/guardduty/latest/ug/guardduty_findings-scripts.md index 2ebec83d1..425b7bcf5 100644 --- a//guardduty/latest/ug/guardduty_findings-scripts.md +++ b//guardduty/latest/ug/guardduty_findings-scripts.md @@ -40 +40 @@ Before you proceed, take the following considerations into account: -The tester script generates only [AttackSequence:S3/CompromisedData](./guardduty-attack-sequence-finding-types.html#attack-sequence-s3-compromised-data) for _Attack sequence finding types_. To visualize and understand [AttackSequence:IAM/CompromisedCredentials](./guardduty-attack-sequence-finding-types.html#attack-sequence-iam-compromised-credentials), you can generate [Sample findings](./sample_findings.html) in your account. +To visualize _Attack sequence finding types_ , the tester script generates only [AttackSequence:EKS/CompromisedCluster](./guardduty-attack-sequence-finding-types.html#attack-sequence-eks-compromised-cluster) and [AttackSequence:S3/CompromisedData](./guardduty-attack-sequence-finding-types.html#attack-sequence-s3-compromised-data). To visualize and understand [AttackSequence:IAM/CompromisedCredentials](./guardduty-attack-sequence-finding-types.html#attack-sequence-iam-compromised-credentials), you can generate [Sample findings](./sample_findings.html) in your account. @@ -66,0 +67,2 @@ Presently, the tester script generates following finding types that are related + * [AttackSequence:EKS/CompromisedCluster](./guardduty-attack-sequence-finding-types.html#attack-sequence-eks-compromised-cluster) +