What Threats Tenable Detects
Tenable provides comprehensive visibility into your environment by monitoring different types of activity. By analyzing both individual actions and long-term patterns, it identifies potential security breaches, misconfigurations, and unauthorized activity.
Threat Detection Types
Threat detection is categorized into the following primary types:
| Detection Type | Data Source | Description |
|---|---|---|
| Cloud-based events | Cloud provider logs | Detects suspicious activity based on a single event occurring within your cloud provider (e.g., AWS, Azure, GCP). |
| Sensor-based events | eBPF runtime sensors | Detects activity based on eBPF runtime sensor events, providing deep visibility into workload-level activities. This includes support for Process Execution events and File Open events. |
Threat Detection Families
Within the cloud-based and sensor-based event sources, Tenable groups threats into specific detection families based on behavioral patterns:
Suspicious Activity
Identifies risky events in near real-time that align with known attacker behaviors or security best practices violations. Unlike anomalies, which rely on historical baselines, these detections are triggered by specific, predefined rules, such as the creation of an excessive administrative role or the deactivation of a critical security logging service.
Anomaly Detection
Tenable improves your security posture through continuous risk analysis. By processing your entire cloud activity log, Tenable builds a unique behavior profile for every user and service identity.
Anomaly Categories
Tenable detects several types of anomalies based on deviations from established baselines:
| Category | Description | Examples | |
|---|---|---|---|
| Data and Resource Access | Interactions with data that fall outside of normal job functions | Accessing the contents of an S3 bucket for the first time | |
| Identity and Access | Unusual modifications to identity permissions and capabilities |
|
|
| Infrastructure and Audit | Changes to the monitoring configurations or network security controls of your cloud environment | Modifications to network configurations (Security Groups/VNets) or changes to logging and audit settings | |
| Reconnaissance | Discovery patterns that suggest an attacker is mapping the environment | Unusual API calls to list all resources, users, or security groups |
Anomaly Detection Policies
Tenable offers out-of-the-box anomaly detection policies that relate to behavior patterns common to cloud identities, mapped to activity categories. Examples of these policies include:
- Unusual data access — Detects identities that accessed data without a history of doing so. This is a common technique used by attackers attempting to use stolen credentials.
- Unusual permission management — Detects identities that modified permissions without a history of performing similar actions. This is often used by attackers to gain a foothold in the environment.
For a complete list of policies, navigate to Policies in the Cloud Exposure Console and filter by the Anomaly Detection category.
Learning Period
For both Suspicious Activity and anomaly detections, to ensure accuracy, Tenable follows a specific 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.
Manage Anomaly Findings
Anomaly findings represent behavioral deviations rather than static misconfigurations, so they cannot be traditionally fixed with a remediation script.
- Manual resolution — After investigating, you must manually mark findings as resolved if they represent legitimate activity.
- Automation: Tenable recommends creating automation rules to route high or critical severity anomaly findings to a notification or SIEM integration of your choice.
Malware Execution
Detects the process execution of a binary that has been flagged as known or suspected malware.
Cloud Exposure includes a built-in integration with an industry-leading security provider to deliver malware reputation data based on SHA-256 file hashes.
Threat Detection MITRE ATT&CK Mapping
Tenable uses a comprehensive library of security framework to classify threats across all detection types. By leveraging MITRE ATT&CK®, the globally recognized standard for describing adversary tactics and techniques, Tenable provides full security context for every identified threat. Each detection is explicitly mapped to specific tactics and techniques of MITRE ATT&CK® Enterprise Matrix to accelerate investigation and response:
- Identify attacker objective — See what the attacker is trying to achieve, whether they are seeking initial access, securing long-term access to your system, or preparing to steal sensitive data.
- Identify the technique — Gain a clear understanding of the specific methods being used.
- Visualize the attack path — Understand the progression of a threat and see which stage of an attack is occurring.