Higher-Order-Rule — CraftedSignal Threat Feed

Multiple Rare Elastic Defend Behavior Rules Triggered on Single Host

hello@craftedsignal.io — Sat, 11 Apr 2026 12:00:00 +0000

This Elastic Defend rule is designed to detect potentially compromised hosts by identifying those that trigger multiple distinct and rare behavior rules. The rule leverages Elastic’s ESQL to analyze endpoint alerts, focusing on behavior rules that are observed on only a single host globally within a specified lookback window. This approach filters out common or widely triggered rules, reducing false positives and highlighting truly anomalous behavior. The rule aims to pinpoint hosts exhibiting unusual activity patterns that may indicate malicious actions, warranting immediate investigation and response. This detection method became generally available in Elastic Stack version 9.3.0.

Attack Chain

Initial Access: An attacker gains initial access through an unknown vector.
Privilege Escalation: The attacker attempts to elevate privileges on the compromised host.
Execution: The attacker executes malicious code or commands via a script or binary.
Defense Evasion: The attacker attempts to evade detection by disabling security tools or masking their activities.
Lateral Movement: The attacker attempts to move laterally to other systems on the network.
Command and Control: The attacker establishes a command and control channel to communicate with a remote server.
Collection: The attacker gathers sensitive data from the compromised host or network.
Impact: The attacker achieves their final objective, which could include data exfiltration, system disruption, or ransomware deployment.

Impact

A successful attack can lead to significant data breaches, system compromise, and operational disruption. The targeted sectors are broad, as the rule is designed to detect general anomalous behavior. Depending on the attacker’s objectives, the impact could range from data theft and financial loss to complete system shutdown and reputational damage. Hosts identified by this rule should be considered high-priority candidates for incident response and further investigation. The number of victims is dependent on the scope of the intrusion, but this detection aims to limit the spread of the attack by identifying compromised hosts early.

Recommendation

Deploy the provided ESQL rule to your Elastic environment (min. version 9.3.0) to detect hosts triggering multiple rare behavior alerts as indicated by the rule_id c4f7a2b1-5d8e-4c3a-9b6e-2f1a0d8c7e5b.
Investigate any hosts flagged by this rule, reviewing the associated behavior rule names and process command lines to understand the triggering actions as documented in the rule’s note.
Examine endpoint and network data for the affected host to assess the scope of the compromise and potential persistence mechanisms, per the investigation guidance in the note.
Document and exclude known-good rule names or hosts from the detection if legitimate single-host tools or scripts trigger multiple rare behavior rules as described in the note.
Enable Elastic Defend on all endpoints to ensure the availability of the required endpoint.alerts data source.

Multiple Alerts in Different ATT&CK Tactics by Host

hello@craftedsignal.io — Wed, 24 Jan 2024 12:00:00 +0000

This detection rule, created by Elastic, is designed to identify potentially compromised hosts by aggregating alert data. It focuses on scenarios where a single host triggers multiple alerts associated with different phases of an attack, as defined by the ATT&CK framework. The rule calculates a risk score based on the number and severity of alerts, prioritizing hosts exceeding a defined threshold. By focusing on hosts exhibiting diverse attack tactics, analysts can more effectively triage and respond to complex, multi-stage intrusions. This rule helps filter out noisy alerts such as “Agent Spoofing”, “Compression DLL Loaded by Unusual Process”, and “Potential PrintNightmare File Modification”, and focuses on alerts where kibana.alert.risk_score is greater than 0.

Attack Chain

An adversary gains initial access to a host through various methods.
The adversary executes malicious code or commands on the host.
The attacker establishes persistence to maintain access.
The adversary attempts to escalate privileges to gain higher-level control.
The attacker performs lateral movement to compromise other systems.
The adversary gathers information about the compromised environment.
The attacker exfiltrates sensitive data from the network.
The attacker achieves their final objective, such as data theft or disruption of services.

Impact

A successful attack, as identified by this rule, can lead to significant data breaches, system compromise, and operational disruption. Multiple alerts across various tactics suggest a sophisticated and persistent attacker. Prioritizing hosts identified by this rule enables security teams to quickly contain and remediate advanced threats, minimizing potential damage and reducing the overall impact on the organization. Without this detection, analysts might miss critical correlations between seemingly isolated alerts.

Recommendation

Deploy the provided Sigma rule to your SIEM to identify potentially compromised hosts based on multiple alerts across different ATT&CK tactics.
Investigate any hosts flagged by this rule, correlating the alert data with other logs and telemetry to understand the full scope of the attack.
Tune the threshold values in the Sigma rule (distinct rule count, tactic count, risk score) to align with your environment and risk tolerance.
Enable logging for process creation, network connections, and file modifications on all hosts to provide sufficient data for the detection rule.
Review the “False positive analysis” section of the rule’s documentation to identify and exclude known benign activities that may trigger the rule.
Use the Esql.kibana_alert_rule_name_values field in the rule output to quickly identify the specific alert types triggering the rule.

Multiple Alerts Involving a User Detection

hello@craftedsignal.io — Wed, 24 Jan 2024 10:00:00 +0000

This detection rule, sourced from Elastic’s detection ruleset, is designed to identify potential user account compromises by aggregating and analyzing existing alert data. The rule focuses on scenarios where a single user triggers multiple distinct alerts, suggesting a higher likelihood of malicious activity. By excluding low-severity alerts and known system accounts, the rule aims to minimize false positives and prioritize investigations. This approach is particularly useful in environments where attackers may attempt to blend in with normal user activity while escalating privileges or moving laterally within the network. The rule utilizes esql to correlate alerts based on user ID. The rule was last updated on 2026/04/27.

Attack Chain

An attacker gains initial access to a user account, potentially through phishing, credential stuffing, or other methods.
The attacker attempts to escalate privileges within the compromised account.
The attacker performs reconnaissance activities, such as discovering sensitive files or network shares.
The attacker attempts to move laterally to other systems within the network using the compromised credentials.
The attacker accesses sensitive data, potentially exfiltrating it from the network.
These actions trigger various security alerts related to privilege escalation, lateral movement, and data access.
The “Multiple Alerts Involving a User” rule detects the correlation between these alerts based on the user ID.
Security analysts are alerted to investigate the compromised user account and contain the potential damage.

Impact

A successful attack leveraging a compromised user account can lead to significant data breaches, financial losses, and reputational damage. The impact can range from unauthorized access to sensitive data to the complete takeover of critical systems. By identifying compromised user accounts early, organizations can mitigate the potential damage and prevent further escalation of the attack. This detection rule helps prioritize investigations and ensures that security analysts focus on the most critical threats.

Recommendation

Deploy the Sigma rule Multiple Alerts Involving a User to your SIEM to detect potential user account compromises based on correlated alerts.
Enable audit logging on systems to capture user activity and generate alerts for suspicious actions.
Review and tune the threshold values (e.g., distinct alert count) in the Sigma rule to align with your environment and risk tolerance.
Use the Resources: Investigation Guide tag to access guidance on investigating triggered alerts and identifying compromised user accounts.
Implement role-based access control (RBAC) to minimize the impact of compromised accounts by limiting access to sensitive resources.

Newly Observed High Severity Detection Alert in Elastic SIEM

hello@craftedsignal.io — Wed, 03 Jan 2024 12:00:00 +0000

This detection rule identifies high-severity alerts within Elastic SIEM that are observed for the first time within a 5-day window. The rule focuses on low-volume, newly observed alerts linked to a specific detection rule. By highlighting these novel alerts, analysts can more effectively prioritize their triage and incident response efforts. This allows security teams to focus on potentially new or evolving threats, rather than being overwhelmed by repeated alerts from well-known attack patterns. The rule aims to reduce alert fatigue and improve the speed and accuracy of threat detection and response. The logic excludes threat_match, machine_learning, and new_terms rule types to minimize noisy alerts.

Attack Chain

A malicious activity occurs on an endpoint or within a network, triggering an Elastic SIEM detection rule with a high severity score (>=73).
The Elastic SIEM generates a security alert based on the triggered detection rule. This alert includes details about the event, the affected host, user, and the rule that was triggered.
The “Newly Observed High Severity Detection Alert” rule, running every 5 minutes, queries the .alerts-security.* indices.
The rule filters for alerts that meet specific criteria such as high risk score, excluding certain rule types like “threat_match”, “machine_learning”, and “new_terms”, and excluding endpoint alerts.
The rule aggregates alerts by kibana.alert.rule.name to identify distinct alerts and calculates the first and last time each alert was observed.
The rule determines if the alert is newly observed, defined as the first time it was seen within the last 10 minutes of the rule execution time. This helps filter out alerts that have been occurring for a longer period.
The rule further filters for alerts affecting a single agent (agent_id_distinct_count == 1) and low alert counts (alerts_count <= 10), indicating a potentially novel or isolated incident.
The final output highlights the newly observed, low-frequency, high-severity alert, allowing security analysts to investigate and respond accordingly.

Impact

A successful attack leading to a newly observed high severity alert could indicate a novel or evolving threat that has not been previously seen in the environment. This can lead to a delayed response, potentially allowing the attacker to further compromise systems, exfiltrate data, or cause damage. The impact depends on the specific activity that triggered the underlying high severity alert, but could range from initial access to data breach or ransomware deployment. Failure to prioritize investigation of these new alerts can result in significant financial loss, reputational damage, and operational disruption.

Recommendation

Deploy the Sigma rule Newly Observed High Severity Detection Alert to your SIEM and tune for your environment.
Use the Investigation Steps outlined in the rule’s note field as a guide to triage newly observed alerts.
Review the specific rule investiguation guide for further actions, as referenced in the original Elastic rule’s documentation.
Configure alerting to notify security analysts immediately upon detection of a Newly Observed High Severity Detection Alert.

Multiple Alerts in Same ATT&CK Tactic by Host

hello@craftedsignal.io — Wed, 03 Jan 2024 12:00:00 +0000

This detection rule correlates multiple security alerts associated with the same ATT&CK tactic on a single host within a defined time window (60 minutes). The purpose of this rule is to identify hosts exhibiting concentrated malicious behavior, which may indicate an active intrusion or post-compromise activity. This allows analysts to prioritize triage towards hosts with a higher likelihood of compromise. The rule specifically excludes noisy tactics such as Discovery, Persistence, and Lateral Movement, focusing instead on tactics like Credential Access, Defense Evasion, Execution, and Command and Control. It requires at least three unique detection rules to trigger, ensuring that the activity is not a single, isolated event. The rule also excludes alerts generated by Machine Learning and Threat Match rules, as well as some noisy rules such as “Agent Spoofing - Mismatched Agent ID” and “Process Termination followed by Deletion”.

Attack Chain

Initial Access: An attacker gains initial access to a host through methods like exploiting a vulnerability or using stolen credentials.
Execution: The attacker executes malicious code on the compromised host, potentially using tools like PowerShell or cmd.exe.
Defense Evasion: The attacker attempts to evade detection by disabling security controls or obfuscating their actions.
Credential Access: The attacker attempts to steal credentials from the compromised host, such as passwords or Kerberos tickets.
Command and Control: The attacker establishes a command and control channel to communicate with the compromised host.
Further Exploitation: The attacker uses the compromised host to move laterally within the network, potentially targeting other systems or data.
Data Exfiltration or Impact: The attacker exfiltrates sensitive data from the network or causes damage to systems.

Impact

A successful attack can lead to significant data breaches, financial losses, and reputational damage. By identifying hosts exhibiting multiple alerts related to the same ATT&CK tactic, organizations can proactively respond to potential intrusions before they escalate into more serious incidents. Failure to detect and respond to these types of attacks can result in widespread compromise and significant disruption to business operations.

Recommendation

Deploy the Sigma rule provided in this brief to your SIEM to detect hosts exhibiting multiple alerts within the same ATT&CK tactic. Tune the rule to your environment to reduce false positives.
Investigate hosts that trigger the Sigma rule to determine the root cause of the alerts and take appropriate remediation steps.
Review and update your existing detection rules to ensure they are effective at detecting the latest threats and tactics.
Enable logging for process creation, network connections, and file modifications to provide more visibility into host activity and improve detection capabilities.
Implement a vulnerability management program to identify and patch vulnerabilities on your systems to prevent attackers from gaining initial access.