|
| 1 | +title: AWS GuardDuty Detector Deleted Or Updated |
| 2 | +id: d2656e78-c069-4571-8220-9e0ab5913f19 |
| 3 | +status: experimental |
| 4 | +description: | |
| 5 | + Detects successful deletion or disabling of an AWS GuardDuty detector, possibly by an attacker trying to avoid detection of its malicious activities. |
| 6 | + Upon deletion, GuardDuty stops monitoring the environment and all existing findings are lost. |
| 7 | + Verify with the user identity that this activity is legitimate. |
| 8 | +references: |
| 9 | + - https://docs.aws.amazon.com/guardduty/latest/APIReference/API_DeleteDetector.html |
| 10 | + - https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateDetector.html |
| 11 | + - https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_suspend-disable.html |
| 12 | + - https://docs.datadoghq.com/security/default_rules/719-39f-9cd/ |
| 13 | + - https://docs.prismacloud.io/en/enterprise-edition/policy-reference/aws-policies/aws-general-policies/ensure-aws-guardduty-detector-is-enabled |
| 14 | + - https://docs.stellarcyber.ai/5.2.x/Using/ML/Alert-Rule-Based-Potentially_Malicious_AWS_Activity.html |
| 15 | + - https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Amazon%20Web%20Services/Analytic%20Rules/AWS_GuardDutyDisabled.yaml |
| 16 | + - https://github.com/elastic/detection-rules/blob/main/rules/integrations/aws/defense_evasion_guardduty_detector_deletion.toml |
| 17 | + - https://help.fortinet.com/fsiem/Public_Resource_Access/7_4_0/rules/PH_RULE_AWS_GuardDuty_Detector_Deletion.htm |
| 18 | + - https://research.splunk.com/sources/5d8bd475-c8bc-4447-b27f-efa508728b90/ |
| 19 | + - https://suktech24.com/2025/07/17/aws-threat-detection-rule-guardduty-detector-disabled-or-suspended/ |
| 20 | + - https://www.atomicredteam.io/atomic-red-team/atomics/T156001#atomic-test-46---aws---guardduty-suspension-or-deletion |
| 21 | +author: suktech24 |
| 22 | +date: 2025-11-27 |
| 23 | +tags: |
| 24 | + - attack.defense-evasion |
| 25 | + - attack.t1562.001 |
| 26 | + - attack.t1562.008 |
| 27 | +logsource: |
| 28 | + product: aws |
| 29 | + service: cloudtrail |
| 30 | +detection: |
| 31 | + selection_event_source: |
| 32 | + eventSource: 'guardduty.amazonaws.com' |
| 33 | + selection_action_delete: |
| 34 | + eventName: 'DeleteDetector' |
| 35 | + selection_action_update: |
| 36 | + eventName: 'UpdateDetector' |
| 37 | + requestParameters.enable: 'false' |
| 38 | + selection_status_success: |
| 39 | + errorCode: 'Success' |
| 40 | + selection_status_null: |
| 41 | + errorCode: null |
| 42 | + condition: selection_event_source and 1 of selection_action_* and 1 of selection_status_* |
| 43 | +falsepositives: |
| 44 | + - Legitimate detector deletion by an admin (e.g., during account decommissioning). |
| 45 | + - Temporary disablement for troubleshooting (verify via change management tickets). |
| 46 | + - Automated deployment tools (e.g. Terraform) managing GuardDuty state. |
| 47 | +level: high |
0 commit comments