> 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/unusual-process-accessed-a-web-browser-history-file.md).
# Unusual process accessed a web browser history file
### Synopsis
| Field | Value |
| -------------------- | --------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | XDR Agent with eXtended Threat Hunting (XTH) |
| Detector Tags | Sensitive Information Stealing Analytics |
| ATT\&CK Tactic | Discovery (TA0007), Collection (TA0009) |
| ATT\&CK Technique | Browser Information Discovery (T1217), Data from Local System (T1005), Automated Collection (T1119) |
| Severity | Low |
### Description
An unusual process has accessed a web browser history file.
### Attacker's Goals
Obtain access to the user's browsing history and steal their contents.
### Investigative actions
* Determine whether it is legitimate for the process to access web browser history.
* Analyze the process/application that accessed the file.
* Check for any other suspicious actions that were performed by the process.
* Look for unusual access of resources using credentials that may be stored in the above file.
### Variations
Unusual process accessed a web browser history file on Linux
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Discovery (TA0007), Collection (TA0009) |
| ATT\&CK Technique | Browser Information Discovery (T1217), Data from Local System (T1005), Automated Collection (T1119) |
| Severity | Low |
**Description**
An unusual process has accessed a web browser history file.
**Attacker's Goals**
Obtain access to the user's browsing history and steal their contents.
**Investigative actions**
* Determine whether it is legitimate for the process to access web browser history.
* Analyze the process/application that accessed the file.
* Check for any other suspicious actions that were performed by the process.
* Look for unusual access of resources using credentials that may be stored in the above file.
---
# 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/unusual-process-accessed-a-web-browser-history-file.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.