Detection proposal: Sysinternals ADExplorer Active Directory snapshots

Open
#4,393 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Domain
security

Research direction

Start with the existing Active Directory Discovery story and related issues #4382 and #4383 to understand how detections are organized. Then inspect the detection content and run contentctl-ng build. Done means both proposed ADExplorer detections build successfully and cover the execution and snapshot behaviors described, including excluding the SchCache schema cache.

Written by the indexing model from the issue text.

Description

enhancement

Gap. Scattered Spider, LAPSUS$ and ransomware affiliates use Sysinternals ADExplorer to take a full offline snapshot of Active Directory, then convert it for BloodHound or mine it for targets. security_content has no analytic that references ADExplorer (no name, no OriginalFileName, no snapshot file). Sigma has rules keyed on the image name with a -snapshot argument, or on an ADExplorer image writing a .dat file. In my lab each of those caught only 2 of 4 real snapshots: a renamed copy, a GUI menu snapshot and a non-.dat extension each evade at least one of them.

Proposal.

  • Windows Sysinternals ADExplorer Execution (Anomaly, Endpoint.Processes): process name or OriginalFileName AdExp. Triage fields: renamed and snapshot_cli.
  • Windows AD Snapshot Created By ADExplorer (TTP, Sysmon EID 1 + 11): a process with OriginalFileName AdExp that writes any file other than the ADSI schema cache (SchCache\*.sch, written on every connection). This catches renamed copies, GUI snapshots and any extension.

Both would go under the existing Active Directory Discovery story (T1087.002, T1069.002).

Evidence. Windows Server 2025 lab DC with Sysmon 15.22 and 6 cases (4 snapshots, 1 GUI launch without a snapshot, 1 PowerShell LDAP negative). Results: Execution 5/5, Snapshot 4/4, no SchCache false positive. contentctl-ng build passes. Related: #4382, #4383 and the dMSA proposal.

Dominant language
Python
Stars
1.7k
Forks
507
Avg merge
2d 17h
Merged PRs (30d)
35

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from splunk/security_content

All issues in splunk/security_content

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.