Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
960 detections
Filters
Last updated
All Time
Detection languages
215
211
197
168
63
Contributors
283
142
113
112
85
Categories
670
218
168
112
95
Platforms
39,897
7,231
6,523
3,864
3,624
960
Products / Services
713
68
64
59
59
MITRE Techniques
310
305
146
136
134
CVEs
5
3
3
2
1
IDS Classtypes
13
11
11
9
8
IDS Protocols
62
1
This rule detects modifications to the user data script of an EC2 instance in AWS. User data scripts are executed when an EC2 instance is launched and can be used to perform initial setup, install software, or run other commands. An adversary modifying this script could achieve persistence or privilege escalation by injecting malicious commands that run upon the next instance boot.
This rule detects when AWS CloudTrail logging configurations are modified, stopped, or deleted. Specifically, it looks for API calls such as 'UpdateTrail', 'StopLogging', 'DeleteTrail', or 'PutEventSelectors' that indicate an attempt to tamper with CloudTrail's ability to record events. Such actions could be performed by an adversary to evade detection by hiding their activities.
This rule detects an excessive number of successful AWS API calls related to discovery activities (e.g., Describe*, List*, Get*) originating from a single IAM user within a 5-minute timeframe. This behavior can indicate an adversary attempting to map out the cloud environment after gaining initial access.
Detects when an AWS CloudWatch log group is deleted. This activity can be an indicator of an adversary attempting to impair defenses by removing or modifying logging capabilities to hide their actions.
This rule detects when an AWS IAM Access Analyzer is deleted. Deleting an Access Analyzer can be a defense evasion technique, as it removes a critical security monitoring tool that helps identify unintended external access to resources. An adversary might delete it to obscure their activities or prevent detection of misconfigurations they introduce.
Detects the registration of a new Multi-Factor Authentication (MFA) method for an AWS user. This can be an indicator of an attacker attempting to maintain persistence or bypass existing MFA controls by registering their own MFA device.
Detects when an AWS Backup Plan or Backup Selection is deleted. This activity can indicate an adversary attempting to inhibit system recovery by removing backup configurations, potentially as a precursor to data destruction or encryption for impact.
Detects a successful attempt to retrieve the encrypted Administrator password for a Windows EC2 instance using the GetPasswordData API call in AWS CloudTrail. This action indicates an adversary is attempting to gain access to credentials for a Windows virtual machine.
Detects AWS IAM activities originating from an EC2 instance that could be used to retain access or escalate privileges. This includes actions like creating users, attaching policies, creating/updating login profiles, creating access keys, creating groups, and creating roles.
Detects attempts to disable multi-factor authentication for an AWS IAM user by monitoring AWS CloudTrail events for 'DeleteVirtualMFADevice' or 'DeactivateMFADevice' actions. This could indicate an adversary attempting to maintain persistent access or bypass MFA for compromised accounts.
Detects when the S3 Public Access Block configuration has been removed from an AWS S3 bucket or an entire AWS account. This action can significantly increase the risk of public exposure for S3 objects, potentially leading to data breaches or unauthorized access. The rule specifically looks for `DeleteAccountPublicAccessBlock`, `DeleteBucketPublicAccessBlock` events, or `PutBucketPublicAccessBlock`/`PutAccountPublicAccessBlock` events where all public access blocking attributes (`RestrictPublicBuckets`, `BlockPublicPolicy`, `BlockPublicAcls`, `IgnorePublicAcls`) are set to false or are missing, indicating a removal or weakening of the public access block.
Detects when AWS VPC Flow Logs are deleted. This action can be an attempt by an adversary to impair defenses by removing or modifying logging capabilities to avoid detection of their activities.
This rule detects potential lateral movement within an AWS environment where an IAM session token, obtained via `GetSessionToken`, is subsequently used from a different IP address than where it was initially requested. This behavior can indicate an attacker has compromised credentials and is attempting to use them from a new location.
This rule detects cryptocurrency mining activity within Amazon EC2, AWS Lambda, or Amazon EKS Runtimes, as reported by AWS GuardDuty. It specifically looks for GuardDuty findings related to 'CryptoCurrency', 'CryptoMinerExecuted', or 'BitcoinDomainRequest' and filters out sample findings.
Detects when an AWS GuardDuty detector is disabled or suspended. This can indicate an adversary attempting to impair defenses to avoid detection.
Detects when an existing password policy is updated or deleted in an AWS account. This could indicate an adversary attempting to weaken password requirements to facilitate brute-force attacks or to remove obstacles for credential reuse.
This rule detects a specific privilege escalation scenario in AWS where a user creates a new access key for another user and then immediately uses that newly created access key from the same IP address to perform further actions. This behavior indicates an attempt to escalate privileges by leveraging a newly generated credential.
This rule detects when a GuardDuty Detector's publishing destination has been deleted. GuardDuty is an AWS threat detection service that continuously monitors for malicious activity and unauthorized behavior to protect AWS accounts and workloads. Deleting its publishing destination prevents GuardDuty from exporting its findings, effectively impairing the organization's ability to detect and respond to security incidents. This action could be performed by an attacker attempting to hide their activities or by an insider aiming to reduce security visibility.
This rule detects AWS IAM activities associated with the S3 Browser utility. Specifically, it looks for attempts to create new users (`CreateUser`), create login profiles (`CreateLoginProfile`), create access keys (`CreateAccessKey`), or put user policies (`PutUserPolicy`) within AWS IAM. The detection is triggered when these actions are performed and the HTTP user agent string in the CloudTrail log indicates the use of 'S3 Browser'. This combination of actions and user agent suggests potential account manipulation for persistence or privilege escalation within an AWS environment.
This rule detects when AWS API Gateway keys are accessed with the 'includeValue' or 'includeValues' parameter set to 'true'. This indicates an attempt to retrieve the actual API key values, which could be a credential access attempt. The rule specifically looks for 'GetApiKey' and 'GetApiKeys' events in AWS CloudTrail logs where the request explicitly asks for the key's value.
Detects when an AWS CloudFront distribution is created or updated with an insecure SSL policy, specifically allowing TLSv1, SSLv3, TLSv1_2016, or TLSv1.1_2016. These protocols are considered insecure and can expose data to various attacks.
Page 40 of 46