Security Connector Web Console

While you configure the network interfaces in the security connector, you can also access the Web Console to configure these interfaces. The Web Console is a web-based user interface. Depending on whether you configure Security Connector with one interface or two interfaces, the Web Console may be on the en1 or the en2 interface.

On the Web Console, you can configure settings for the VM and perform administrative operations. For example, you can:

  • Generate a diagnostic report for debugging purposes. The diagnostic report contains logs and system files. When you encounter an issue that requires additional support, you can provide this report to ​Akamai​ Support. To generate this report, see Generate a diagnostic report.

  • Configure rsyslog: You can configure the VM to send logs to your organization's security information and event management product.

If you enabled and set up the proxy, the Web Console is automatically secured with the TLS certificate that you generated or uploaded from your organization as part of the proxy setup. If you haven’t set up the proxy, you can generate the ​Akamai​ certificate or if your company already has a public key infrastructure (PKI), you can create a certificate signing request (CSR) and upload the signed certificate to ETP. For instructions on creating this certificate, see Create an ​Akamai​ certificate and Create a non-​Akamai​ certificate.

📘

The common name for this certificate is <SC ID>.sc.akaetp.net, where <SC_ID> is the identification number that’s associated with Security Connector. This ID is shown on the Security Connector page (Threat Protection > Clients & Connectors > Security Connectors) in Enterprise Center.

Web Console

Log in to the Web Console

Before you begin:

  • Make sure you’ve generated an ​Akamai​ certificate, or if your organization has a public key infrastructure (PKI), make sure you uploaded the certificate that’s signed by your organization’s certificate authority (CA). If you've set up ETP Proxy, this is the same certificate that’s used for the proxy. For instructions on creating this certificate, see Create an ETP certificate and Create a non-ETP certificate. This certificate must be distributed to user laptops. For more information on distributing the certificate, see Distribute the ETP Proxy certificate.

  • Make sure the common name of the Security Connector certificate matches the ID of the Security Connector. You can see certificate information from the browser you use with the Security Connector. The common name for this certificate is <SC_ID>.sc.akaetp.net, where <SC_ID> is the identification number that’s associated with Security Connector. This ID is shown on the Security Connector page (Threat Protection > Clients & Connectors > Security Connectors) in Enterprise Center.

Complete this procedure to log in to the Web Console.

📘

When accessing the Web Console, you may see an error message because the IP address to access the console does not match the common name for the certificate. You can ignore this message.

To log in to the Web Console:

  1. In your browser, go to https://<Web_Console _Interface_IP>:3000, where <Web_Console _Interface_IP> is the IP address of the Web Console. Keep in mind that the IP address you provide depends on whether the Web Console is on the en1 or en2 interface. For more information on the en1 and en2 interfaces, see Download and deployment.

  2. In the Web Console Login, enter the password for the security connector, and click Login.

Generate a diagnostic report

From the Web Console, you can generate a diagnostic report for debugging purposes. This operation creates a TAR file that you provide to ​Akamai​ Support.

To generate a diagnostic report:

  1. Log in to the Web Console.

  2. Click the gear icon and select Generate Diagnostic Report. A report is generated and saved to wherever your browser saves downloaded files.

Next steps

Contact ​Akamai​ Support and securely send the diagnostic report TAR file to your ​Akamai​ support representative.

Configure rsyslog

From the Web Console, you can configure the security connector to send logs to your organization's security information and event management product. By default, the security connector uses TLS encryption. As a result, a client certificate and client key signed by the CA of the rsyslog server is not required. If a certificate is not provided, the security connector accepts the encryption of the rsyslog server.

📘

Ensure that the remote rsyslog server is configured to accept logs with the TCP.

To configure rsyslog:

  1. Log in to the Web Console.

  2. Click the edit icon to modify the VM settings in the Web Console.

  3. Click the Configure SIEM slider to change it from FALSE to TRUE.

  4. In the Server IP fields, enter the IP address and the port of the rsyslog server.

  5. To enable TLS and transport logs securely with a certificate:

    1. Click the Enable TLS slider to change it from FALSE to TRUE.

    2. In the CA certificate field, paste the contents of a certificate from your trusted CA.

    📘

    If a certificate is not provided, the rsyslog server is trusted by default

  6. Click Save.

Modify the port of the Web Console

By default, the Web Console uses port 3000. However, you can modify it based on the ports allowed in your network. Make sure that the port you provide for this setting is not the one you use for the HTTP Forwarder explicit or transparent proxy.

To modify the port for the Web Console:

  1. In the Security Connector console menu, press 8 or or use the arrow keys to select Advanced and press Enter.

  2. Press 3 or use the arrow keys to select Configure WebUI port and press Enter.

  3. Press C to edit this setting.

  4. Type the new port number and press Enter. Make sure the port number you provide is not used for the transparent or explicit proxy configuration of HTTP Forwarder.

  5. Type yes and press Enter to confirm the change.


Did this page help you?