AWS guardduty documentation change
Summary
Minor grammatical correction ('align to' changed to 'aligns with') and added ending period
Security assessment
Purely editorial change with no impact on security content or procedures. No security features or vulnerabilities referenced.
Diff
diff --git a/guardduty/latest/ug/guardduty-attack-sequence-finding-types.md b/guardduty/latest/ug/guardduty-attack-sequence-finding-types.md index f175eb127..6d6552cd7 100644 --- a//guardduty/latest/ug/guardduty-attack-sequence-finding-types.md +++ b//guardduty/latest/ug/guardduty-attack-sequence-finding-types.md @@ -9 +9 @@ AttackSequence:EKS/CompromisedClusterAttackSequence:ECS/CompromisedClusterAttack -GuardDuty detects an attack sequence when a specific sequence of multiple actions align to a potentially suspicious activity. An attack sequence includes **signals** such as API activities and GuardDuty findings. When GuardDuty observes a group of signals in a specific sequence that indicates an in-progress, ongoing, or a recent security threat, GuardDuty generates an attack sequence finding. GuardDuty considers individual API activities as [weak signals](./guardduty_concepts.html#guardduty-weak-signals-attack-sequence) because they don't present themselves as potential threat. +GuardDuty detects an attack sequence when a specific sequence of multiple actions aligns with a potentially suspicious activity. An attack sequence includes **signals** such as API activities and GuardDuty findings. When GuardDuty observes a group of signals in a specific sequence that indicates an in-progress, ongoing, or a recent security threat, GuardDuty generates an attack sequence finding. GuardDuty considers individual API activities as [weak signals](./guardduty_concepts.html#guardduty-weak-signals-attack-sequence) because they don't present themselves as potential threat.