Connect Network-Isolated Servers

You can connect network-isolated servers to Tenable One Cloud Exposure for the following integrations:

  • IaC Security:
    • GitHub Enterprise Server
    • GitLab Self-Managed Server
  • SIEM
    • QRadar
  • Workload Protection:
    • Container Image Registries (3rd Party)

To connect such servers, first add a Tenable Endpoint Connector for each server you want to integrate, and then proceed with adding the integration. Adding a connector via a Helm chart on a dedicated Kubernetes cluster that is in the same network as, and connected to, the integration.

How Tenable Connects to Your Server

The following steps describe how Cloud Exposure connects to your server when you install the connector on a dedicated Kubernetes cluster via a Helm chart:

  1. When you Add a Connector, a workload (deployment) is created and runs in your cluster. This workload:
    • Doesn't expose any of your ports externally, and isn't accessible from the internet.
    • Is configured to only trust the Cloud Exposure platform.
  2. The workload initiates a secure, dedicated connection with Cloud Exposure using reverse proxy.
  3. The workload routes traffic from the secure connection to the network-isolated server, and back.
  4. Tenable then uses the secured connection to periodically access the network-isolated server.
Important: This process doesn't expose the network-isolated server to the internet. All external communication is performed only via the created workload.

Add a Connector

Add a connector for each network-isolated server you want to integrate with Cloud Exposure. Support is currently available for the following integrations:

To add Tenable Endpoint Connector:

  1. In the Cloud Exposure Console, navigate to Settings > Integrations.
  2. (Optional) Select an account scope in the Organization dropdown.
  3. Click Add Integration.
  4. In the Integrations Library, click Endpoint Connector. The Endpoint Connector wizard opens.
  5. Enter the following Integration Details (step 1 in wizard) and then click Next:
    1. Name. The connector name, as it will appear in the Cloud Exposure Console.
    2. Endpoint. The hostname or IP address of the integration. For example, github.tenable.com or 192.82.156.1.
    3. Port. The port number used by the integration.
  6. Deploy on Kubernetes Cluster (step 2 in wizard). Deploy the connector on a dedicated Kubernetes cluster that is in the same network as, and connected to, the integration:
    1. Install Helm as a package manager for Kubernetes. Please refer to Helm’s documentation to get started.
    2. Configure kubectl to connect to your Kubernetes cluster.
    3. Run the following command to add the Tenable repo:
      helm repo add tenable https://charts.tenable.com
    4. To connect and send data to Tenable, run the command that appears in the wizard. This command installs the endpoint connector on the Kubernetes cluster.
  7. Click Finish.

Advanced Connector Configuration

You can use the values.yaml file to help you customize the connector configuration for advanced use cases. You can retrieve this file via a helm command, configure its values as needed, and then include it when you run the helm install command.

Note: Some of the file values can also be provided as arguments within the helm install command itself.

To configure your connector via the values.yaml file:

  1. Run the following command to retrieve the values.yaml:

    helm show values tenable/tenable-cloud-security-endpoint-connector

  2. Configure the values.yaml file as needed, and then save the file.
  3. Append the file to the end of the helm install command that you run, as follows:
    helm install {...} -f custom-values.yaml

    Where {...} is the dynamically generated command that appears in the Add Clusters dialog.

Values.Yaml Content

The values.yaml file contains the following common parameters:

Parameter Description Default
apiKeyTokenSecretName The name of the Kubernetes secret containing the Tenable API key. This is required only if apiKeyToken is not provided directly.
resources Specifies the compute resource requirements and limits for the pod, including CPU and memory.
tolerations Specifies under what conditions a pod can be scheduled onto a node with taints.
proxyUrl Use a proxy server to connect.
  • Without Authentication:
    proxyUrl: "http://your-proxy:<port>"
  • With Authentication:
    proxyUrl: "http://<username>:<password>@your-proxy:<port>"

Manage Secrets

After you add an integration, use Manage Secrets to change the secrets it authenticates with, without deleting the integration. You might replace a secret to follow your organization's rotation policy or because the secret was exposed, or disable one temporarily.

An integration holds a maximum of two secrets. Create the new secret before you delete the old one so your pipeline or connector keeps working during the switch. Each secret appears only once, when you create it.

To manage the secrets of an integration:

  1. In the left navigation bar, click Settings > Integrations.
  2. In the table, click the actions menu for the integration, and then click Manage Secrets.
  3. Do one of the following:
    • To create a secret, click Create Secret, and then copy the secret to a secure location.
    • To rotate a secret, create a new secret, update everything that uses the old secret and confirm that it works, and then delete the old secret. If the integration already holds two secrets, delete one before you create the new one.
    • To enable or disable a secret, click the Status toggle for the secret. A disabled secret cannot authenticate, so anything that uses it stops working until you enable it again. The other secrets of the integration are not affected.
    • To delete a secret, click the delete icon next to the secret, and then confirm the deletion in the Delete Secret window.

Secret deletion is permanent. Any code that uses a deleted secret stops working immediately. Deleting a secret does not delete the integration or its scan results.

Update the Connector with a New Secret

The connector authenticates with the secret you provided when you installed it. After you create a new secret, update the connector to use it, and then delete the old secret.

To update the connector with a new secret:

  1. Create a new secret in the Manage Secrets window.
  2. Do one of the following, depending on how you provided the secret when you installed the connector:
    • If you provided the secret directly in the helm install command or in the values.yaml file, run the helm upgrade command again with the new secret, either in the command or in the values.yaml file.
    • If you provided the secret through a Kubernetes secret (the apiKeyTokenSecretName parameter), do one of the following:
      • To use a new Kubernetes secret, create a Kubernetes secret that contains the new secret. Then run the helm upgrade command with --set apiKeyTokenSecretName=<new-secret-name>, or set apiKeyTokenSecretName in the values.yaml file to the new name.
      • To keep the existing Kubernetes secret, change its value to the new secret, and then restart the deployment: kubectl rollout restart deployment <deployment-name> -n <namespace>
  3. In the Manage Secrets window, delete the old secret.