Kubernetes Requirements per Cloud

The following table summarizes the permissions and networking settings that are required to work with clusters in each cloud provider. For more details, and specific connection instructions, refer to the documentation link for each provider.

Note: For Azure, permissions are granted differently depending on the authentication/authorization method you use to configure your clusters. The local account authentication method is only supported using the Tenable Kubernetes Cluster Connector, and not via the cloud-based connection procedures for AKS clusters.
AWS Azure (Microsoft Entra ID with Azure RBAC) Azure (Microsoft Entra ID with Kubernetes RBAC) GCP OCI
Required Permissions Create a ClusterRole and ClusterRoleBinding for the Tenable IAM role.
  • Assign built-in role bindings to the Tenable App1
  • Add a custom Tenable role to your cluster/subscription
Create a ClusterRole and ClusterRoleBinding for Tenable Add the Kubernetes Engine Viewer role during GCP connection Create a ClusterRole and ClusterRoleBinding for the Tenable OCI group role.
Network Access Set cluster networking to Public and private, and specify Tenable One Cloud Exposure IP addresses to allow. If the cluster networking is Private, you can connect it via the Tenable Connector. Enable Set authorized IP ranges, and specify Tenable IP addresses to allow. Enable Set authorized IP ranges, and specify Tenable IP addresses to allow. Enable Control plane authorized networks, and specify Tenable IP addresses to allow. Set cluster networking and specify Cloud Exposure IP addresses to allow. See Allow Network Access to Tenable.
Documentation EKS Cluster AKS Cluster: Azure RBAC AKS Cluster: K8S RBAC GKE Cluster OKE Cluster

Required roles 1

  • Azure Kubernetes Service Cluster User Role
  • Azure Kubernetes Service RBAC Reader
Note: While Tenable can access clusters with public access enabled, this configuration does not follow security best practices. To maintain a secure posture and monitor private clusters, the platform recommends using a Helm chart connection.