{"description":"Trending threats, MITRE ATT\u0026CK coverage, and detection metadata — refreshed continuously.","feed_url":"https://feed.craftedsignal.io/products/sql-server-reporting-services/","home_page_url":"https://feed.craftedsignal.io/","items":[{"_cs_actors":[],"_cs_cves":[],"_cs_exploited":false,"_cs_products":["Elastic Defend","Microsoft Defender XDR","SentinelOne Cloud Funnel","SQL Server","SQL Server Reporting Services"],"_cs_severities":["medium"],"_cs_tags":["credential_access","lsass","memory_dump","windows"],"_cs_type":"advisory","_cs_vendors":["Elastic","Microsoft","SentinelOne"],"content_html":"\u003cp\u003eThis detection rule identifies the creation of LSASS memory dump files on Windows systems, which is a common technique used by attackers to extract credentials. The rule focuses on specific filenames associated with LSASS dumps and tools used for creating these dumps, such as \u003ccode\u003elsass*.dmp\u003c/code\u003e, \u003ccode\u003edumpert.dmp\u003c/code\u003e, \u003ccode\u003eAndrew.dmp\u003c/code\u003e, \u003ccode\u003eSQLDmpr*.mdmp\u003c/code\u003e, and \u003ccode\u003eCoredump.dmp\u003c/code\u003e. The rule excludes known legitimate crash analysis paths and SQLDumper dump locations to reduce false positives. The rule aims to detect credential access attempts through trusted utilities such as Task Manager or SQLDumper, or known tooling such as Dumpert and AndrewSpecial. It is designed to work with data from Elastic Defend, Microsoft Defender XDR, SentinelOne Cloud Funnel, and Sysmon.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker gains initial access to a Windows system (e.g., through phishing or exploiting a vulnerability).\u003c/li\u003e\n\u003cli\u003eThe attacker executes a tool or utility to create a memory dump of the LSASS process. This can be done using built-in tools like Task Manager or SQLDumper, or third-party tools like Dumpert or AndrewSpecial.\u003c/li\u003e\n\u003cli\u003eThe tool writes the LSASS memory dump to a file with a name matching a known pattern, such as \u003ccode\u003elsass.dmp\u003c/code\u003e, \u003ccode\u003edumpert.dmp\u003c/code\u003e, or \u003ccode\u003eSQLDmpr0001.mdmp\u003c/code\u003e.\u003c/li\u003e\n\u003cli\u003eThe file is created in a location that is not a known legitimate crash dump location (e.g., not in \u003ccode\u003e\\Windows\\System32\\config\\systemprofile\\AppData\\Local\\CrashDumps\\\u003c/code\u003e).\u003c/li\u003e\n\u003cli\u003eThe attacker may move, copy, or archive the dump file to avoid detection or to prepare it for exfiltration.\u003c/li\u003e\n\u003cli\u003eThe attacker uses another tool, such as Mimikatz, to parse the LSASS memory dump and extract credentials.\u003c/li\u003e\n\u003cli\u003eThe attacker uses the extracted credentials to move laterally to other systems or to access sensitive data.\u003c/li\u003e\n\u003cli\u003eThe final objective is often to gain domain administrator privileges or to exfiltrate sensitive data.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation and credential extraction can lead to complete domain compromise, unauthorized access to sensitive data, and significant financial or reputational damage. The impact is amplified if the compromised system is a domain controller, jump host, or privileged admin workstation. The rule is designed to detect the initial stage of credential access and prevent further damage.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eEnable Sysmon FileCreate events (Event ID 11) to capture the creation of LSASS memory dump files.\u003c/li\u003e\n\u003cli\u003eDeploy the Sigma rule \u003ccode\u003eLSASS Memory Dump Creation\u003c/code\u003e to your SIEM to detect suspicious LSASS memory dump creation events and tune for your environment.\u003c/li\u003e\n\u003cli\u003eInvestigate any alerts generated by the Sigma rule, focusing on the process executable, parent process, file path, and user context.\u003c/li\u003e\n\u003cli\u003eIf a suspicious LSASS memory dump is found, isolate the affected host and begin credential hygiene for implicated accounts and systems.\u003c/li\u003e\n\u003cli\u003eBlock known malicious tools like Dumpert and AndrewSpecial from running on your network.\u003c/li\u003e\n\u003cli\u003eMonitor for related credential-access, staging, privilege, or lateral-movement alerts for the same user or host.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2024-01-02T12:00:00Z","date_published":"2024-01-02T12:00:00Z","id":"/briefs/2024-01-lsass-dump-creation/","summary":"This rule identifies the creation of LSASS memory dump files, often indicative of credential access attempts using tools like Task Manager, SQLDumper, Dumpert, or AndrewSpecial, by monitoring for specific filenames and excluding legitimate dump locations.","title":"LSASS Memory Dump Creation Detection","url":"https://feed.craftedsignal.io/briefs/2024-01-lsass-dump-creation/"}],"language":"en","title":"CraftedSignal Threat Feed — SQL Server Reporting Services","version":"https://jsonfeed.org/version/1.1"}