FAQ: Threat Detection and Threat Story
This article contains a list of frequently asked questions related to Cloud Threat Detection and Cloud Threat Story within Tenable One Cloud Exposure.
Threat Detection
This section contains a list of frequently asked questions related to Cloud Threat Detection within Cloud Exposure.
Licensing and Billing
Cloud threat detection is included as part of the Cloud Exposure Enterprise license. Enabling these capabilities does not incur additional costs and does not increase your count of billable resources.
In-Account Scanning
In-account scanning is not relevant for threat detection. While in-account scanning performs vulnerability and data scanning locally within the customer's infrastructure, Tenable detects threats by analyzing sensor activity events and cloud provider logs directly through the Cloud Exposure platform. Consequently, all threat identification occurs within the Cloud Exposure platform rather than through the in-account scanning infrastructure.
Near Real-Time (NRT) Detection
Yes. Tenable utilizes a Near Real-Time (NRT) approach. By continuously collecting and processing cloud events and sensor data, Tenable identifies and alerts on suspicious activity as it is identified.
Data Retention
Data retention periods for the Enterprise / CNAPP Complete license depend on the type of data:
- Cloud events (agentless monitoring): 90 days
- Runtime events (sensor-based monitoring) : 90 days
- Detections — 1 year
Learning Period
The learning period is the time Tenable needs to establish a baseline of normal behavior for an identity before it can accurately identify deviations. It applies to threats surfaced from the following sources:
- Cloud Policies — Policies in the Anomaly Detection. Matching resources are displayed in Cloud Findings.
- Threat Detection Rules — Rules that detect threats based on behavior patterns. Suspicious activity that matches rules are displayed as detections in Threat Detections.
Tenable follows this learning lifecycle:
- Analysis period — Tenable analyzes up to 12 months of historical data and requires at least 30 days of active observation to establish a baseline for an identity.
- Recurring behavior — When similar anomalous behavior is discovered after an initial finding or detection is opened:
- Within 30 days — Tenable adds the behavior to the existing finding or detection and reopens it if it was previously resolved.
- After 30 days — Tenable generates a new finding or detection.
Custom Detection Rules
Custom detection rules are currently on the product roadmap and will be available as a future update.
Remediation
Remediation capabilities are currently on the product roadmap and will be available as a future update.
API Support
API support for threat detection findings is currently on the product roadmap and will be available as a future update.
Threat Story
This section contains a list of frequently asked questions related to Threat Story within Cloud Exposure.
Threat Stories vs. Threat Detections
A threat detection identifies a single suspicious activity within your cloud runtime environment, such as a modified security group. A threat story connects multiple related detections observed over time by related entities, such as a shared actor, to show you the entire scope of a potential attack.
Event Correlation
Tenable automatically correlates security events by analyzing shared contextual data. This data includes the specific actor identity, the timeframe of the events, the affected cloud resources, and the progression of events across your runtime cloud environments.
Investigation Workflow
Open the threat story detail view and follow these steps to investigate the event:
- Review the overview details — Look at the Summary and Impact sections located directly below the top metadata panel to understand what occurred and how it affects your security posture.
- Analyze the relationship map — Use the interactive visual Graph further down the page to trace the connections between the threat actor, the threat story, and the affected resources.
- Inspect the data — View the individual records listed under the Detections table at the bottom of the page to see each specific step of the event.
Status Tracking
Yes, you can track your investigation by updating the workflow status of a threat story. You can set the status to reflect whether the threat story is Open, In Progress, or Resolved based on your internal triage and remediation efforts.