Insights Collector (Microsoft Active Directory) | Insights

The Insights Collector is used to collect data from Active Directory and Active Directory Certificate Services. It provides two services related to Active Directory. Once for Inventory and Event Ingestion and one for Password Auditing.

Gaining visibility into your Active Directory landscape is critical to understand how to approach Identity Security in a proactive way. Insights will highlight potentially malicious events and hygiene recommendations in a prioritized way using True Privilege allowing you to focus on the risks that make the largest impact.

Architecture

📘

The architecture diagram shows individual servers hosting the Inventory and Events feature and the Password Auditing feature, with separate Service Accounts for each component.

If needed, these features can be combined onto a single server and use a single service account.

Active Directory inventory and event ingestion

Bring in users, groups, computers, group policy objects (GPOs), Access Control Lists (ACLs), and Active Directory Certificate Services (ADCS) data from your on-premises Active Directory.

BeyondTrust prerequisites

You must configure the Insights Collector in your Insights Tenant before you can install it on a member server within your Active Directory environment.

Active Directory prerequisites

Requirement
Hardware16 GB RAM, dual-core CPU
Windows member server (domain-joined)

🚧 The Insights Collector is not supported when on a Domain Controller.
Service Account Group MembershipDomain Users
Event Log Reader
Additional Service Account Permissions (If Active Directory has been hardened)Read access to the following Active Directory attributes;

userAccountControl
lastLogon
lastLogonTimestamp
pwdLastSet
Outbound Network Connectivity

(Member Server -> BeyondTrust)
Authentication: https://login.beyondtrust.io

Ingestion Endpoint (Select your region):

- America: https://ingest.beyondtrust.io
- Europe: https://ingest.eu-insights-01.beyondtrust.io
- Canada: https://ingest.ca-insights-01.beyondtrust.io
- UK: https://ingest.uk-insights-01.beyondtrust.io
Internal Network Connectivity

(Member Server -> Domain Controllers)
- TCP 636 (or TCP 389 if non-SSL)
- COM+ Network Access (DCOM-In)
- Remote Event Log Management (NP-In)
- Remote Event Log Management (RPC)
- Remote Event Log Management (RPC-EPMAP)
- Windows Management Instrumentation (ASync-In)
- Windows Management Instrumentation (DCOM-In)
- Windows Management Instrumentation (WMI-In)
Internal Network Connectivity

(Member Server -> ADCS Enrollment Servers)
- COM+ Network Access (DCOM-In)
- Remote Event Log Management (NP-In)
- Remote Event Log Management (RPC)
- Remote Event Log Management (RPC-EPMAP)
- Windows Management Instrumentation (ASync-In)
- Windows Management Instrumentation (DCOM-In)
- Windows Management Instrumentation (WMI-In)
ADCS Enrollment Server PermissionsThe Service Account must have Read access to the following registry keys;

HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CertSvc\\Configuration\\{servername}\\PolicyModules\\CertificateAuthority_MicrosoftDefault.Policy
HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CertSvc\\Configuration\\{servername}
ADCS ConfigurationEnable Audit Certification Services (Success & Failure)
Enable "Issue and manage certificate requests" in CA audit filter

ℹ️ For more information on these configuration settings, refer to the Microsoft documentation.

Active Directory password auditing

Enables support for password auditing capabilities, including identifying blank, duplicate/reused and compromised passwords within your Active Directory domain.

Given the nature of password auditing, the member server must be a tier 0 member of the infrastructure, requiring the highest level of privilege to access.

📘

For more information, see Protecting Tier 0 the Modern Way.

BeyondTrust prerequisites

You must configure the Insights Collector in your Insights Tenant before you can install it on a member server within your Active Directory environment.

Active Directory prerequisites

📘

The Password Auditing feature can be installed as a standalone component on a separate member server using its own Service Account or as part of the Active Directory Inventory and Event feature.

Requirement
Hardware16 GB RAM, dual-core CPU
Windows member server (domain-joined)

🚧 The Insights Collector is not supported when on a Domain Controller.
Service Account PermissionsThe following permissions are configured at the Domain level.

Replicating Directory Changes
Replicating Directory Changes All
Replicating Directory Changes In Filtered Set
Outbound Network Connectivity

(Member Server -> BeyondTrust)
Authentication: https://login.beyondtrust.io

Ingestion Endpoint (Select your region):

- America: https://ingest.beyondtrust.io
- Europe: https://ingest.eu-insights-01.beyondtrust.io
- Canada: https://ingest.ca-insights-01.beyondtrust.io
- UK: https://ingest.uk-insights-01.beyondtrust.io
Internal Network Connectivity

(Member Server -> Domain Controllers)
- TCP 636 (or TCP 389 if non-SSL)

Install the Insights Collector

📘

If choosing to run the Password Auditing feature on a separate component please be aware that only a single Insights Collector needs to be setup within Insights.

  1. Navigate to Insights> Connectors from the top left menu

  2. Click Available Connectors.

  3. Find Insights Collector and click Create Connector

  4. Enter a name for your connector and click Create Connector.

  5. Copy the generated key and save it securely.

  6. Click Download to get the installation file.

  7. Run the installer on your member server.

  8. When prompted, paste the installation key from step 5.

  9. When prompted, select your required features.

    If your deployment is Password Safe on-premises, select the Password Safe check box. If it is Password Safe Cloud, do not select the Password Safe check box and use the Password Safe Cloud connector.

    Options when installing the Insights collector
  10. After installation completes, return to Insights and click Close Key (or View Credentials if you need to access the key again).

  11. Verify the connector appears in your Available Connectors list.

Update or reinstall the Insights Collector

Automatic updates

The Insights connector updates automatically when a new version becomes available, without any need for manual installation.

Reinstall the Insights Collector

  1. Navigate to Insights > Connectors from the top left menu.
  2. Find the Insights Collector you want to reinstall.
  3. Click the menu icon and select View Connector.
  4. Click Settings.
  5. Click the download the installer link.
  6. Run the installer on the member server and follow the on-screen prompts.

Troubleshooting

Common errors

ErrorResolution
Ensure the Registration Key within Insights has not expired. If it has please generate a new Insights Collector.

Ensure the Member Server can communicate to https://login.beyondtrust.io
BeyondTrust Insights Collector Service not StartingEnsure the service accounts are granted Log on as a Service rights on the member server.

Log locations

Management ServiceC:\Program Files\BeyondTrust\Insights Collector\logs
Collectors running as Domain Users%USERPROFILE%\AppData\Local\Temp\insightlogs

Override registry keys

Override registry keys to fine-tune the behavior of the Insights collector, ensuring it operates optimally within your infrastructure. Adjust settings such as targeted forest, targeted domains, and job frequencies to enhance security, improve performance, and tailor the collector functionality to meet your needs.

Configuration

  1. Press Windows + R, type regedit, and press Enter (click Yes if prompted)
  2. Navigate to HKEY_LOCAL_MACHINE\\SOFTWARE\\BeyondTrust\\Insights.
  3. Right-click in the right pane and select New > String Value.
  4. Name the value (details below).
  5. Double-click your key and enter the setting (details below).

Active Directory inventory and event ingestion registry keys

The following registry keys are available to fine-tune the Active Directory Inventory and Event Ingestion component.

Value
TypeDescriptionExampleReason
Forest
StringTargeted forest name to use.exampleForestNameTo determine the AD forest context for LDAP queries for collecting ADCS-related information.
Domain
StringTargeted domain name to use.exampleDomainNameTo limit AD inventory collection to a specific domain.
To enable targeted event collection from a specific domain (in combination with a domain controller).
DomainController
StringTargeted domain controller to use.
Requires the Domain string value to be set.
exampleDomainControllerTo set the target LDAP server for AD inventory collection.
To collect events only from specified domain and its controller(s), if configured.
SecurityLogsDomainControllersTargeted
StringComma-separated list of DCs to target for event collection.

Requires the Domain string value to be set.
dc1,dc2To collect events only from specified domain and targeted domain controller(s), if configured.
SecurityLogsDomainControllersExcluded
StringComma-separated list of DCs to exclude from event collection.

Requires the Domain string value to be set.
dc3,dc4To exclude specific domain controller(s) for event collection.
SkipDomains
StringComma-separated list of domains to skip collecting from.domain1,domain2A setting to exclude specific domains from data collection processes such as Active Directory password auditing.
CollectADCS
StringValues: true(default) or false (default: true).trueFlag to enable the collection of Active Directory Certificate Services (ADCS) data.
ADInventoryJobFrequency
StringFrequency of AD inventory job in minutes (default: 120).120Override the job frequency using a registry setting (if present).
DomainControllerEventJobFrequency
StringFrequency of domain controller event job in minutes (default: 10).10Override the job frequency using a registry setting (if present).
InventoryThreads
StringNumber of inventory threads (default: 25).25Maximum number of parallel threads used for processing ADInventory data, to optimize performance.
UseSSL
StringToggles the use of SSL for LDAP connections (default: true)falseIf LDAP does not use SSL in your environment (ie LDAPS)

Active Directory password auditing registry keys

The following registry keys are available to fine-tune the Active Directory Password Auditing component.

ValueTypeDescriptionExampleReason
PasswordAuditingJobFrequencyStringFrequency of password auditing job in minutes (default: 10080).10080Override the job frequency using a registry setting (if present).
CachePurgeJobFrequencyStringFrequency of cache purge job in minutes (default: 1440).1440Override the job frequency using a registry setting (if present).
CachePasswordAuditFilesStringtrue(default) or false
Local cache of audit database during audit.
trueOverride the default behavior of using a local cache on disk of the database audit. If disk space is a concern this can be disabled.

Information collected and polling periods

The Insights Collector accesses a variety of information. It uses store and forward techniques to store event data locally in the event of a connection issue with a member server.

Data Collected or AccessedDefault Poll Period
Domain Controller Event Log- Windows Event Log (Read by the connected Domain Controller)
- Security Log (See below for detail)
- Last collection date for each pull (to collect new events)
10 minutes
Active Directory Inventory- Active Directory object metadata
- Important Access Control Lists
- Active Directory Certificate Services (ADCS)
- Objects;
- Users
- Groups
- Computer
- Containers
- Organizational Units (OUs)
- Domain
- Group Policy Objects (GPOs)
2 hours - Delta
24 hours - Full
Active Directory Certificate Services (ADCS)- LDAP object properties for certificate authority, certificate templates, and enrollment services from the configuration container
- Security events from the enrollment service machines (see below for detail)
- The agent security Access Control Lists (ACLs) from the enrollment service machines via the registry
- The enrollment agent restrictions from the enrollment service machines via the registry
2 hours - Delta
24 hours - Full
Active Directory Password AuditingThe service account retrieves Active Directory password hashes to the member server, where they stay—they're never transmitted elsewhere or saved to disk.

These hashes are compared locally against the Insights password audit database (including haveibeenpwned.com) to check for weak, shared or compromised passwords. The audit results show pass or fail for each account without including the actual password hash.
24 hours

ℹ️

The Insights Collector gathers information from Active Directory, and sends this information Insights for analysis. Some security solutions may detect this as an attack pattern after the connector is installed.

Security alerts you may see include:

  • Suspicious LDAP search
  • A service account is authenticating over Kerberos
  • A device is sending data externally

Event ID details

Event IDDetailFeature
4768A Kerberos authentication ticket (TGT) was requested. This event generates every time Key Distribution Center issues a Kerberos Ticket Granting Ticket (TGT).Security
4769A Kerberos service ticket was requested. This event generates every time Key Distribution Center gets a Kerberos Ticket Granting Service (TGS) ticket request.Security
4770A Kerberos service ticket was renewed. This event generates for every Ticket Granting Service (TGS) ticket renewal.Security
4771Kerberos pre-authentication failed. This event generates every time the Key Distribution Center fails to issue a Kerberos Ticket Granting Ticket (TGT). This problem can occur when a domain controller doesn't have a certificate installed for smart card authentication (for example, with a "Domain Controller" or "Domain Controller Authentication" template), the user's password has expired, or the wrong password was provided.Security
4776The computer attempted to validate the credentials for an account. This event generates every time a credential validation occurs using NTLM authentication. It occurs only on the computer that is authoritative for the provided credentials. For domain accounts, the domain controller is authoritative. For local accounts, the local computer is authoritative.Security
4624An account was successfully logged on. This event generates when a logon session is created (on destination machine). It generates on the computer that was accessed, where the session was created.Security
4662An operation was performed on an object. This event generates whenever an operation was performed on an Active Directory object. This event generates only if appropriate SACL was set for Active Directory object and performed operation meets this SACL.Security
4740A user account was locked out. This event generates every time a user account is locked out. This account lockout event ID is very helpful when troubleshooting.Security
4742A computer account was changed. This event generates every time a computer object is changed.Security
5136A directory service object was modified. This event generates every time an Active Directory object is modified. To generate this event, the modified object must have an appropriate entry in SACL: the “Write” action auditing for specific attributes.Security
4741This event generates every time a new computer object is created. This event generates only on domain controllers.Security
4670Permissions on an object were changedWindows Server
4717System security access was granted to an accountWindows Server
4720A user account was createdWindows Server
4722A user account was enabledWindows Server
4727A security-enabled global group was createdWindows Server
4728A member was added to a security-enabled global groupWindows Server
4732A member was added to a security-enabled local groupWindows Server
4735A security-enabled global group was changedWindows Server
4738A user account was changedWindows Server
4764A group’s type was changedWindows Server
4886Certificate Services received a certificate requestCertificate
4887Certificate Services approved a certificate request and issued a certificateCertificate
5145A network share object was checked to see whether the client can be granted desired access.Certificate

©2003-2025 BeyondTrust Corporation. All Rights Reserved. Other trademarks identified on this page are owned by their respective owners. BeyondTrust is not a chartered bank or trust company, or depository institution. It is not authorized to accept deposits or trust accounts and is not licensed or regulated by any state or federal banking authority.