> 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-non-browser-process-accessed-a-website-ui.md).
# A non-browser process accessed a website UI
### Synopsis
| Field | Value |
| -------------------- | ---------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | Palo Alto Networks Url Logs |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Web Service (T1102) |
| Severity | Informational |
### Description
An uncommon network communication between a non-browser process and a website UI.
### Attacker's Goals
Data exfiltration or attack tool staging.
### Investigative actions
* Examine the host to verify that the host was not part of infiltration or data exfiltration from the organization.
* Verify that the host doesn't have sensitive company data that can be easily exfiltrated.
### Variations
Suspicious content upload to a known text share website by Non browser process
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------- |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Web Service (T1102) |
| Severity | High |
**Description**
Uncommon data upload to a known text share website through a Non-browser process.
**Attacker's Goals**
Data exfiltration or attack tool staging.
**Investigative actions**
* Examine the host to verify that the host was not part of infiltration or data exfiltration from the organization.
* Verify that the host doesn't have sensitive company data that can be easily exfiltrated.
Uncommon data upload to a website through a Non-browser process
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------- |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Web Service (T1102) |
| Severity | Low |
**Description**
Uncommon data upload to a website through a Non browser process.
**Attacker's Goals**
Data exfiltration or attack tool staging.
**Investigative actions**
* Examine the host to verify that the host was not part of infiltration or data exfiltration from the organization.
* Verify that the host doesn't have sensitive company data that can be easily exfiltrated.
Uncommon data download from a known text share website through a Non-browser process
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------- |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Web Service (T1102) |
| Severity | Medium |
**Description**
Uncommon content download from a known text share website through a Non browser process.
**Attacker's Goals**
Data exfiltration or attack tool staging.
**Investigative actions**
* Examine the host to verify that the host was not part of infiltration or data exfiltration from the organization.
* Verify that the host doesn't have sensitive company data that can be easily exfiltrated.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/a-non-browser-process-accessed-a-website-ui.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.