> 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-data-source/palo-alto-networks-global-protect.md).

# Palo Alto Networks Global Protect

Alerts related to data source "Palo Alto Networks Global Protect".

| Alert                                                                                                                                                                                                        |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [A disabled user attempted to log in to a VPN](/analytics-alerts/alerts-by-name/a-disabled-user-attempted-to-log-in-to-a-vpn.md)                                                                             |
| [A Successful VPN connection from TOR](/analytics-alerts/alerts-by-name/a-successful-vpn-connection-from-tor.md)                                                                                             |
| [A user connected to a VPN from a new country](/analytics-alerts/alerts-by-name/a-user-connected-to-a-vpn-from-a-new-country.md)                                                                             |
| [A user logged in at an unusual time via VPN](/analytics-alerts/alerts-by-name/a-user-logged-in-at-an-unusual-time-via-vpn.md)                                                                               |
| [Azure Privilege Escalation Using an Application](/analytics-alerts/alerts-by-name/azure-privilege-escalation-using-an-application.md)                                                                       |
| [First VPN access attempt from a country in organization](/analytics-alerts/alerts-by-name/first-vpn-access-attempt-from-a-country-in-organization.md)                                                       |
| [First VPN access from ASN for user](/analytics-alerts/alerts-by-name/first-vpn-access-from-asn-for-user.md)                                                                                                 |
| [First VPN access from ASN in organization](/analytics-alerts/alerts-by-name/first-vpn-access-from-asn-in-organization.md)                                                                                   |
| [Impossible traveler - VPN](/analytics-alerts/alerts-by-name/impossible-traveler-vpn.md)                                                                                                                     |
| [Possible Insider Threat Activity](/analytics-alerts/alerts-by-name/possible-insider-threat-activity.md)                                                                                                     |
| [Possible phishing attack via Microsoft Teams](/analytics-alerts/alerts-by-name/possible-phishing-attack-via-microsoft-teams.md)                                                                             |
| [Potential extraction of NAA Account Credentials in Microsoft Configuration Manager](/analytics-alerts/alerts-by-name/potential-extraction-of-naa-account-credentials-in-microsoft-configuration-manager.md) |
| [VPN access with an abnormal operating system](/analytics-alerts/alerts-by-name/vpn-access-with-an-abnormal-operating-system.md)                                                                             |
| [VPN login attempt by a honey user](/analytics-alerts/alerts-by-name/vpn-login-attempt-by-a-honey-user.md)                                                                                                   |
| [VPN login Brute-Force attempt](/analytics-alerts/alerts-by-name/vpn-login-brute-force-attempt.md)                                                                                                           |
| [VPN login by a dormant user](/analytics-alerts/alerts-by-name/vpn-login-by-a-dormant-user.md)                                                                                                               |
| [VPN login by a service account](/analytics-alerts/alerts-by-name/vpn-login-by-a-service-account.md)                                                                                                         |
| [VPN Login Password Spray](/analytics-alerts/alerts-by-name/vpn-login-password-spray.md)                                                                                                                     |
| [VPN login with a machine account](/analytics-alerts/alerts-by-name/vpn-login-with-a-machine-account.md)                                                                                                     |


---

# 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-data-source/palo-alto-networks-global-protect.md?ask=<question>&goal=<user_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.