Skip to main content

Active Directory

The Active Directory integration reads a domain through LDAP from any domain controller. It runs on an Integrator inside your network, since domain controllers are never reachable from outside.

It is read-only. The integration only ever searches the directory. It never changes an account, a group, a password or a permission.

What it collects​

SyncCollects
Directory syncUsers with their account flags, password and logon times, service principal names, Kerberos delegation and group memberships; groups with their scope, type, member count and privileged status; and on every object the access rights other principals hold over it
Computer discoveryComputer accounts with their DNS name, operating system and version, domain controller role, delegation and logon times, matched into the host inventory
Identity reviewAn assessment of the collected directory, run on the platform after each sync, that raises identity findings

The identity review checks for: members of privileged groups that are stale, disabled or service accounts; accounts whose password never expires or is not required; AS-REP roastable accounts (Kerberos pre-authentication disabled); Kerberoastable privileged accounts (a service principal name on a privileged account); unconstrained and protocol-transition delegation; stale computers; unsupported operating systems; orphaned adminCount on accounts no longer privileged; and dangerous access rights on privileged objects (full control, write DACL or owner, reset password, add member, DCSync held by a principal that should not have them).

Users and groups appear under Identity Exposure; computers join the host inventory.

Create a read-only bind account​

Active Directory lets any authenticated user read the attributes the integration needs, so the bind account is an ordinary domain user with no group memberships beyond the default Domain Users. It does not need Domain Admins, Account Operators or any delegated right. The security descriptor of each object (its owner and permissions) is readable by every authenticated user too, so no extra right is required to collect access rights.

  1. In Active Directory Users and Computers, create a user such as svc-inventory in an organizational unit for service accounts.
  2. Set a long random password, set Password never expires and clear User must change password at next logon.
  3. Do not add it to any group, and do not grant it a logon right on any computer. It only ever binds over LDAP.

Or from PowerShell on a domain controller:

New-ADUser -Name "svc-inventory" -UserPrincipalName "[email protected]" `
-Path "OU=Service Accounts,DC=corp,DC=example,DC=com" `
-AccountPassword (Read-Host -AsSecureString "Password") -Enabled $true `
-PasswordNeverExpires $true -ChangePasswordAtLogon $false

Rotate the password in the integration's settings whenever you rotate it in the domain.

LDAPS and the domain controller certificate​

The integration binds over LDAPS (port 636), so the account's password is never sent in cleartext. Domain controllers with Active Directory Certificate Services, or a certificate from your own CA, serve LDAPS out of the box. If your domain controllers only listen on port 389, enter that port instead: the integration upgrades the connection with StartTLS before binding and refuses to bind if the upgrade fails.

A domain controller certificate issued by a CA the Integrator does not trust (an internal CA, or a self-signed certificate) is accepted on first use: the first connection records the certificate's fingerprint on the integration, and every later connection must present the same certificate. After renewing the certificate, clear the pinned fingerprint in the integration's settings so the new one is recorded. A certificate issued by a trusted CA is verified normally and never pinned.

Connect it​

  1. Under Integrations, add Active Directory with:
    • Domain controller: the hostname or address of any domain controller (a hostname is preferred so the certificate can be matched to it).
    • Base DN: the domain's root, for example DC=corp,DC=example,DC=com. A subtree narrows the collection to that organizational unit.
    • Username: the bind account as a user principal name ([email protected]) or a distinguished name.
    • Password: the account's password.
  2. In the integration's settings, assign the Integrator that can reach the domain controller on port 636 (or 389).
  3. Enable the syncs you want. The identity review runs on the platform after each collection and needs nothing from the Integrator.

A refused username or password fails the sync with an error. It does not report an empty domain.

Samba AD domain controllers answer the same LDAP queries with the same attributes and security descriptors, so a Samba domain connects the same way.