> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/a-successful-vpn-connection-from-tor.md).
# A Successful VPN connection from TOR
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Hour |
| Required Data | Requires one of the following data sources:
Palo Alto Networks Global Protect OR Third-Party VPNs
|
| Detection Modules | Identity Analytics |
| ATT\&CK Tactic | Initial Access (TA0001), Command and Control (TA0011) |
| ATT\&CK Technique | Proxy: Multi-hop Proxy (T1090.003), Valid Accounts (T1078) |
| Severity | High |
### Description
A successful VPN connection from a TOR exit node.
### Attacker's Goals
Gain initial access to organization and hiding itself.
### Investigative actions
* Block all web traffic to and from public Tor entry and exit nodes.
* Search for additional logins from the same user around the alert timestamp.
### Variations
A Successful VPN connection from TOR via Mobile Device
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001), Command and Control (TA0011) |
| ATT\&CK Technique | Proxy: Multi-hop Proxy (T1090.003), Valid Accounts (T1078) |
| Severity | Medium |
**Description**
A successful VPN connection from a TOR exit node.
**Attacker's Goals**
Gain initial access to organization and hiding itself.
**Investigative actions**
* Block all web traffic to and from public Tor entry and exit nodes.
* Search for additional logins from the same user around the alert timestamp.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/a-successful-vpn-connection-from-tor.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.