Getting Started: Connecting Your Active Directory Domain
Satyam
Last Update hace 2 meses
Active Directory Integration allows SecOps Solution to communicate directly with your on-premises or hybrid Active Directory environment. Once a domain is connected, SecOps Solution can discover computer accounts, synchronize security groups, and onboard devices into your managed asset inventory — all without manual input.
This article walks you through adding your first domain, understanding the validation process, and managing existing domain connections.
Prerequisites
Before adding a domain, ensure the following conditions are met:
Adding a Domain
- A Jump Host Agent is installed and online within your network. The Jump Host Agent acts as the intermediary between SecOps and your domain controller. If you have not yet installed an agent, refer to the Jump Host Agent setup guide.
- The Domain Controller FQDN is reachable from the Jump Host Agent.
- LDAP port 389 (or port 636 for LDAPS) is open between the Jump Host Agent and your domain controller.
- You have domain admin credentials
Adding a Domain
- Navigate to AD Integration from the main navigation menu.
- You will land on the Domains tab by default.
- Click Add Domain in the top-right of the Domains section.
The Add Domain modal will appear. Complete each field as described below.
| Field | Description |
| DNS Domain Name | The fully qualified DNS name of your Active Directory domain. Example: testlab.local |
| NetBIOS Domain Name | The short (pre-Windows 2000) name of the domain. Example: TESTLAB |
| Domain Controller FQDN | The fully qualified hostname of the domain controller SecOps will connect to. Example: dc01.testlab.local |
| LDAP Port | The port used for LDAP communication. Default is 389. Change to 636 if using LDAPS. |
| Use LDAPS (SSL) | Enable this toggle if your domain controller requires encrypted LDAP over SSL (port 636). Requires a valid SSL certificate on the domain controller. |
| Jump Host Agent | Select the Jump Host Agent that has network access to the domain controller. This agent handles all communication between SecOps and your AD environment. |
| Admin Username | A domain account with read access to the directory. Format: DOMAIN\Username or [email protected]. |
| Admin Password | The password for the above account. Credentials are encrypted and stored securely. |
Understanding the Validation Process
| Outcome | What It Means |
| Success | SecOps Solution successfully connected to the domain controller using the credentials provided. The domain is added and ready to use. |
| Failed | The connection could not be established. Review the error message displayed in the banner and refer to the checklist below. |
If Validation Fails
- Confirm the Domain Controller FQDN resolves correctly from the Jump Host Agent's network.
- Verify that port 389 (or 636 for LDAPS) is not blocked by a firewall between the agent and the DC.
- Ensure the Admin Username and Password are correct and the account has not expired or been locked.
- If using LDAPS, confirm the domain controller has a valid SSL certificate and that the Jump Host Agent trusts the certificate authority.
- Check that the Jump Host Agent is online in the Agents section of SecOps.