> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/pam/concepts/session-recording.md).

# Session recording

Session recording in Devolutions PAM captures video and metadata of privileged sessions, enabling audit trails, anomaly detection, and rapid response.

**Session recording** involves capturing real-time video and metadata of user activity during [privileged sessions](/pam/concepts/privileged-session.md). This provides a detailed audit trail that can be reviewed to verify actions and ensure accountability. By recording keystrokes, command inputs, and visual screens, organizations can monitor session behavior and detect anomalies.

In solutions such as Devolutions PAM, session recording supports security teams by enabling them to immediately pause or terminate suspicious sessions. This rapid response capability helps contain potential threats before they escalate. When combined with Devolutions Gateway, it ensures that remote session traffic is securely brokered and monitored, further strengthening the visibility and control of privileged activity.

Session recordings are stored securely and can be accessed for [compliance](/pam/concepts/compliance-reporting.md) checks, investigations, and forensic analysis. Combined with role-based access controls and auditing logs, session recording ensures transparent oversight of [privileged accounts](/pam/concepts/privileged-account.md). It helps maintain compliance with regulatory standards and enhances the organization's ability to monitor, control, and secure sensitive environments.

#### Session recording aliases

* Session auditing
* Privileged session monitoring
* Privileged session recording

#### Related topics

* [Logs, reports, and audits](https://docs.devolutions.net/rdm/concepts/advanced-concepts/logs-reports-and-audits)
* [Security](https://docs.devolutions.net/rdm/concepts/advanced-concepts/security)
* [Permissions/RBAC/Roles](https://docs.devolutions.net/rdm/concepts/advanced-concepts/permissions-rbac-and-roles)

### See also

* [Devolutions Academy – Overview of Devolutions Gateway](https://academy.devolutions.net/student/page/2130656-overview-of-devolutions-gateway?sid=a8dd6031-cbc8-4333-894b-acf977f77506\&sid_i=0)


---

# 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://docs.devolutions.net/pam/concepts/session-recording.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.
