Active Directory (WIP)
Imports computer objects from Active Directory — the domain's own record of every machine ever joined to it, including the ones that stopped reporting years ago.
| Type name | active_directory |
| Creates | Endpoints |
| Runs on | A sensor, or as an isolated integration with an uploaded CSV |
| Presence flag | active_directory_hosts_exits |
| Field prefix | active_directory_ |
What it contributes
- Identity — name, DNS host name, SAM account name, distinguished name, object GUID, SID, UPN, object class
- Network — IPv4 address, IPv6 address
- Platform: operating system version. The operating system name goes to the
shared
osfield; the integration's own OperatingSystem field is not filled - Lifecycle — created, modified, last logon date, last bad password attempt, enabled flag
- Organisation — managed by, location, description, last known parent, primary group, instance type. The primary group's name is stored in the primaryGroupID field, and the numeric primary group ID is not stored
It writes the shared fields names, os, os_vendor, type, private_ip,
distinguished_name (added to what the asset already holds) and updated_at,
and keeps the whole source row in _meta_active_directory_scan_result. The last
logon date is the sighting it reports for last_seen and first_seen. It does
not write MAC addresses.
A computer object is imported only if its LastLogonDate is present, readable and
within the template's Ignore of host is offline window. Objects with an empty
LastLogonDate, such as pre-staged accounts that never joined, are dropped, even
when the window is not set. Dates are read in the M/d/yyyy h:mm:ss AM/PM,
M/d/yyyy H:mm and d/M/yyyy h:mm:ss AM/PM forms; a date in any other format
counts as missing, and the object is dropped.
Every other source lists machines that are alive. AD lists machines that were ever joined. Assets present in AD but absent from CrowdStrike or Windows Defender are either an agent-coverage gap or dead computer objects nobody cleaned up — both worth knowing.
Data collection
The sensor-side implementation reads a CSV export of computer objects. Produce it
on a domain-joined host with the RSAT ActiveDirectory PowerShell module:
Import-Module ActiveDirectory
$props = @(
'DistinguishedName','DNSHostName','Enabled','IPv4Address','IPv6Address','Name',
'ObjectClass','ObjectGUID','OperatingSystem','OperatingSystemVersion',
'SamAccountName','SID','UserPrincipalName','Created','Modified','Description',
'HomedirRequired','instanceType','LastBadPasswordAttempt','LastKnownParent',
'LastLogonDate','Location','ManagedBy','PrimaryGroup','primaryGroupID'
)
Get-ADComputer -Filter * -Properties $props |
Select-Object $props |
Export-Csv -NoTypeInformation -Encoding UTF8 .\ad-computers.csv
Column names must match the property names above — the parser looks them up by header, and any it cannot find is simply left empty rather than raising an error.
Because unknown headers are skipped silently, a truncated Select-Object produces
a successful run with sparse assets. If a field you expect is empty across every
asset, check the CSV header before suspecting the integration.
Run the export on a host whose regional format writes dates in one of the forms
listed under What it contributes, for example an en-US
session. A missing LastLogonDate column drops every row.
Matching
Each computer object is matched to an existing endpoint by the first rule that finds one:
- SID
- Object GUID
- Distinguished name
- AD name together with the private IP or the AD IPv4 address
- AD name alone
- Host name together with the private IP
- Host name alone
A finding that matches nothing creates a new endpoint, subject to the template's On New Asset Discovered action.
Requirements
This type is the odd one in the catalogue: collection is from a CSV export of
Get-ADComputer that you supply, so the requirements fall mostly on whoever
produces that export rather than on the platform.
Network access
| From | To | Protocol | Port |
|---|---|---|---|
| The sensor running the integration | Nothing — the run parses a CSV export | — | — |
No route from a sensor to a domain controller is needed for the CSV path, which is
what makes this type usable for management forests and air-gapped domains where the
domain is deliberately unreachable. The reach that is needed belongs to the
machine where you run Get-ADComputer — an already domain-joined administrative
host, using whatever access it normally has to the domain.
There is no direct-collection path today. The URL, Username and Password fields are stored but not used: a run on an instance without Isolated Integration ticked fails on the sensor without collecting anything.
Access in Active Directory
| Need | Why |
|---|---|
An account that can run Get-ADComputer against the domain | It produces the export; Authenticated Users is enough in a default domain — see Permissions in Active Directory |
The RSAT ActiveDirectory PowerShell module on that host | Get-ADComputer ships with it rather than with Windows itself — Data collection has the export command |
In this deployment
| Need | Why |
|---|---|
| Console access to upload the export | In Isolated Integration mode the CSV is supplied through the console rather than collected. See Isolated integration |
| A registered sensor to select | Sensor is a required field, even though only the isolated mode collects anything. See Sensors |
Configuration
| Field | Required | Notes |
|---|---|---|
| Name | Yes | Label for this instance |
| URL | Yes | Domain controller URL. Not used by the current collection |
| Username | Yes | Account used for the connection. Not used by the current collection |
| Password | Yes | Password for that account. Not used by the current collection |
| Cookies | No | Extra cookies added to requests |
| Sensor | Yes | Sensor that will run the integration |
| Ignore SSL | Yes | Skips certificate validation |
| Isolated Integration | Yes | See below. Tick it: it is the only mode that collects |
Password and Cookies are write-only: once saved, the console shows a locked box with Replace (and Remove for Cookies) and never displays the value again.
Isolated integration
Ticking Isolated Integration means the integration cannot be started via a sensor — you upload the CSV yourself instead. This is the mode to use when the domain is deliberately unreachable from where sensors run, which is common for management forests and air-gapped domains. It is also the only mode that works today: a non-isolated instance has no collection behind it, and its runs fail.
Permissions in Active Directory
Reading computer objects needs no privilege beyond Authenticated Users in a default domain. Use a dedicated read-only service account anyway, so the access is attributable in domain controller logs.
See also
- Active Directory users — user objects from the same domain
- LDAP users — for a non-AD directory
- Integrations overview — the shared configuration model