A security analyst is reviewing endpoint telemetry for signs of lateral movement and credential dumping. Which THREE of the following event log indicators or telemetry artifacts suggest potential credential dumping activity targeting LSASS? (Choose THREE)
Sysmon Event ID 10 logs process access with the granted access mask, so lsass.exe being accessed by unverified tools reveals memory-read attempts against the credential store. This is the specific telemetry artefact indicating credential dumping rather than routine authentication activity.
Why this answer
Option A is correct because Sysmon Event ID 10 (ProcessAccess) specifically logs when a process opens a handle to another process, and access to lsass.exe by unverified or unusual tools is a classic credential-dumping indicator (e.g., Mimikatz or procdump). Option D is correct because unsigned or unknown binaries running from writable user paths like C:\Users\Public and then opening handles to LSASS combine two strong red flags: masquerading/execution from atypical locations plus direct LSASS access. Option E is correct because Windows Security Event IDs 4656/4663 record handle requests to objects, and a request to lsass.exe with PROCESS_VM_READ (0x0010) is exactly the permission needed to read LSASS memory for credential extraction.
Option B is not relevant because dfrgui.exe performing scheduled defragmentation is normal system maintenance and does not touch LSASS memory. Option C is not relevant because a standard user changing their own password via Ctrl+Alt+Del is a legitimate, expected activity that does not involve dumping LSASS credentials.
Exam trap
CND often tests the ability to distinguish normal system activities from malicious credential dumping indicators, and candidates may overlook that legitimate processes can also access LSASS, but the combination of unsigned binaries and specific access rights is key.