✕
×

Prerequisites and Requirements - Active Directory

SM
By Sarah Marshall time 3 min read time️ Updated Jun 24, 2026

Table of Contents

  1. 1.Prerequisites
  2. 1.1.Prerequisites to Audit Active Directory
  3. 1.2.Prerequisites to Audit Group Policy Objects
  4. 2.Required User Rights
  5. 2.1.Least Privileges
  6. 2.2.Full Privileges
  7. 2.3.Required SQL Server Rights
  8. 2.4.Required Ports

1. Prerequisites

1.1 Prerequisites to Audit Active Directory

  • The Event Viewer for all domain controllers including the primary domain controller should be accessible from the application server. (Required for only Without Agent Auditing)

  • The required user rights to add a domain should meet the requirements that are listed in section 2.

1.2 Prerequisites to Audit Group Policy Objects

  • Windows PowerShell 2.0 and .NET Framework 4.6.2 should be installed on both the server to be audited and the application server (the server where the Solution will be installed).

  • GPMC (Group Policy Management Console) should be installed on the computer where the Solution is installed.

2. Required User Rights

To install and work with the Lepide Data Security Platform, you need to have appropriate rights to the system where it will be installed. Also, you need to have appropriate rights to access Active Directory.

There are two approaches to configure Active Directory with Lepide Data Security Platform:

  • Least Privileges

  • Full Privileges

Note: To understand the difference in the functionalities being offered with both these approaches please refer to the Configuring with Minimum Privileges section.

2.1  Least Privileges

To configure the Lepide Data Security Platform with least privileges, the service account requires the membership of the following groups:

  • A Domain User Account.

  • This account should be a member of the Event Log Readers group inside AD.

  • This account should be a member of the Administrators Group on the Lepide Server.

  • This account should be a member of Organization Management group inside AD for Exchange Auditing.

2.2 Full Privileges

To configure the Lepide Data Security Platform with full privileges the service account requires the membership from any of the following groups:

  • Domain Admins

  • Schema Admins

  • Enterprise Admins

3. Required SQL Server Rights

  • For Windows Authentication: A login for the currently logged on Windows User should exist in SQL Server with the assigned role of dbcreator in SQL server.

  • For SQL Authentication: A local SQL account with dbcreator permission.

Note: For using SQL authentication, the SQL server should be set to mixed authentication mode.

4.  Required Ports

The software uses the following ports for different purposes.

  1. Lepide Data Security Platform uses the following ports for communication:

a.     Port 389 and Port 636 for LDAP queries.

b.     Port 445 for RPCS (Remote Procedure Call Services)

c.     Port 135 for communication to Event Logs

d.     TCP/5985 (HTTP) and TCP/5986(HTTPS) for Remote PowerShell Communication

e.     Default Port for SQL Server Communication. In most cases, the default port for SQL is 1433.

  1. The software also uses the following Microsoft functions, which use different ports:

a.    OpenEventLog, which uses Port 445 and Port 135

b.    ReadEventLog, which uses Port 445 and Port 135

c.    AdsOpenObject, which uses Port 389 and Port 636

  1. Lepide Data Security Platform Web Console uses Port 7778 (HTTP).

  1. Lepide Data Security Platform App uses Port 1051.