<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Esql - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/esql/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 18 Sep 2026 19:19:34 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/esql/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Detection of Potential Lateral Movement via Alert Correlation</title><link>https://feed.craftedsignal.io/briefs/2026-09-lateral-movement-detection/</link><pubDate>Fri, 18 Sep 2026 19:19:34 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-lateral-movement-detection/</guid><description>This detection capability monitors for lateral movement by identifying sequences where a host IP address from one security alert subsequently appears as the source IP in alerts from a different host.</description><content:encoded><![CDATA[<p>This detection rule provides a higher-order analytical approach to identify lateral movement by correlating disparate security alerts across an enterprise network. Instead of focusing on single atomic events, the rule logic aggregates alerts where the <code>host.ip</code> of one host correlates with the <code>source.ip</code> of alerts originating from a separate host. This pattern suggests an adversary is using a compromised endpoint as a pivot point to conduct further reconnaissance or access additional systems within the environment. The rule filters out low-severity events and specific noise-prone alerts to maintain a high signal-to-noise ratio, effectively acting as an automated threat hunting mechanism to surface cross-host infection chains.</p>
<h2 id="impact">Impact</h2>
<p>Successful lateral movement allows adversaries to navigate an internal network, elevate privileges, and reach high-value assets such as domain controllers, sensitive file shares, or cloud service configuration interfaces. If left undetected, this phase of an attack often precedes ransomware deployment, large-scale data exfiltration, or long-term persistence in the target network.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Prioritized actions for detection and response teams:</p>
<ul>
<li>Deploy the higher-order detection logic to identify cross-host alert correlation patterns indicating potential pivots.</li>
<li>Enable <code>host.ip</code> collection for all endpoints, specifically ensuring Elastic Defend versions 8.18 and above are configured to populate this field as required for the logic.</li>
<li>Review the list of triggered alerts to isolate the patient-zero host; perform network isolation immediately upon confirming lateral movement indicators.</li>
<li>Investigate the specific user accounts associated with the source and destination alerts to determine if credentials were compromised or if non-interactive service accounts are being abused.</li>
<li>Tune the detection logic to account for known network architecture artifacts, such as NAT gateways, proxies, or jump hosts, which may generate frequent cross-host alert patterns.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>lateral-movement</category><category>threat-detection</category><category>esql</category><category>detection-engineering</category></item></channel></rss>