Configure Threat Detection
To enable Threat Protection on a given account, you need to connect the account to Tenable One Cloud Exposure and grant Tenable the specific logs or events required for detection. You can enable this feature for the following platforms:
AWS: Configure CloudTrail Access
Tenable reads activity logs from an AWS CloudTrail to monitor activity for your connected account. During the account connection process, you must choose a trail and grant Tenable access to it.
- If you already connected the AWS account where you want to enable Threat Detection, but haven’t yet added the required permissions, follow the procedure below.
- If you did not yet connect the AWS account where you want to enable Threat Detection, follow the procedure documented in Connect an AWS Account.
To verify whether or not you have already added Threat Detection permissions, navigate to Settings > Accounts > AWS in the Cloud Exposure Console, and check the status of the account.
- If the status is Connected, the required permissions have already been granted.
- If the status is Connected with issues, and the tooltip indicates that Monitoring (read-only) permissions have not been granted, follow the procedure below.
To grant threat detection permissions:
- In the Cloud Exposure Console, navigate to Settings > Accounts > AWS.
- Locate the relevant account and click Edit.
- Navigate to step 2 (Permissions) of the wizard, enable the Monitoring (read-only) permission, and then click Next.
- Click Finish.
- Verify that the Status of the account is Connected.
Azure: Grant Activity Logs Permissions
Tenable reads Azure activity logs to monitor activity for your connected account. During the account connection process, you must grant Monitoring (read-only) access to Tenable.
- If you already connected the Azure account where you want to enable Threat Detection, but haven’t yet added the required permissions, follow the procedure below.
- If you did not yet connect the Azure account where you want to enable Threat Detection, follow the procedure documented in Connect an Azure Subscription.
To verify whether or not you have already added Threat Detection permissions, navigate to Settings > Accounts > Azure in the Cloud Exposure Console, and check the status of the account.
- If the status is Connected, the required permissions have already been granted.
- If the status is Connected with issues, and the tooltip indicates that Monitoring (read-only) permissions have not been granted, follow the procedure below.
To grant threat detection permissions:
- In the Cloud Exposure Console, navigate to Settings > Accounts > Azure.
- Locate the relevant account and click Edit.
- Navigate to step 3 (Permissions) of the wizard, enable the Monitoring (read-only) permission, and then click Next.
- Click Finish.
- Verify that the Status of the account is Connected.
- Follow the Azure Required Permissions article and verify that AuditLog.Read.All permission is granted.
GCP: Grant Audit Logs Permissions
Tenable reads GCP audit logs to monitor activity for your connected account. During the account connection process, you must grant Monitoring (read-only) access to Tenable.
- If you already connected the GCP account where you want to enable Threat Detection, but haven’t yet added the required permissions, follow the procedure below.
- If you did not yet connect the GCP account where you want to enable Threat Detection, follow the procedure documented in Connect a GCP Project.
To verify whether or not you have already added Threat Detection permissions, navigate to Settings > Accounts > GCP in the Cloud Exposure Console, and check the status of the account.
- If the status is Connected, the required permissions have already been granted.
- If the status is Connected with issues, and the tooltip indicates that Monitoring (read-only) permissions have not been granted, follow the procedure below.
To grant threat detection permissions:
- In the Cloud Exposure Console, navigate to Settings > Accounts > GCP.
- Locate the relevant account and click Edit.
- Navigate to step 3 (Permissions) of the wizard, enable the Monitoring (read-only) permission, and then click Next.
- Click Finish.
- Verify that the Status of the account is Connected.
- Follow the Google Required Permissions article and verify that Audit logs permission is granted.
Kubernetes: Install the Kubernetes Sensor
Tenable identifies suspicious activity within your containerized workloads by collecting events via the Kubernetes sensor. To enable threat detection for a cluster, you must install the eBPF sensor-based technology.
- If you already connected the cluster where you want to enable threat detection, but haven’t yet installed the sensor, follow the procedure documented in Install the Runtime Detection Sensor for Kubernetes.
- If you already connected the cluster and enabled the sensor, you need to re-install it to have the runtime detection capabilities.
- If you did not yet connect the cluster, follow the procedure documented in Connect a Cluster via Helm Chart.
To verify whether or not you have already installed the sensor and enabled threat detection, navigate to Explore > Kubernetes Clusters in the Cloud Exposure Console and check the status of the cluster:
- If the status is Connected, the sensor is active and permissions have been granted.
- If you see a different status, and the tooltip indicates that there is an issue with the cluster, follow the procedure below.
To install or update the sensor:
- In the Cloud Exposure Console, navigate to Explore > Kubernetes Clusters.
- Locate the relevant cluster and click Edit > Install / Upgrade Helm.
- Follow the steps in the wizard to set up and run Helm command.
- Click Close.
- Verify that the Status of the cluster is Connected.