Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
75 detections
Filters
Last updated
All Time
Detection languages
24
21
18
4
4
Contributors
24
19
7
5
3
Categories
50
40
24
6
4
Platforms
39
12
11
10
4
Products / Services
38
13
7
6
6
MITRE Techniques
18,108
15,614
12,573
8,384
6,204
IDS Classtypes
2
IDS Protocols
2
Detects configuration changes to Oracle Audit Vault. The Vault is the integrity
control for database auditing, so altering its configuration can stop collection,
narrow what is recorded, or redirect the audit trail — removing the evidence of
whatever follows.
Treat any change here as affecting the reliability of all database audit data for
the period concerned.
Onboarding: ORACLE-AUDIT-VAULT is ingested via Syslog (KV) (Bloo extractor 310).
Integration guide: https://bloo.io/docs/hypercloud/syslog-connector
BQL (Bloo Query Language):
stream=configuration where sourcename='ORACLE-AUDIT-VAULT'
and action='CONFIGURATION_CHANGED'
| groupby user, config, srcip
control for database auditing, so altering its configuration can stop collection,
narrow what is recorded, or redirect the audit trail — removing the evidence of
whatever follows.
Treat any change here as affecting the reliability of all database audit data for
the period concerned.
Onboarding: ORACLE-AUDIT-VAULT is ingested via Syslog (KV) (Bloo extractor 310).
Integration guide: https://bloo.io/docs/hypercloud/syslog-connector
BQL (Bloo Query Language):
stream=configuration where sourcename='ORACLE-AUDIT-VAULT'
and action='CONFIGURATION_CHANGED'
| groupby user, config, srcip
An SAP BTP tenant that was recently active stopped producing audit logs
Detects administrative actions that disable or modify Amazon GuardDuty, which could be an attempt to blind security monitoring or evade detection of malicious activity. This includes disabling a detector, deleting publishing destinations, or modifying threat intel and IP sets.
Detects modifications to AWS GuardDuty configurations, including disabling the detector, deleting publishing destinations, or altering threat intelligence sets and trusted IP lists. These actions could indicate an attempt to blind security monitoring or evade detection.
Detects when an administrator explicitly disables Unified Audit Log (UAL) ingestion for Exchange Online using the Set-AdminAuditLogConfig cmdlet. This action effectively stops the generation of audit records for Exchange administration and user activity, a critical defense evasion tactic used to conceal malicious operations.
Detects when an administrator explicitly disables Unified Audit Log (UAL) ingestion for Exchange Online using the Set-AdminAuditLogConfig cmdlet. This action effectively stops the generation of audit records for Exchange administration and user activity, a critical defense evasion tactic used to conceal malicious operations.
Detects when an actor searches Slack audit logs, which could indicate an attacker attempting to understand logging capabilities or evade detection. Also detects bulk session resets initiated by an administrator, which may be a response to an account takeover or an attacker attempting to evict legitimate users from their sessions.
This rule detects a spike in modifications or creations of Azure Diagnostic Settings within a one-hour window. A high volume of 'Diagnostic Setting' operations by a single caller could indicate an attempt to alter logging configurations, potentially to impair defenses or hide malicious activity.
Detects when an actor searches Slack audit logs, which could indicate an attacker attempting to understand logging capabilities or evade detection. Also detects bulk session resets initiated by an administrator, which may be a response to an account takeover or an attacker attempting to evict legitimate users from their sessions.
Detects when an actor searches Slack audit logs, which could indicate an attacker attempting to understand logging capabilities or evade detection. Also detects bulk session resets initiated by an administrator, which may be a response to an account takeover or an attacker attempting to evict legitimate users from their sessions.
This rule detects attempts to disable AWS CloudTrail logging via the AWS API. It specifically looks for HTTP requests to 'cloudtrail.amazonaws.com' with 'StopLogging' in the URI, indicating an attempt to stop CloudTrail from recording API activity.
Detects disabling of AWS CloudTrail audit logging
This rule detects a spike in modifications or creations of Azure Diagnostic Settings within a one-hour window. A high volume of 'Diagnostic Setting' operations by a single caller could indicate an attempt to alter logging configurations, potentially to impair defenses or hide malicious activity.
This rule detects a spike in modifications or creations of Azure Diagnostic Settings within a one-hour window. A high volume of 'Diagnostic Setting' operations by a single caller could indicate an attempt to alter logging configurations, potentially to impair defenses or hide malicious activity.
This rule detects when Azure Monitor Diagnostic Settings are deleted. It specifically looks for HTTP DELETE requests to 'management.azure.com' with 'diagnosticSettings' in the URI. This activity could indicate an attacker attempting to evade detection by removing logging configurations.
Detects various sensitive configuration modifications in AWS that could indicate malicious activity, such as privilege escalation, defense evasion, or data exposure. This rule looks for a curated list of API calls related to changes in IAM, EC2 security groups, S3 bucket policies, and logging configurations.
Detects various sensitive configuration modifications in AWS that could indicate malicious activity, such as privilege escalation, defense evasion, or data exposure. This rule looks for a curated list of API calls related to changes in IAM, EC2 security groups, S3 bucket policies, and logging configurations.
`This rule looks for API calls that stops logging for CloudTrail Lake channels and a trail configuration.
These actions would prevent logging of CloudTrail logs from the time of API call.
These actions would prevent logging of CloudTrail logs from the time of API call.
Looking for changes of remiving the delivery channel or configuration recorder for AWS Config.
Indicative of defense evasion or someone covering their tracks.
This would stop all data such as configuration snapshots and rule compliance notifications from getting to the S3 bucket/SNS topic.
Note: Before you can delete a delivery channel, you must first stop the customer-managed configuration recorder
Indicative of defense evasion or someone covering their tracks.
This would stop all data such as configuration snapshots and rule compliance notifications from getting to the S3 bucket/SNS topic.
Note: Before you can delete a delivery channel, you must first stop the customer-managed configuration recorder
Detects attempts to tamper with AWS CloudTrail or GuardDuty logging configurations by monitoring specific API calls that can disable, modify, or delete logging mechanisms. This includes actions like stopping logging, deleting trails, updating trails, disassociating from master accounts, archiving findings, stopping member monitoring, and deleting or updating detectors. Successful execution of these actions without an error indicates potential malicious activity aimed at evading detection.
Detects various sensitive configuration modifications in AWS that could indicate malicious activity, such as privilege escalation, defense evasion, or data exposure. This rule looks for a curated list of API calls related to changes in IAM, EC2 security groups, S3 bucket policies, and logging configurations.
Page 1 of 4