AWS CloudTrail Log Suspended

Identifies suspending the recording of AWS API calls and log file delivery for the specified trail. An adversary may suspend trails in an attempt to evade defenses.

Elastic rule (View on GitHub)

  1[metadata]
  2creation_date = "2020/06/10"
  3integration = ["aws"]
  4maturity = "production"
  5min_stack_comments = "AWS integration breaking changes, bumping version to ^2.0.0"
  6min_stack_version = "8.9.0"
  7updated_date = "2024/04/14"
  8
  9[rule]
 10author = ["Elastic"]
 11description = """
 12Identifies suspending the recording of AWS API calls and log file delivery for the specified trail. An adversary may
 13suspend trails in an attempt to evade defenses.
 14"""
 15false_positives = [
 16    """
 17    Suspending the recording of a trail may be done by a system or network administrator. Verify whether the user
 18    identity, user agent, and/or hostname should be making changes in your environment. Trail suspensions from
 19    unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted
 20    from the rule.
 21    """,
 22]
 23from = "now-60m"
 24index = ["filebeat-*", "logs-aws.cloudtrail-*"]
 25interval = "10m"
 26language = "kuery"
 27license = "Elastic License v2"
 28name = "AWS CloudTrail Log Suspended"
 29note = """## Triage and analysis
 30
 31### Investigating AWS CloudTrail Log Suspended
 32
 33Amazon CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your Amazon Web Services account. With CloudTrail, you can log, continuously monitor, and retain account activity related to actions across your Amazon Web Services infrastructure. CloudTrail provides event history of your Amazon Web Services account activity, including actions taken through the Amazon Management Console, Amazon SDKs, command line tools, and other Amazon Web Services services. This event history simplifies security analysis, resource change tracking, and troubleshooting.
 34
 35This rule identifies the suspension of an AWS log trail using the API `StopLogging` action. Attackers can do this to cover their tracks and impact security monitoring that relies on this source.
 36
 37#### Possible investigation steps
 38
 39- Identify the user account that performed the action and whether it should perform this kind of action.
 40- Investigate other alerts associated with the user account during the past 48 hours.
 41- Contact the account and resource owners and confirm whether they are aware of this activity.
 42- Check if this operation was approved and performed according to the organization's change management policy.
 43- Considering the source IP address and geolocation of the user who issued the command:
 44    - Do they look normal for the user?
 45    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
 46    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
 47- Investigate the deleted log trail's criticality and whether the responsible team is aware of the deletion.
 48- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
 49
 50### False positive analysis
 51
 52- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and IP address conditions.
 53
 54### Response and remediation
 55
 56- Initiate the incident response process based on the outcome of the triage.
 57- Disable or limit the account during the investigation and response.
 58- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
 59    - Identify the account role in the cloud environment.
 60    - Assess the criticality of affected services and servers.
 61    - Work with your IT team to identify and minimize the impact on users.
 62    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
 63    - Identify any regulatory or legal ramifications related to this activity.
 64- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 65- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 66- Consider enabling multi-factor authentication for users.
 67- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
 68- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
 69- Take the actions needed to return affected systems, data, or services to their normal operational levels.
 70- Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
 71- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 72
 73## Setup
 74
 75The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule."""
 76references = [
 77    "https://docs.aws.amazon.com/awscloudtrail/latest/APIReference/API_StopLogging.html",
 78    "https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudtrail/stop-logging.html",
 79]
 80risk_score = 47
 81rule_id = "1aa8fa52-44a7-4dae-b058-f3333b91c8d7"
 82severity = "medium"
 83tags = ["Domain: Cloud", "Data Source: AWS", "Data Source: Amazon Web Services", "Use Case: Log Auditing", "Resources: Investigation Guide", "Tactic: Defense Evasion"]
 84timestamp_override = "event.ingested"
 85type = "query"
 86
 87query = '''
 88event.dataset:aws.cloudtrail and event.provider:cloudtrail.amazonaws.com and event.action:StopLogging and event.outcome:success
 89'''
 90
 91
 92[[rule.threat]]
 93framework = "MITRE ATT&CK"
 94[[rule.threat.technique]]
 95id = "T1562"
 96name = "Impair Defenses"
 97reference = "https://attack.mitre.org/techniques/T1562/"
 98[[rule.threat.technique.subtechnique]]
 99id = "T1562.001"
100name = "Disable or Modify Tools"
101reference = "https://attack.mitre.org/techniques/T1562/001/"
102
103
104
105[rule.threat.tactic]
106id = "TA0005"
107name = "Defense Evasion"
108reference = "https://attack.mitre.org/tactics/TA0005/"

Triage and analysis

Investigating AWS CloudTrail Log Suspended

Amazon CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your Amazon Web Services account. With CloudTrail, you can log, continuously monitor, and retain account activity related to actions across your Amazon Web Services infrastructure. CloudTrail provides event history of your Amazon Web Services account activity, including actions taken through the Amazon Management Console, Amazon SDKs, command line tools, and other Amazon Web Services services. This event history simplifies security analysis, resource change tracking, and troubleshooting.

This rule identifies the suspension of an AWS log trail using the API StopLogging action. Attackers can do this to cover their tracks and impact security monitoring that relies on this source.

Possible investigation steps

  • Identify the user account that performed the action and whether it should perform this kind of action.
  • Investigate other alerts associated with the user account during the past 48 hours.
  • Contact the account and resource owners and confirm whether they are aware of this activity.
  • Check if this operation was approved and performed according to the organization's change management policy.
  • Considering the source IP address and geolocation of the user who issued the command:
    • Do they look normal for the user?
    • If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
    • If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
  • Investigate the deleted log trail's criticality and whether the responsible team is aware of the deletion.
  • If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.

False positive analysis

  • If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and IP address conditions.

Response and remediation

  • Initiate the incident response process based on the outcome of the triage.
  • Disable or limit the account during the investigation and response.
  • Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
    • Identify the account role in the cloud environment.
    • Assess the criticality of affected services and servers.
    • Work with your IT team to identify and minimize the impact on users.
    • Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
    • Identify any regulatory or legal ramifications related to this activity.
  • Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
  • Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
  • Consider enabling multi-factor authentication for users.
  • Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
  • Implement security best practices outlined by AWS.
  • Take the actions needed to return affected systems, data, or services to their normal operational levels.
  • Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
  • Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).

Setup

The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.

References

Related rules

to-top