Elastic Security Detection Rules

AWS RDS Instance/Cluster Stoppage

Last updated 7 months ago on 2025-01-15
Created 5 years ago on 2020-05-20

About

Identifies that an Amazon Relational Database Service (RDS) cluster or instance has been stopped.
Tags
Domain: CloudData Source: AWSData Source: Amazon Web ServicesData Source: AWS RDSUse Case: Asset VisibilityTactic: ImpactLanguage: kuery
Severity
medium
Risk Score
47
MITRE ATT&CK™

Impact (TA0040)(opens in a new tab or window)

↳ Service Stop (T1489)(opens in a new tab or window)

False Positive Examples
Valid 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 known behavior is causing false positives, it can be exempted from the rule.
License
Elastic License v2(opens in a new tab or window)

Definition

Rule Type
Query (Kibana Query Language)
Integration Pack
Prebuilt Security Detection Rules
Index Patterns
filebeat-*logs-aws.cloudtrail-*
Related Integrations

aws(opens in a new tab or window)

Query
event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and event.action:(StopDBCluster or StopDBInstance) and event.outcome:success

Install detection rules in Elastic Security

Detect AWS RDS Instance/Cluster Stoppage in the Elastic Security detection engine by installing this rule into your Elastic Stack.

To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(opens in a new tab or window).