Connect an Azure AKS Cluster

Connect an Azure AKS Cluster in Tenable One Cloud Exposure to get full visibility and risk assessment for all cloud identities and resources associated with the cluster, including information about permissions, subscription usage, and security configurations.

Until you complete the integration, objects and configurations associated with the cluster will not be analyzed or available for investigation in Tenable. A sync status is displayed for each Kubernetes cluster in the relevant inventory view, indicating whether Tenable can connect to the Kubernetes API, and helping you troubleshoot potential connection issues.

Note: Agentless scanning does not support Azure VMs that use ephemeral disks, as this disk type does not support snapshotting. This limitation impacts AKS clusters, which use ephemeral disks by default.

Requirements

For each cluster that you want to monitor, follow the steps described below to:

Note: Enabling the Kubernetes Runtime Detection, Admission Controller and sensor-based Workload Protection, requires you to install a sensor using a Helm chart. This applies across all cloud providers and cluster types.

Grant Tenable Permissions to the Cluster: Microsoft Entra ID with Azure RBAC

If you use Azure RBAC for your Kubernetes cluster authorization, you will need to do the following to grant Tenable permissions to the cluster:

Note: You may choose to use a role with a more limited set of resource permissions, however, this means that you will need to manually add any relevant permissions added in the future.
FedRAMP: If you use Tenable One Cloud Exposure in a FedRAMP environment, make sure to connect integrations only to FedRAMP authorized services and endpoints. You are responsible for confirming that each service you connect meets your FedRAMP requirements. Sending data to a service outside your authorization boundary can put your organization out of compliance with FedRAMP requirements.

Assign Built-in Role Bindings to Tenable

  • If you already connected the Azure subscription where the cluster resides to Tenable, and just need to add Kubernetes-related permissions to a cluster, follow the procedure below.
  • If you did not yet connect the Azure subscription where the cluster resides, follow the procedure documented in Connect an Azure Subscription.

To assign role bindings:

  1. In the Azure portal, navigate to the Subscriptions page, and then click on the relevant subscription.
  2. Click Access control (IAM), and then click Add role assignment.
  3. On the Add role assignment page, search for and select one of the following roles, and then click Next:

    Note: You can only add one role at a time, so you will need to perform these steps twice, once for each role.
    • Azure Kubernetes Service Cluster User Role
    • Azure Kubernetes Service RBAC Reader
  4. Under Assign access to, leave the default selection as User, group, or service principal.
  5. Under Members, click +Select members.
  6. Search for and select Cloud Exposure Connector App, and then click Select.
  7. Click Next, review the new role, and then click Review + assign.
  8. Repeat steps 1 through 7 to add the other role, depending on which role you already chose in step 3.

Add a Custom Tenable Role

If you use Azure RBAC for your Kubernetes cluster authorization, and want to gain IAM visibility within Tenable not provided by the role bindings that you added to the Tenable App, add the following custom role JSON to your subscription. Refer to Azure documentation for more information about custom roles.

To add the Tenable role:

  1. In the Azure portal, navigate to the Subscriptions page, and then click on the relevant subscription.
  2. Click Access control (IAM), and then click Add > Add custom role.
  3. Navigate to the JSON tab and click Edit.
  4. Paste the following role to replace the contents of the JSON:

    Important: Replace {subscription Id} below with your Azure Subscription ID.
    Copy

    JSON

    {
        "properties": {
            "roleName": "Tenable Azure Kubernetes Service Reader",
            "description": "Allows read-only access to see most objects in a namespace.",
            "assignableScopes": [
                "/subscriptions/{subscription Id}"
            ],
            "permissions": [
                {
                    "actions": [
                        "Microsoft.ContainerService/managedClusters/listClusterUserCredential/action"
                    ],
                    "notActions": [],
                    "dataActions": [
                        "Microsoft.ContainerService/managedClusters/*/read"
                    ],
                    "notDataActions": []
                }
            ]
        }
    }
  5. Click Save and then click Review + create.
  6. Review the new custom role, and then click Create.
  7. Return to the Access control (IAM) page and then click Add > Add role assignment.
  8. Search for and select Tenable Azure Kubernetes Service Reader, and then click Next.
  9. Under Assign access to, leave the default selection as User, group, or service principal.
  10. Under Members, click +Select members.
  11. Search for and select Ermetic App, and then click Select.
  12. Click Next, review the new role assignment, and then click Review + assign.

Grant Tenable Permissions to the Cluster: Microsoft Entra ID with Kubernetes RBAC

If you use Kubernetes RBAC for your Kubernetes cluster authorization, to grant Tenable permissions to the cluster, you will need to create a ClusterRole and ClusterRoleBinding for Tenable. Create the following ClusterRole and ClusterRoleBinding for Tenable, using, for example, the kubectl command-line tool:

Note: You may choose to use a role with a more limited set of resource permissions, however, this means that you will need to manually add any relevant permissions added in the future.
Copy

YAML

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: ermetic-kube-connector-cluster-role
rules:
  - apiGroups: ["*"]
    resources: ["*"]
    verbs: ["get", "list", "watch"]
Copy

YAML

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: ermetic-kube-connector-cluster-role-binding
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: ermetic-kube-connector-cluster-role
subjects:
  - apiGroup: rbac.authorization.k8s.io
    kind: User
    name: <ermetic-microsoft-entra-id-application-object-id>

Allow Network Access to Tenable

For Tenable to access the cluster, the cluster endpoint needs to be publicly accessible, and the relevant Tenable IP addresses need to be allowed.

To allow network access:

  1. In the Azure Portal, navigate to Kubernetes services.
  2. Click on the relevant Cluster name.
  3. Under Settings, click on Networking.
  4. Under Security, click the checkbox to Set authorized IP ranges.

    Note: Although Tenable can access the cluster when this setting is disabled, it does not follow security best practice to do so. Instead, this setting should be enabled, and the authorized network should be restricted to specific IP addresses, including those associated with Tenable.
  5. In the Specify IP ranges field that appears, add all Tenable IP addresses associated with your Tenable region.
  6. Click Apply.