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 where you configure settings for the VM and perform administrative operations.

On the Web Console, you can:

Depending on the interfaces you set up for Security Connector, the following applies:

  • If you use one interface, the Web Console is on the en2 interface.
  • If you use two interfaces, the Web Console is on the en1 interface.

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 ​SIA​. 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.

Log in to the Web Console

Complete this procedure to log in to the Web Console. Depending on whether Security Connector receives a TLS certificate, the Web Console is served over HTTP or HTTPS. Note the following:

  • If the Security Connector does not receive a TLS certificate, it is served over HTTP.
  • If the TLS certificate is received, the Web Console is automatically served over HTTPS.

Before you begin:

  • To serve the console over HTTPS, make sure you’ve generated an ​Akamai​ certificate, or if your organization has a public key infrastructure (PKI), make sure you upload the certificate that’s signed by your organization’s certificate authority (CA). If you've set up ​SIA​ Proxy, this is the same certificate that’s used for the proxy. For instructions on creating this certificate, see Create an ​SIA​ certificate and Create a non-​SIA​ certificate. This certificate must be distributed to user laptops. For more information on distributing the certificate, see Distribute the ​SIA​ 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.

To log in to the Web Console:

  1. In your browser, go to https://<SC_ID>.sc.akaetp.net:3000, where <SC_ID> is the identification number that’s associated with Security Connector. This ID is shown as the Connector ID on the Security Connector page (Threat Protection > Clients & Connectors > Security Connectors) in Enterprise Center.

    📘

    By default, the port is 3000. However, you can configure a different port in the Security Connector interface. For more information, see Modify the port of the Web Console.

  2. In the Web Console Login, enter the password for the security connector, and click Login. The username is autofilled with the username admin.

  3. Click Sign In.

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:

In the Web Console, 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.

Select the log level for Security Connector

You can select from these log levels for Security Connector:

  • DEBUG. Records the end user's DNS queries or requests. Also lists detailed trace logs to help IT administrators or ​Akamai​ identify the cause of an issue.
  • INFO. Logs only basic service communication information.
  • WARN. Logs activity that’s suspicious.
  • ERROR. Logs events that cause errors and issues with Security Connector.
  • CRITICAL. Logs the most serious threats detected by Security Connector. Indicates there's a severe risk that malicious activity can result in outages, disrupt services, spread throughout a network, or critically impact an organization's infrastructure.

To select the log level for Security Connector:

  1. In the Web Console, click Edit Configuration.
  2. Select a log level, and click Apply Configuration. A confirmation dialog appears.
  3. Click Confirm. After the configuration completes, a message appears with an operation ID. Click OK.

Configure a syslog server

In the Web Console, you can configure the security connector to send system logs to a syslog server.

📘

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

To configure a syslog server:

  1. In the Web Console, click Edit Configuration.
  2. Go to the SIEM Configuration section.
  3. Enable the Configure SIEM toggle.
  4. In the Endpoint IP field, enter the IP address of the syslog server.
  5. Enter the port of the syslog server. By default, the port is 514.
  6. To use TLS for a syslog connection, turn on the toggle for TLS Enabled.
  7. If you enabled TLS, paste the contents of your CA certificate in PEM format.
  8. Click Apply Configuration. A confirmation dialog appears.
  9. Click Confirm. After the operation completes, a message appears with an operation ID. Click OK.

Capture Security Connector packets

Complete these steps to capture packets that are directed to Security Connector. Capturing these packets can help with Security Connector troubleshooting and analysis.

To capture Security Connector packets:

  1. In the Web Console, click the gear icon, and select Packet Capture.
  2. In the Packet Capture dialog, complete these steps:
    1. In the Interface menu, select the network interface where you want to capture packets.
    2. Select the packet data that you want to capture. You can select from these options:
      • Protocols: All, Ports: All

        📘

        This option is selected by default.

      • Protocols: TCP, Ports: 80 and 443
      • Protocols: All, Ports: All except 80 and 443
  3. Select the duration of the capture. By default, 1 minute is selected.
  4. Click Capture. After the capture completes, the file is downloaded to the location your browser saves downloaded files. The file has this naming convention:
    packetCapture_<YYYY-MM-DD_HH_MM_SS>_utc.pcap
    where <YYYY-MM-DD_HH_MM_SS> is the date and time that the capture occurred.

Modify the port of the Web Console

You can modify the port for the Web Console 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.

    📘

    If HTTP Forwarder is disabled, Advanced may appear as menu item 7.

  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?