| ID | Technique | Tactic |
|---|---|---|
| T1090.003 | Multi-hop Proxy | Command and Control |
Detection: Cisco SA - Access to Anonymizer Services
Description
This analytic detects attempts to access proxy-evasion or anonymizer services using Cisco Secure Access DNS and secure web proxy telemetry. Users who reach anonymizer or proxy-evasion infrastructure are often trying to bypass corporate controls such as secure web gateway inspection, DLP monitoring, CASB visibility, and threat-detection systems. These services frequently establish encrypted tunnels that hide subsequent traffic from inspection. Early identification helps security teams spot circumvention attempts before potential data exfiltration or follow-on malicious activity. Correlating DNS resolution and proxy session data strengthens confidence that access was intentional.
Search
1`cisco_secure_access_dns`
2action = "allowed" category= "*anonymizer*"
3
4| fillnull
5
6| stats count min(_time) as firstTime max(_time) as lastTime values(domain) as domain values(query) as query values(reply_code) as reply_code values(record_type) as record_type by src_ip src_external_ip user identity_type action category sourcetype
7
8| `security_content_ctime(firstTime)`
9
10| `security_content_ctime(lastTime)`
11
12| `cisco_sa___access_to_anonymizer_services_filter`
Data Source
| Name | Platform | Sourcetype | Source |
|---|---|---|---|
| Cisco Secure Access DNS | Other | 'cisco:cloud_security:dns' |
'not_applicable' |
Macros Used
| Name | Value |
|---|---|
| cisco_secure_access_dns | sourcetype="cisco:cloud_security:dns" |
| cisco_sa___access_to_anonymizer_services_filter | search * |
cisco_sa___access_to_anonymizer_services_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Annotations
Default Configuration
This detection is configured by default in Splunk Enterprise Security to run with the following settings:
| Setting | Value |
|---|---|
| Disabled | true |
| Cron Schedule | 0 * * * * |
| Earliest Time | -70m@m |
| Latest Time | -10m@m |
| Schedule Window | auto |
| Creates Finding (Notable) | No |
| Creates Intermediate Finding (Risk Event) | Yes |
Implementation
Ingest Cisco Secure Access DNS and proxy events into Splunk using the Splunk Add-on for Cisco Security Cloud (https://splunkbase.splunk.com/app/7404).
Update the cisco_secure_access_dns macro so it resolves to the indexes, sources, and sourcetypes used in your environment.
Known False Positives
Security research, approved privacy tools, or mis-categorized destinations may appear as anonymizer traffic. Tune this analytic with the filter macro or allow-lists for known-good users, networks, and domains after validating business justification.
Associated Analytic Story
Intermediate Findings
| Message | Entity Field | Entity Type | Risk Score |
|---|---|---|---|
| User $user$ from $src_ip$ accessed proxy-evasion or anonymizer infrastructure (domains=$domain$, categories=$category$). | user | user | 20 |
Threat Objects
| Field | Type |
|---|---|
| domain | domain |
References
Detection Testing
| Test Type | Status | Dataset | Source | Sourcetype |
|---|---|---|---|---|
| Validation | ✅ Passing | N/A | N/A | N/A |
| Unit | ✅ Passing | Dataset | not_applicable |
cisco:cloud_security:dns |
| Integration | ✅ Passing | Dataset | not_applicable |
cisco:cloud_security:dns |
Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI.
Alternatively you can replay a dataset into a Splunk Attack Range
Source: GitHub |
Version: 1