1. System Requirements

1.1 Basic System Requirements

• Required Processor

  • Minimum 6 core processor

  • Recommended 8 core processor

• Required RAM

  • Minimum 16 GB RAM

  • Recommended 32 GB RAM

• Required free disk space

  • Minimum 100 GB

  • Recommended 200 GB

• Any of the following Windows Operating Systems.

  • Windows Server OS: 2016, 2019, 2022 and 2025 (latest)

• Supported SQL Server Options for Storing Auditing Logs:

  • Any of the following SQL Server instances, either local or network hosted.

  • Recommended: Network-hosted SQL Server.

  • Any SQL Server above and including SQL Server 2016 (standard or enterprise)

• .NET Framework 4.6.2 developer pack and above

• Network Bandwidth Recommendations:

  • We recommend the use of Giga switches and a Giga Lan adapter on your local network (on-premise) and you should have a Giga network plan supported on Azure as well. The internet speed is also recommended to be in Giga (the more the better).

  • The network speed between on-premise machines and Azure virtual machines should be similar to what we normally have when transferring data between two machine within local network.

1.2 Supported Servers for Auditing

Supported Versions: All Windows Servers above Windows Server 2016

1.3 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 the file server. There are two approaches to configure Windows File Server with Lepide Data Security Platform:

• With Least Privileges

• With Full Privileges

Least Privileges

• To configure the Lepide Data Security Platform with least privileges the service account requires the following rights:

• A domain user account.

• This account should have Db owner/Db_creator rights over the SQL databases. An SQL account with the mentioned privileges can also be used.

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

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

• This account should have List Folder/Read Data, Traverse Folder/Execute File and Read Permissions rights on the Shares which are to be audited.

• This account should be used to Logon to the Lepide Server to Configure the File Server for Auditing.

• The SYSTEM account should have Modify rights on the folder where the agent is installed.

Full Privileges

• To configure the Lepide Data Security Platform with full privileges the service account requires the following rights:

• Member of Domain Admins Group in Active Directory

• Should have access to the admin$ on the File Servers

1.4 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.

1.5 Required Ports

The software uses the following ports for different purposes.

Lepide Data Security Platform uses the following ports for communication:

• Port 389 and Port 636 for LDAP queries.

• Port 445 for RPCS (Remote Procedure Call Services)

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

• Port 3000 is the default port used for communication between the Agent and the Lepide Console. This can be changed if required

Lepide Data Security Platform Web Console uses Port 7779 (HTTP). This is the default port and can be changed during or after installation.

Lepide Data Security Platform App uses Port 1051.