Skip to content

SCCM MECM

gzzcoo edited this page Nov 19, 2026 · 1 revision

SCCM/MECM Inventory in the Viewer

DACLhound can add SCCM/MECM inventory to the JSON when collection runs with --sccm. Load that JSON in the Viewer like any other collection.

Guides: Home · Viewer

daclhound collect --host DC01.lab.local -d lab.local -u 'user' -p 'password' --dc-ip 192.0.2.10 --sccm

Collection queries published LDAP information and profiles discovered computers using DNS, SMB, and TCP checks. It is optional because it makes additional network requests and can take time. Results report observed indicators; by themselves, they do not confirm that an attack path is exploitable end to end.

Sites and roles

The Viewer represents SCCM sites as nodes and groups each computer’s observed roles into an SCCM roles relationship. Select that relationship to inspect the site, computer, and detected roles.

SCCM site and role relationships

SCCM roles details

Roles may include Management Point, Distribution Point, SMS Provider, Site Server (Active or Passive), WSUS, MSSQL, and other indicators available in the collection. Evidence depends on network connectivity and the account’s permissions.

Attack transitions

When collected metadata allows DACLhound to assess the prerequisites for a scenario, the graph may show transitions such as CoerceAndRelayToMSSQL, CoerceAndRelayToSMSProvider, or CoerceAndRelayPassiveToActiveServer. Select an edge to review prerequisites, observed evidence, and limitations.

These edges represent candidates that depend on the listed requirements. Collection does not perform coercion or relay, nor does it validate the final attack outcome.

For details on each scenario, see the references linked in its Viewer panel.

DACLhound

Clone this wiki locally