> 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/possible-collection-of-screen-captures-with-windows-problem-steps-recorder.md).

# Possible collection of screen captures with Windows Problem Steps Recorder

### 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              |
| ATT\&CK Tactic       | Collection (TA0009)    |
| ATT\&CK Technique    | Screen Capture (T1113) |
| Severity             | Medium                 |

### Description

Windows Problem Steps Recorder (psr.exe), can record screen and clicks. Adversaries may abuse psr.exe to create screen captures and collect them afterward.

### Attacker's Goals

Evading security controls and collecting screen captures of the desktop.

### Investigative actions

Monitor the command-line arguments of psr.exe and the process causality. Validate the following criteria, if none of them are correct, follow incident response procedures:

* Check the causality of execution and if the TSS script was executed (Microsoft Troubleshooting Script).
* If output parameters in the command line are executed by the user.
* If the parent process is known in the organization as a support tool.


---

# 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/possible-collection-of-screen-captures-with-windows-problem-steps-recorder.md?ask=<question>&goal=<endgoal>
```

`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.