Install Tenable Identity Exposure

Required User Role: Administrator on the local machine

Tenable Identity Exposure's installation program installs the following components on different servers:

  • A Storage Manager (SM) to host all data based on MSSQL.

  • A Directory Listener (DL) to target audited domains.

  • A Security Engine Node (SEN) to perform security analysis and serve the user interface.

    For more information about how to install the SEN on several machines, see Split Security Engine Node (SEN) Services.

All machines and installed binaries support the application of any security update for the underlying OS, either through Windows Server Update Services (WSUS) or System Center Configuration Manager (SCCM).

Installation Order

To install Tenable Identity Exposure 3.42, proceed in the following order:

Before you start

  • Download the executable programs for Tenable Identity Exposure and Secure Relay from Tenable’s Downloads site.

  • Review the Pre-deployment Requirements.

  • Review On-Premises Architectures and select the TLS Installation Types for your platform.

  • Reserve the following resources and have their information on hand before you install Tenable Identity Exposure:

    • Network — Private IP addresses.

    • Access — DNS name used to access Tenable Identity Exposure’s web portal.

    • Security — TLS certificate and its associated private key to secure access to the web portal.

      For more information, see Network Requirements.

  • Run the installer as a local user or a domain user who is a member of the Local Administrators group.

  • Have account permissions: The account you use to deploy Tenable Identity Exposure must have these specific permissions: SeBackupPrivilege, SeDebugPrivilege, and SeSecurityPrivilege.

  • Restart your server before launching the Tenable Identity Exposure installer for each component.

Installation Procedures

The following procedures install the Tenable Identity Exposure components in TLS with autogenerated and self-signed certificates (Default). For more information, see TLS Installation Types.

  1. On the local machine, run the Tenable Identity Exposure 3.42 On-Premises installer.

    A welcome screen appears.

  2. In the setup language box, click the arrow to select the language for the installation, and click Next.

    The Setup Wizard appears.

  1. Select the Expert Mode checkbox.

  1. Click Next.

    The Custom Setup window appears.

  2. Deselect the Security Engine Nodes and Directory Listener components.

  1. Click Next.

    The TLS Options window appears.

  2. Select the TLS with autogenerated and self-signed certificates (Default) option.

    Optional: If you select TLS with custom certificates without peer verification or TLS with custom certificates with peer verification, the next TLS certificates screen asks you to provide the following information:

    • In the Server PFX Archive box, click ... to browse to your PFX archive.

    • In the PFX Password box, type the password for the PFX file.

    • In the CA Cert File box, click ... to browse to your CA certificate file.

  3. Click Next.

    The Storage Manager window appears.

  1. In the Password box, type a password for the MSSQL database.

    Note: The installer requires an SA password with the syntax described in Strong Passwords for the SQL Server.

Note: Tenable strongly recommends that you keep the default TENABLE instance name.

  1. Click Next.

    The Ready to Install window appears.

  1. Click Install to begin the installation.

    After the installation completes, the Completing the Tenable Identity Exposure Setup Wizard window appears.

  2. Click Finish.

    A dialog box asks you to restart your machine.

  3. Click No.

    Caution: Do not restart the machine now.

  4. Install the Security Engine Node.

  1. On the local machine, run the Tenable Identity Exposure 3.42 On-Premises installer.

    A welcome screen appears.

  2. In the setup language box, click the arrow to select the language for the installation, and click Next.

    The Setup Wizard appears.

  1. Select the Expert Mode checkbox.

  2. Click Next.

    The Custom Setup window appears.

  3. Deselect the Storage Manager and Directory Listener components.

    Note: To install SEN services over several machines, see Split Security Engine Node (SEN) Services.

  4. Click Next.

    The TLS Options window appears.

  5. Select the TLS with autogenerated and self-signed certificates (Default) option.

    Optional: If you select TLS with custom certificates without peer verification or TLS with custom certificates with peer verification, the next TLS certificates screen asks you to provide the following information:

    • In the Server PFX Archive box, click ... to browse to your PFX archive.

    • In the PFX Password box, type the password for the PFX file.

    • In the CA Cert File box, click ... to browse to your CA certificate file.

  6. Click Next.

    The Storage Manager window appears.

  7. Provide the following information:

    • In the MSSQL and Event Logs Storage boxes, type the FQDN or IP address of the Storage Manager.

    • In the Password box, type the service account password for the MSSQL database defined in the Storage Manager installation.

      Note: The installer requires an SA password with the syntax described in Strong Passwords for the SQL Server.

  8. Click Next.

    The Security Engine Node window appears.

  9. In the Host box, type the DNS name (preferred) or IP address of the web server that end users enter to access Tenable Identity Exposure.

Note: By default, the installation process creates a self-signed certificate with the DNS name or the IP address that you entered. For more information, see Change the IIS Certificate.

  1. Click Next.

    The Directory Listener window appears.

  2. In the Ceti box, type the IP address or configured FQDN for the Directory Listener machine.

  1. Click Next.

    The Ready to Install window appears.

  3. Click Install to begin the installation.

    After the installation completes, the Completing the Tenable Identity Exposure Setup Wizard window appears.

  4. Click Finish.

    A dialog box asks you to restart your machine.

  5. Click No.

    Caution: Do not restart the machine now.

  6. Install the Directory Listener.

  1. On the local machine, run the Tenable Identity Exposure 3.42 On-Premises installer.

    A welcome screen appears.

  2. In the setup language box, click the arrow to select the language for the installation, and click Next.

    The Setup Wizard appears.

  1. Select the Expert Mode checkbox.

  1. Click Next.

    The Custom Setup window appears.

  2. Deselect the Storage Manager and the Security Engine Nodes components.

  3. Click Next.

    The TLS Options window appears.

  4. Select the TLS with autogenerated and self-signed certificates (Default) option.

    Optional: If you select TLS with custom certificates without peer verification or TLS with custom certificates with peer verification, the next TLS certificates screen asks you to provide the following information:

    • In the Server PFX Archive box, click ... to browse to your PFX archive.

    • In the PFX Password box, type the password for the PFX file.

    • In the CA Cert File box, click ... to browse to your CA certificate file.

  1. Click Next.

    The Security Engine Node window appears.

  2. In the Host box for RabbitMQ, type the address of the Security Engine Node hosting RabbitMQ.

  1. Click Next.

    The Directory Listener window appears.

  2. In the Subnets box (if applicable), type the subnet information for the Directory Listener.

  3. Click Next.

    The Ready to Install window appears.

  4. Click Install to begin the installation.

    After the installation completes, the Completing the Tenable Identity Exposure Setup Wizard window appears.

  5. Click Finish.

    A dialog box asks you to restart your machine.

  6. Click Yes.

    The machine restarts.

  7. Restart the SEN machine.

  8. Restart the Storage Manager machine.

  1. Log in to Tenable Identity Exposure

  2. Type in your initial credentials with the username [email protected] and the password verySecure1.