<?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/"><channel><title>Cisco AnyConnect Secure Mobility Client — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/cisco-anyconnect-secure-mobility-client/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 03 Jan 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/cisco-anyconnect-secure-mobility-client/feed.xml" rel="self" type="application/rss+xml"/><item><title>Suspicious LSASS Process Access</title><link>https://feed.craftedsignal.io/briefs/2024-01-suspicious-lsass-access/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-suspicious-lsass-access/</guid><description>This rule identifies suspicious access attempts to the LSASS process, potentially indicating credential dumping attempts by filtering out legitimate processes and access patterns to focus on anomalies.</description><content:encoded><![CDATA[<p>The Local Security Authority Subsystem Service (LSASS) is a critical Windows component responsible for enforcing security policies and handling user authentication. Attackers often target LSASS to extract credentials, enabling unauthorized access and privilege escalation. This detection rule identifies suspicious access attempts to LSASS memory, which may indicate credential dumping activities. It filters out common legitimate processes and access patterns to highlight anomalous behaviors associated with credential theft. The rule is designed to detect unauthorized access attempts by monitoring process access events and filtering out known benign processes that interact with LSASS. It helps defenders identify potential credential access attempts before they lead to significant compromise.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to a system, possibly through phishing or exploitation of a vulnerability.</li>
<li>The attacker executes a malicious process or script on the compromised system.</li>
<li>The malicious process attempts to gain a handle to the LSASS process.</li>
<li>The attacker&rsquo;s tool requests specific access rights to LSASS, such as <code>ReadProcessMemory</code> (0x0010) or <code>PROCESS_QUERY_INFORMATION</code> (0x0400), which are necessary for memory dumping.</li>
<li>The attacker&rsquo;s process bypasses or disables endpoint detection and response (EDR) solutions to avoid detection.</li>
<li>The tool dumps the LSASS memory, extracting sensitive information like usernames, passwords, and Kerberos tickets.</li>
<li>The attacker uses the extracted credentials to move laterally within the network, accessing other systems and resources.</li>
<li>The attacker achieves their objective, such as data exfiltration or deployment of ransomware.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful LSASS memory dump can lead to the compromise of domain credentials, allowing attackers to move laterally within the network and gain access to sensitive data and systems. This can result in data breaches, financial loss, and reputational damage. Organizations across all sectors are vulnerable, particularly those with weak credential management practices. A single compromised account can lead to widespread damage, potentially affecting thousands of systems.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Enable Sysmon process access event logging (Event ID 10) as described in the setup instructions linked in the rule to collect the necessary data.</li>
<li>Deploy the Sigma rule &ldquo;Suspicious Lsass Process Access&rdquo; to your SIEM and tune the exclusions based on your environment to reduce false positives.</li>
<li>Review and harden privileged account management practices to limit the impact of credential compromise.</li>
<li>Monitor systems for unusual process creation events, especially those spawning from unexpected locations, to identify potential initial access points.</li>
<li>Regularly scan systems for vulnerabilities and apply patches to prevent exploitation.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>credential-access</category><category>lsass</category><category>windows</category></item></channel></rss>