Cisco Secure Firewall - High EVE Threat Confidence
Description
The following analytic detects connections with a high Encrypted Visibility Engine (EVE) threat confidence score, indicating potentially malicious behavior within encrypted traffic. It leverages Cisco Secure Firewall Threat Defense logs and evaluates the EVE_ThreatConfidencePct field, which reflects the system's confidence in classifying encrypted sessions as threats based on machine learning models and behavioral analysis. A score equal to or greater than 80 suggests the connection is highly likely to be associated with malware command and control (C2), remote access tools, or suspicious tunneling behavior. If confirmed malicious, this may indicate covert communication over TLS from compromised hosts.
Query · spl
`cisco_secure_firewall` EventType=ConnectionEvent EVE_ThreatConfidencePct >= 80
| stats count min(_time) as firstTime max(_time) as lastTime
Values(rule) as rule
Values(url) as url
by EVE_Process, EVE_ThreatConfidencePct, src, dest, dest_port, transport, action
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| `cisco_secure_firewall___high_eve_threat_confidence_filter`
Implementation guide
This search requires Cisco Secure Firewall Threat Defense Logs, which
includes the ConnectionEvent EventType. This search uses an input macro named cisco_secure_firewall.
We strongly recommend that you specify your environment-specific configurations
(index, source, sourcetype, etc.) for Cisco Secure Firewall Threat Defense logs. Replace the macro definition
with configurations for your Splunk environment. The search also uses a post-filter
macro designed to filter out known false positives.
The logs are to be ingested using the Splunk Add-on for Cisco Security Cloud (https://splunkbase.splunk.com/app/7404).
The access policy must also enable logging.
Known false positives
- Some benign applications may exhibit behaviors that resemble encrypted threat patterns, especially if they use uncommon encryption libraries or custom protocols. Custom-developed or internal tools may trigger high EVE confidence scores depending on how they encrypt data. It is recommended to validate the associated process (`EVE_Process`) and destination context, and correlate with other logs (e.g., endpoint or threat intel) before taking response action.
Analyst notes
Known false positives: Some benign applications may exhibit behaviors that resemble encrypted threat patterns, especially if they use uncommon encryption libraries or custom protocols.
Custom-developed or internal tools may trigger high EVE confidence scores depending on how they encrypt data.
It is recommended to validate the associated process (EVE_Process) and destination context, and correlate with other logs (e.g., endpoint or threat intel) before taking response action.