AWS RDS Instance/Cluster Stoppage
editAWS RDS Instance/Cluster Stoppage
editIdentifies that an Amazon Relational Database Service (RDS) cluster or instance has been stopped.
Rule type: query
Rule indices:
- filebeat-*
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:
- https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/stop-db-cluster.html
- https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_StopDBCluster.html
- https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/stop-db-instance.html
- https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_StopDBInstance.html
Tags:
- AWS
- Elastic
- SecOps
- Asset Visibility
- Continuous Monitoring
Version: 1
Added (Elastic Stack release): 7.9.0
Rule authors: Elastic
Rule license: Elastic License
Potential false positives
editValid clusters or instances may be stopped by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Cluster or instance stoppages from unfamiliar users or hosts should be investigated. If a known behavior is causing false positives, it can be excluded from the rule.
Investigation guide
editThe AWS Filebeat module must be enabled to use this rule.
Rule query
editevent.action:(StopDBCluster or StopDBInstance) and event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and event.outcome:success
Threat mapping
editFramework: MITRE ATT&CKTM
-
Tactic:
- Name: Impact
- ID: TA0040
- Reference URL: https://attack.mitre.org/tactics/TA0040/
-
Technique:
- Name: Service Stop
- ID: T1489
- Reference URL: https://attack.mitre.org/techniques/T1489/