Threat Detection Requirements

Tenable threat detection provides near real-time analysis of security events and identifies runtime risks by analyzing cloud logs and activity collected by Kubernetes sensors.

The configuration and integration requirements depend on your environment:

Requirements

To enable threat detection, you must configure your environment to export the relevant activity logs or install the Kubernetes sensor, depending on the cluster type.

Cloud Accounts

To monitor suspicious activity within your cloud infrastructure, you must enable activity logs of your cloud provider accounts so that Tenable can collect and analyze events across your cloud environment. The following table provides a breakdown of the required logs for each cloud provider.

Platform Requirement
AWS Configure AWS CloudTrail
Microsoft Azure Grant permissions to access your Azure activity logs
GCP Grant permissions to access your Google audit logs

Kubernetes Clusters

To monitor and identify suspicious activity within your containerized workloads, you must install the Kubernetes sensor. The sensor provides visibility into Kubernetes cluster suspicious activity events for both cloud-based and on-premises environments. To install the sensor, see Install the Runtime Detection Sensor for Kubernetes.

Sensor Resources

The runtime detection sensor requires the following pod-level resources:

Category Requirement / Utilization
CPU (Pod Limit) 1 Core (1000m)
Memory (RAM) 1 GiB
API Permissions Read-only access to query the Kubernetes cluster. See the entire list here.

Permissions and Connectivity

The runtime detection sensor requires the following cluster permissions and network access:

  • API access — The sensor requires a ClusterRole with permissions to get, list, and watch resources such as pods, nodes, and namespaces. See the entire list here.
  • Network — The sensor must be able to reach the Tenable One Cloud Exposure platform via outbound HTTPS. For more details, see Requirements.