AWS Config Resource Deletion

Identifies attempts to delete an AWS Config Service resource. An adversary may tamper with Config services in order to reduce visibility into the security posture of an account and / or its workload instances.

Elastic rule (View on GitHub)

  1[metadata]
  2creation_date = "2020/06/26"
  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 = "2023/10/24"
  8
  9[rule]
 10author = ["Elastic", "Austin Songer"]
 11description = """
 12Identifies attempts to delete an AWS Config Service resource. An adversary may tamper with Config services in order to
 13reduce visibility into the security posture of an account and / or its workload instances.
 14"""
 15false_positives = [
 16    """
 17    Privileged IAM users with security responsibilities may be expected to make changes to the Config service in order
 18    to align with local security policies and requirements. Automation, orchestration, and security tools may also make
 19    changes to the Config service, where they are used to automate setup or configuration of AWS accounts. Other kinds
 20    of user or service contexts do not commonly make changes to this service.
 21    """,
 22]
 23from = "now-60m"
 24index = ["filebeat-*", "logs-aws*"]
 25interval = "10m"
 26language = "kuery"
 27license = "Elastic License v2"
 28name = "AWS Config Resource Deletion"
 29note = """## Triage and analysis
 30
 31### Investigating AWS Config Resource Deletion
 32
 33AWS Config provides a detailed view of the configuration of AWS resources in your AWS account. This includes how the resources are related to one another and how they were configured in the past so that you can see how the configurations and relationships change over time.
 34
 35This rule looks for the deletion of AWS Config resources using various API actions. Attackers can do this to cover their tracks and impact security monitoring that relies on these sources.
 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- Identify the AWS resource that was involved and its criticality, ownership, and role in the environment. Also investigate if the resource is security-related.
 41- Investigate other alerts associated with the user account during the past 48 hours.
 42- Contact the account and resource owners and confirm whether they are aware of this activity.
 43- Check if this operation was approved and performed according to the organization's change management policy.
 44- Considering the source IP address and geolocation of the user who issued the command:
 45    - Do they look normal for the calling user?
 46    - 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?
 47    - 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?
 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/config/latest/developerguide/how-does-config-work.html",
 78    "https://docs.aws.amazon.com/config/latest/APIReference/API_Operations.html",
 79]
 80risk_score = 21
 81rule_id = "7024e2a0-315d-4334-bb1a-552d604f27bc"
 82severity = "low"
 83tags = ["Domain: Cloud", "Data Source: AWS", "Data Source: Amazon Web Services", "Resources: Investigation Guide", "Tactic: Defense Evasion"]
 84timestamp_override = "event.ingested"
 85type = "query"
 86
 87query = '''
 88event.dataset:aws.cloudtrail and event.provider:config.amazonaws.com and
 89    event.action:(DeleteConfigRule or DeleteOrganizationConfigRule or DeleteConfigurationAggregator or
 90    DeleteConfigurationRecorder or DeleteConformancePack or DeleteOrganizationConformancePack or
 91    DeleteDeliveryChannel or DeleteRemediationConfiguration or DeleteRetentionConfiguration)
 92'''
 93
 94
 95[[rule.threat]]
 96framework = "MITRE ATT&CK"
 97[[rule.threat.technique]]
 98id = "T1562"
 99name = "Impair Defenses"
100reference = "https://attack.mitre.org/techniques/T1562/"
101[[rule.threat.technique.subtechnique]]
102id = "T1562.001"
103name = "Disable or Modify Tools"
104reference = "https://attack.mitre.org/techniques/T1562/001/"
105
106
107
108[rule.threat.tactic]
109id = "TA0005"
110name = "Defense Evasion"
111reference = "https://attack.mitre.org/tactics/TA0005/"

Triage and analysis

Investigating AWS Config Resource Deletion

AWS Config provides a detailed view of the configuration of AWS resources in your AWS account. This includes how the resources are related to one another and how they were configured in the past so that you can see how the configurations and relationships change over time.

This rule looks for the deletion of AWS Config resources using various API actions. Attackers can do this to cover their tracks and impact security monitoring that relies on these sources.

Possible investigation steps

  • Identify the user account that performed the action and whether it should perform this kind of action.
  • Identify the AWS resource that was involved and its criticality, ownership, and role in the environment. Also investigate if the resource is security-related.
  • 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 calling 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?
  • 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