How Tenable Monitors Threats in Your Environment
Tenable monitors your cloud infrastructure and containerized workloads by analyzing suspicious activity within cloud logs and by observing user activities. The monitoring method depends on the environment type and whether you are tracking management-level activity or runtime activity to identify active threats across your environment in near-real time.
Supported Coverage
Tenable provides threat detection coverage across cloud providers and container platforms. The method used is determined by the environment type and the specific logs or events required for detection.
If you have not yet connected the account where you want to enable threat detection, use the following articles to connect the relevant cloud provider.
| Cloud Provider | Article |
|---|---|
| AWS | Connect an AWS Organization |
| Azure | Connect an Azure Organization |
| GCP | Connect a GCP Organization |
The following table provides a breakdown of the supported container platforms and the monitoring methods for each one. If you have not yet connected your clusters, use the relevant articles to connect them.
| Environment Type | Platform | Monitoring Method |
|---|---|---|
| Managed (Public) | Agentless | |
| Managed (Private) | Sensor-based (eBPF) | |
| Unmanaged (Cloud) | Connect a private-managed Kubernetes cluster | Sensor-based (eBPF) |
| On-prem (Unmanaged) | Connect Kubernetes and OpenShift clusters | Sensor-based (eBPF) |
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.
For more details about the sensor requirements, see Sensor Resources.
Monitoring Methods
Tenable uses two primary threat detection methods to collect and analyze user activity.
Agentless
This method uses API integrations to collect and analyze activity logs without requiring software installation.
- Agentless deployment — Operates through API-based log collection, ensuring no software is installed on your environment.
- User-level monitoring — Tracks suspicious activity across your cloud infrastructure.
- Centralized visibility — Detects suspicious activity across all connected cloud accounts.
Runtime Detection (eBPF Sensor-Based)
This method provides runtime visibility by installing a sensor on your clusters. It uses eBPF technology to monitor user activity at the kernel level.
- Granular visibility — Provides near-real time visibility into user activity within the cluster.
- User-level insights — Identifies suspicious activity within the workload that is not visible to cloud provider activity logs.
- Deployment — Easily deployed across clusters using Tenable's Helm chart.
Security and Privacy
The following section outlines the security and privacy practices implemented to protect customer data and ensure the integrity of the Tenable One Cloud Exposure Threat Detection solution.
Minimum Necessary Permissions
Tenable follows a strict least privilege security model to reduce security risks while maintaining the necessary security context for effective monitoring:
- Log analysis: Tenable utilizes the minimum cloud permissions necessary to collect and analyze cloud provider logs, such as AWS CloudTrail, Azure Monitor, and GCP Audit Logs.
- Sensor monitoring — Runtime sensors are configured with the minimum permissions required to monitor Threat Detection activity without granting broad administrative access.
Data Isolation and Residency
- Regional data residency — Data is stored in the region where your Tenable container is deployed, such as US, EMEA, or APAC. This ensures compliance with regional data requirements and keeps security activity data within your preferred geographic boundary.
- Secure log storage — Cloud logs and events are stored within Tenable's secure data store.
Data Encryption and Secure Communication
- Data in transit — All data moving across open networks, including runtime sensor activity data and cloud event logs, is encrypted using TLS 1.2 or higher. Runtime sensors utilize the same security communication protocols as Cloud Exposure vulnerability management and Kubernetes Security Posture Management.
- Data at rest — All stored data and event data is encrypted at rest using AES-256, ensuring your security metadata remains protected against unauthorized access.