IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« AWS RDS Snapshot Restored AWS Root Login Without MFA »

› › ›

AWS Redshift Cluster Creation

edit

AWS Redshift Cluster Creation

edit

Identifies the creation of an Amazon Redshift cluster. Unexpected creation of this cluster by a non-administrative user may indicate a permission or role issue with current users. If unexpected, the resource may not properly be configured and could introduce security vulnerabilities.

Rule type: query

Rule indices:

filebeat-*
logs-aws*

Severity: low

Risk score: 21

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://docs.aws.amazon.com/redshift/latest/APIReference/API_CreateCluster.html

Tags:

Elastic
Cloud
AWS
Continuous Monitoring
SecOps
Asset Visibility
Persistence

Version: 3 (version history)

Added (Elastic Stack release): 8.3.0

Last modified (Elastic Stack release): 8.4.0

Rule authors: Elastic

Rule license: Elastic License v2

Potential false positives

edit

Valid clusters may be created by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Cluster creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.

Investigation guide

edit

Rule query

edit

event.dataset:aws.cloudtrail and event.provider:redshift.amazonaws.com
and event.action:CreateCluster and event.outcome:success

Threat mapping

edit

Framework: MITRE ATT&CK^TM

Tactic:
- Name: Persistence
- ID: TA0003
- Reference URL: https://attack.mitre.org/tactics/TA0003/

Rule version history

edit

Version 3 (8.4.0 release)

Formatting only

« AWS RDS Snapshot Restored AWS Root Login Without MFA »