> 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/audit-trail.md).

# Audit trail

Where the solution writes every login, command, password change, file transfer and administrative operation, how long those records are kept, and how to consult or forward them.

## What this is and when to use it

The audit trail is the set of searchable records the solution writes for everything that happens through it: who logged in and from where, which commands ran inside a session, which passwords changed, which files moved, and which administrative objects were created, edited, or deleted.

Use it when you need to answer a question about the past — "who restarted that host on Friday", "was this account used outside business hours", "who changed that authorization rule".

Three things in the **Audit** area are easy to confuse:

| Area                                                                                   | What it holds                                                            |
| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| **Audit trail** (this page)                                                            | The records themselves — text, searchable, filterable, exportable        |
| [Session recordings](https://wiki.datadike.com/pam/administration/audit/recordings.md) | The video-style replay of a session, played back from the session record |
| [Reports](https://wiki.datadike.com/pam/administration/audit/reports.md)               | Packaged extracts of the same data, generated on demand or on a schedule |

The audit trail is the source; recordings and reports are two ways of looking at it.

## Before you start

* Your role must grant access to the **Audit** area. Reading other people's records is gated by RBAC — see [Roles](https://wiki.datadike.com/pam/administration/identities/roles.md).
* Retention is a system-wide setting, configured in **System settings › Retention**. Records older than the retention window are no longer there to find.
* To forward records off the appliance, the syslog or Elasticsearch target must be reachable from the nodes.

## Where each record lives

| Record               | Console location                         | What it answers                                                                                              |
| -------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Login log**        | **Audit › Console › Login log**          | Who tried to authenticate, with which method, from which address, and whether it succeeded                   |
| **Session records**  | **Audit › Console › Session records**    | Every session opened on an asset, live and historical, with replay and download                              |
| **Online users**     | **Audit › Console › Online users**       | Who is connected to the console right now, with the option to disconnect them                                |
| **Password changes** | **Audit › Console › Password changes**   | Which account had its password changed, by whom or by which automation, from which address                   |
| **Action log**       | **Audit › Log audit › Action log**       | Creation, modification, and deletion of objects — users, assets, rules, permissions                          |
| **Commands**         | **Audit › Sessions › Keylogger**         | Every command typed in an SSH or Telnet session, with its risk classification and a link back to the session |
| **File transfers**   | **Audit › Sessions › Transfers**         | Uploads and downloads made during sessions, with a copy of the file                                          |
| **Job list**         | **Audit › Operation audit › Job list**   | The automations configured to run, with their schedules                                                      |
| **Executions**       | **Audit › Operation audit › Executions** | Each run of each automation, whether it finished, and whether it succeeded                                   |

The **Dashboard** at the top of the **Audit** area is the consolidated view of the same data over **Today**, **7 days**, or **30 days**: total commands and how many of them were risk commands, scheduled and running jobs, online and total sessions, transferred files, accesses, operation log entries, and passwords changed — followed by a table of the most recent sessions.

## What gets recorded

The trail is grouped into families of events:

| Family                      | Events                                                                                                                                                                                                              |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Operational activity**    | Access, access attempt, blocked access, password change                                                                                                                                                             |
| **Configuration activity**  | Changes to system and object configuration                                                                                                                                                                          |
| **Audit activity**          | Access to reports, to command records, to transferred files, and to session recordings                                                                                                                              |
| **Authentication activity** | Successful and failed password authentications, passwords unused for more than a given number of days, passwords used, passwords changed, account discovery, account registration, account use, account association |
| **Access RBAC**             | Users attached to a permission, users removed from a permission, changes to access permissions                                                                                                                      |

{% hint style="info" %}
Reading the trail is itself part of the trail. Opening a recording, a command record, a transferred file, or a report is written as an *audit activity* event, so consulting evidence is as traceable as producing it.
{% endhint %}

### Retention

Records are searchable from the console and kept according to the policies in **System settings › Retention**. Set that window before you need it: a question asked outside the window cannot be answered afterwards, and shortening retention discards history immediately.

### Forwarding to a SIEM

Records can be sent to an external collector, so that the trail survives independently of the appliance. Supported destinations are syslog over UDP, TCP, or TLS, Elasticsearch, e-mail, and plain text export.

| Protocol   | Default port |
| ---------- | ------------ |
| Syslog UDP | 514          |
| Syslog TCP | 514          |
| Syslog TLS | 6514         |

The record format follows a common standard and is consumed without a custom parser by the usual collectors — Splunk, IBM QRadar, Microsoft Sentinel, Elastic Security and the ELK stack, OpenSearch, Google Security Operations, Securonix, LogRhythm, Graylog, Wazuh, Loki and Grafana, Fluentd and Fluent Bit, rsyslog and syslog-ng, SolarWinds, ManageEngine, and Nagios. Configure the destination in **System settings** — see [Syslog and SIEM](https://wiki.datadike.com/pam/administration/integrations/syslog-and-siem.md).

## Steps

Investigating an incident follows the same shape in every log:

1. Open the log that holds the kind of evidence you need, from the table above.
2. Narrow the **period** with the date selector at the top of the page — start date and end date. Every log defaults to a recent window, not to everything.
3. Search by the identifier you actually have. **Login log** searches by username; **Session records** searches by user, asset, user ID, asset ID, account, protocol, login origin, remote address, and terminal.
4. Sort by any column to bring the extremes together — repeated failures on one username, or every session on one asset.
5. Follow the record to its context. From a command in **Keylogger**, use **Go to session** to reach the session it was typed in, and from there its [recording](https://wiki.datadike.com/pam/administration/audit/recordings.md). From **Transfers**, download the copy of the file that moved.
6. Export the result if the evidence has to leave the console, or build a repeatable extract in [Reports](https://wiki.datadike.com/pam/administration/audit/reports.md) instead.

## What you should see

![The Operate logs screen, with the change history and one record open](https://1085357737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7xzJyi9JVzRwnV6JzUho%2Fuploads%2Fgit-blob-0ee200912e806bd3de78865d9ed1a1ba8505ca3b%2Faudit-trail.png?alt=media)

**1** How many records the current filter returns. **2** One record, with the action and the resource it touched. **3** The resource type, which is how you narrow to one kind of object. **4** The total behind the filter.

Each log is a table you can filter, sort, and export. Two details are worth knowing before you read them:

* In **Session records**, live sessions are under **Online session** and finished ones under **Historical sessions**. A session that ended appears in the second tab with **Replay** and **Download** in the **Operation** column.
* In **Keylogger**, the **Risk level** column shows how the command was treated by policy: **Accept** in green means it was allowed, **Reject** in red means it was blocked for violating a rule. The classification comes from [command inspection](https://wiki.datadike.com/pam/administration/access/command-filtering.md), so a red row is a blocked attempt, not a command that ran.

## How to verify it worked

Do not trust the presence of a log page; prove that it is capturing. Each check below is one action followed by one lookup:

1. **Login log** — sign in once with a deliberately wrong password, then sign in correctly. Both attempts must appear, with **Failure** carrying a reason and **Success** carrying the authentication method.
2. **Keylogger** — open an SSH session, run a harmless command and one command your policy rejects. Both must be listed, the second classified **Reject**, and **Go to session** must lead back to that session.
3. **Password changes** — rotate one managed account, then confirm the account appears with the automation or user as **Modifier** and the source address filled in.
4. **Action log** — change any object, such as a user's group, and confirm the modification is recorded against your username.
5. **Dashboard** — set the filter to **Today** and confirm the counters moved by the actions you just performed.

If you forward to a SIEM, repeat step 1 and confirm the event arrives on the collector. A record present in the console and absent on the collector is a transport or port problem, not an auditing problem.

## Common errors

| Symptom                                                   | Cause                                                                                            | Fix                                                                                                                       |
| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------- |
| The event you are looking for is not in the log           | The date filter excludes it, or it is older than the retention window                            | Widen the period first; if the window has passed, the record is gone — raise retention in **System settings › Retention** |
| A session is live on the asset but missing from the trail | The session was never registered as active, so cleanup routines can close it out of sight        | Look for it under **Historical sessions**; recurring cases are an installation problem, not a filter problem              |
| Commands are missing for a session                        | Command capture covers SSH and Telnet; graphical protocols leave a recording, not a command list | Use the [recording](https://wiki.datadike.com/pam/administration/audit/recordings.md) for RDP, VNC, and web sessions      |
| A command shows as **Reject** but the user says it ran    | The row is the blocked attempt, not an execution                                                 | Confirm against the session recording; blocked commands never reach the target                                            |
| You cannot see another user's records                     | RBAC does not grant audit visibility to your role                                                | Adjust the role — see [Roles](https://wiki.datadike.com/pam/administration/identities/roles.md)                           |
| Nothing arrives at the SIEM                               | Wrong protocol or port, or the collector is unreachable from the nodes                           | Check against 514/UDP, 514/TCP, 6514/TLS and test reachability from every node                                            |

## Field reference

### Login log

| Field                 | What it holds                                                                 |
| --------------------- | ----------------------------------------------------------------------------- |
| Username              | The account that attempted to log in                                          |
| Authentication method | How it authenticated — password, MFA, and so on                               |
| Reason description    | Detail for a failure, for example that the username or password was incorrect |
| Status                | **Success** or **Failure**                                                    |
| Login date            | Date and time of the attempt                                                  |

### Session records

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

### Online users

| Field                 | What it holds                                     |
| --------------------- | ------------------------------------------------- |
| User                  | The connected user                                |
| Authentication method | How they authenticated                            |
| Login date            | When they connected                               |
| Active                | Whether the session is still active               |
| Operation             | **Disconnect** to end that user's console session |

{% hint style="warning" %}
You cannot disconnect yourself from **Online users** — the attempt is refused because it is your own session. The list covers users connected through the web console; sessions on assets are ended from **Session records** or from [live monitoring](https://wiki.datadike.com/pam/administration/sessions/live-monitoring.md).
{% endhint %}

### Password changes

| Field          | What it holds                                                                                 |
| -------------- | --------------------------------------------------------------------------------------------- |
| User           | The account whose password changed                                                            |
| Modifier       | The user or process that changed it — the account itself, an administrator, or a rotation job |
| Remote address | Source address of the change                                                                  |
| Date           | When it happened                                                                              |

### Keylogger

| Field      | What it holds                                                    |
| ---------- | ---------------------------------------------------------------- |
| Command    | The command as typed                                             |
| Risk level | **Accept** (allowed by policy) or **Reject** (blocked by a rule) |
| User       | Who typed it                                                     |
| Assets     | Where it ran                                                     |
| Account    | The credential used                                              |
| Session    | **Go to session**, a link to the originating session             |

An asset tree on the right of the page narrows the list to one asset, which is the fastest way to review everything typed on a single host.

### Transfers

| Field              | What it holds                                          |
| ------------------ | ------------------------------------------------------ |
| ID                 | Unique transfer identifier                             |
| User               | Who transferred the file                               |
| Assets             | Source or destination asset                            |
| Account            | The credential used                                    |
| Operation          | Direction of the transfer — **Download** or **Upload** |
| File name          | Name of the file transferred                           |
| Operation (button) | Retrieves a copy of the transferred file               |

### Job list and Executions

| Field              | What it holds                                                         |
| ------------------ | --------------------------------------------------------------------- |
| Name               | Name of the job                                                       |
| Command            | The command configured to run, for example `win_shell:reboot -s -t 0` |
| Type               | Command, file upload, and so on                                       |
| Periodic execution | Cron expression for the schedule, for example `0 0 * * *`             |
| Interval           | Interval between runs                                                 |
| Creator            | Who or what started an execution                                      |
| Task type          | `adhoc` for a manual run, `upload_file` for an upload                 |
| Finished           | Whether the run completed                                             |
| Was it successful? | Whether the run succeeded                                             |
| Operation          | **View** for the run detail, **Stop** to interrupt a running task     |

## Related pages

* [Session recordings](https://wiki.datadike.com/pam/administration/audit/recordings.md) — the replay behind a session record
* [Reports](https://wiki.datadike.com/pam/administration/audit/reports.md) — repeatable extracts of these same records
* [Command inspection](https://wiki.datadike.com/pam/administration/access/command-filtering.md) — where the **Accept** and **Reject** classification comes from
* [Syslog and SIEM](https://wiki.datadike.com/pam/administration/integrations/syslog-and-siem.md) — forwarding the trail off the appliance
* [Risk score](https://wiki.datadike.com/pam/administration/ueba/risk-score.md) — the behavioural reading of the same events
