AWS Config Service Tamperingedit
Identifies attempts to delete an AWS Config Service rule. An adversary may tamper with Config rules in order to reduce visibility into the security posture of an account and/or its workload instances.
Rule type: query
Rule indices:
- filebeat-*
- logs-aws*
Severity: medium
Risk score: 47
Runs every: 10 minutes
Searches indices from: now-60m (Date Math format, see also Additional look-back time)
Maximum alerts per execution: 100
References:
Tags:
- Elastic
- Cloud
- AWS
- Continuous Monitoring
- SecOps
- Monitoring
Version: 2 (version history)
Added (Elastic Stack release): 7.9.0
Last modified (Elastic Stack release): 7.10.0
Rule authors: Elastic
Rule license: Elastic License
Potential false positivesedit
Privileged IAM users with security responsibilities may make changes to the Config rules in order to align with local security policies and requirements. Automation, orchestration, and security tools may also make changes to the Config service, when they are used to automate setup or configuration of AWS accounts. Other types of user or service contexts do not commonly make changes to this service.
Investigation guideedit
The AWS Filebeat module must be enabled to use this rule.
Rule queryedit
event.dataset: aws.cloudtrail and event.action: DeleteConfigRule and event.provider: config.amazonaws.com
Threat mappingedit
Framework: MITRE ATT&CKTM
-
Tactic:
- Name: Defense Evasion
- ID: TA0005
- Reference URL: https://attack.mitre.org/tactics/TA0005/
-
Technique:
- Name: Disabling Security Tools
- ID: T1089
- Reference URL: https://attack.mitre.org/techniques/T1089/
Rule version historyedit
- Version 2 (7.10.0 release)
-
- Formatting only