Pre-Requisites and Requirements - Lepide Identify

Lepide Identify helps you locate and categorize sensitive information across your environment. Before configuration, ensure the following technical requirements are in place.

1. Prerequisites

  • The .NET Framework 4.6.2 or above must be installed on the system where the DDC Agent is deployed.

  • Ensure all the latest Windows Updates are installed.

  • The SQL Server must be installed and accessible from the system hosting the DDC Agent.

  • TCP/IP protocol should be enabled in SQL Server Configuration Manager.

  • The SQL Server port (default: 1433) must be open in the firewall for inbound connections.

  • The DDC Agent and SQL Server must be able to communicate over the network without interruption.

  • You must have administrative rights to configure the SQL connection and deploy agents.

2. Supported SQL Server Versions

Lepide Identify supports all active versions of Microsoft SQL Server that are compatible with the Lepide Data Security Platform.

3. Permissions and Authentication

  • The user account used for configuration must have read/write access to the SQL database.

  • For connecting the SQL Server:
    - Use Windows Authentication
    or
    - Use SQL Server Authentication with valid credentials.

4. System and Network Requirements

  • Ensure that firewall and antivirus settings allow communication between the Lepide Server, DDC Agent, and SQL instance.

  • Ports used for agent installation and scanning must not be blocked.

5. Before You Begin

  • Verify that all required system services (including WMI and SQL Browser, if applicable) are running.

  • Confirm that sufficient disk space is available on the DDC Agent server for storing classification results.

  • Review existing data classification patterns, tags, and templates before starting configuration, if upgrading from an older version.

Important Notes:

1. You can configure the SQL Server settings from within the Lepide Identify module using the Settings icon.
2. If using a remote SQL instance, ensure connectivity by testing the connection before proceeding with scans.
3. Classification results and logs are stored in the SQL database specified during configuration.