Overview
The eyeInspect Command Center and Enterprise Command Center components are Java web applications served by an Apache Tomcat web application server. The eyeInspect Passive Sensor is a Linux application using OpenSSL to secure its communication with the Command Center. This procedure also applies to eyeInspect Passive Sensors integrated in eyeInspect appliances, with some differences in the path of the certificates folder.
X.509 certificates and related private keys provide secure communication on two different channels:
- Between the user's browser and the (Enterprise) Command Center
- Between the Command Center and Passive Sensors
eyeInspect ships with default self-signed certificates, used for both communication channels.
Note that deploying proprietary X.509 certificates in eyeInspect is not supported if the application is configured to be in FIPS-compliant mode.
This guide describes the procedure to replace the default eyeInspect certificates with proprietary ones for three different scenarios:
- Proprietary certificates are used for encrypting HTTPS communication between the user's browser and the (Enterprise) Command Center.
- Proprietary certificates are used for the communication between the user's browser and the (Enterprise) Command Center, and between the Command Center and Passive Sensors.
- Active Sensor Certificates are replaced with customer-specific certificates.