> For the complete documentation index, see [llms.txt](https://wiki.datadike.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.datadike.com/pam/administration/audit/recordings.md).

# Session recordings

Find, replay, and download the recording of a finished session, and understand what is captured for each protocol and how long it is kept.

## What this is and when to use it

Every session the solution brokers is recorded, whatever the protocol — SSH, RDP, VNC, and database sessions included — and can be replayed afterwards as video with a timeline. The recording is the evidence you use when a text log is not enough: what a person actually saw and did on a graphical desktop, in what order, and for how long.

Use it for incident investigation, for change verification, and for the compliance requirement that privileged activity be reviewable after the fact.

Two distinctions save time here:

* A recording is **after the fact**. Watching a session while it is still running, pausing it, or cutting it off is [live monitoring](https://wiki.datadike.com/pam/administration/sessions/live-monitoring.md).
* A recording is **the whole screen or terminal**. The searchable list of commands typed in SSH and Telnet sessions is a separate record — see [Audit trail](https://wiki.datadike.com/pam/administration/audit/audit-trail.md). Search the command list to find the session, then open the recording to see the context.

## Before you start

* Recordings must actually be stored. The destination is a storage backend, not a per-session switch — see [Session recording](https://wiki.datadike.com/pam/administration/sessions/recording.md). A session routed to the **null** backend still leaves a session record, with no replay behind it.
* Your role must grant audit visibility. Replaying someone else's session is gated by RBAC, in the same way as watching a live session — see [Roles](https://wiki.datadike.com/pam/administration/identities/roles.md).
* Retention applies. Recordings are kept for the window configured in **System settings › Retention**; past that, the session record may remain while its recording does not.

## Steps

1. Open **Audit › Console › Session records**. The dedicated list under **Audit › Sessions › Recordings** shows the same material filtered to recorded sessions.
2. Switch to the **Historical sessions** tab. **Online session** holds sessions that are still running and has no replay — those are handled from [live monitoring](https://wiki.datadike.com/pam/administration/sessions/live-monitoring.md).
3. Narrow the list before you scroll it. You can filter by user, asset, user ID, asset ID, account, protocol, login origin, remote address, and terminal, plus a start and end date.
4. Use **Replay** in the **Operation** column to watch the session in the browser, or **Download** to save a copy for an evidence package.
5. To retrieve a file that moved during the session, use **Transfers** instead of the recording — it keeps a copy of each uploaded and downloaded file. See [File transfer](https://wiki.datadike.com/pam/administration/sessions/file-transfer.md).

## What you should see

The player opens on the session and plays it back with a timeline you can seek through, so a two-hour session can be reviewed at the few moments that matter. The session record around it carries the identity of the session — user, asset and IP, account, protocol, start time, duration.

**Download** produces a file of the session, not a screenshot: it is the same material as the replay, for keeping outside the console.

{% hint style="info" %}
Opening a recording is itself an audited event. It is written to the action log as an *audit activity*, together with access to reports, command records, and transferred files, so a reviewer's access to evidence is traceable.
{% endhint %}

## How to verify it worked

Verify the pipeline end to end, on a session you create for the purpose, rather than assuming an old session is representative:

1. Open a session to the asset whose recording you want to prove — one session per protocol you care about.
2. Do something visually identifiable, then close the session.
3. In **Session records**, confirm the session has left **Online session** and is listed under **Historical sessions** with **Replay** available.
4. Play it back and confirm the identifiable action is there and that playback runs to roughly the recorded duration — a replay that stops early is a different problem from one that never starts.
5. Click **Download** and confirm you receive a file.
6. Open the action log in [Audit trail](https://wiki.datadike.com/pam/administration/audit/audit-trail.md) and confirm your own access to the recording was logged.

Step 3 is the one that catches the common case: if the session stays under **Online session** after you disconnected, the session was never closed properly and the recording will not be offered.

## Common errors

| Symptom                                                           | Cause                                                                     | Fix                                                                                                                                           |
| ----------------------------------------------------------------- | ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| The session is listed but **Replay** is not offered               | Recording was not enabled for that asset or platform when the session ran | Enable it in [Session recording](https://wiki.datadike.com/pam/administration/sessions/recording.md); past sessions cannot be recovered       |
| The session never appears under **Historical sessions**           | The session did not close cleanly and is still held as online             | Check the **Online session** tab; if it lingers after the user disconnected, the session needs to be closed before its recording is available |
| The recording is gone but the session record is there             | The retention window for recordings has passed                            | Raise the window in **System settings › Retention** before you need the evidence, not after                                                   |
| You can replay your own sessions but not other people's           | RBAC does not grant audit visibility to your role                         | Adjust the role — see [Roles](https://wiki.datadike.com/pam/administration/identities/roles.md)                                               |
| You need the file a user copied, not the video of them copying it | Recordings are screen and terminal material only                          | Retrieve the copy from **Transfers** — see [File transfer](https://wiki.datadike.com/pam/administration/sessions/file-transfer.md)            |

## Field reference

Columns on the session record that carries the recording:

| Field      | What it holds                                   |
| ---------- | ----------------------------------------------- |
| Number     | Unique session identifier                       |
| User       | Who opened the session                          |
| Target     | The asset accessed, with name and IP address    |
| Account    | The credential used                             |
| Protocol   | SSH, RDP, SFTP, HTTP, and others                |
| Start date | When the session began                          |
| Duration   | Total length of the session                     |
| Operation  | **Replay** to watch it, **Download** to save it |

Filters available above the list:

| Filter             | Notes                                                                |
| ------------------ | -------------------------------------------------------------------- |
| User / User ID     | The person who opened the session                                    |
| Assets / Asset ID  | The target                                                           |
| Account            | The credential used                                                  |
| Protocol           | Narrows to one protocol, useful when only some platforms record      |
| Login origin       | Where the session was launched from                                  |
| Remote address     | Client source address                                                |
| Terminal           | Which component brokered the session                                 |
| Start and end date | The period; set it first, since the list defaults to a recent window |

## Related pages

* [Session recording](https://wiki.datadike.com/pam/administration/sessions/recording.md) — where recordings are stored, and how to deliberately not store them
* [Live monitoring](https://wiki.datadike.com/pam/administration/sessions/live-monitoring.md) — watching, pausing, and ending a session in progress
* [Audit trail](https://wiki.datadike.com/pam/administration/audit/audit-trail.md) — the command, login, and file transfer records around the recording
* [File transfer](https://wiki.datadike.com/pam/administration/sessions/file-transfer.md) — copies of the files that moved during a session
* [Reports](https://wiki.datadike.com/pam/administration/audit/reports.md) — packaging session evidence for an audit
