Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 45. Configuring session recording by using the CLI

Configure user terminal session recordings using the System Security Services Daemon (SSSD) to audit and monitor user activity. Manage and play back recorded sessions using the tlog command-line utility.

45.1. Session recording overview and components
Copiar enlace

Session recording captures and saves a user’s terminal activity. This provides a detailed, unchangeable record of all commands, output, and error messages, which you can use for auditing, troubleshooting, and investigating a security incident.

SSSD enforces the recording policies you define, and the tlog utility handles the actual recording and playback.

Components of the session recording

  • tlog utility

    The tlog utility provides tools for recording and playing back terminal I/O. tlog-rec-session functions as an intermediary login shell and captures all data between the user’s terminal and shell. All tlog recordings are in JSON format. You can play back recorded sessions using tlog-play. Note that by default, terminal input recording is disabled for security reasons. For detailed configuration options, see the /etc/tlog/tlog-rec-session.conf file and the tlog-rec-session.conf(5) man page on your system.

  • SSSD

    SSSD provides a set of daemons that manage access to remote directories and authentication mechanisms. When you configure session recording, SSSD overlays the user’s default shell with the tlog-rec-session program.

Limitations of session recording
  • You can configure session recording for the root user, but the root user has the privileges to disable or bypass the recording process, which makes the session recording unreliable for auditing purposes.
  • Terminal sessions in a GNOME graphical session are not recorded. This is because all terminals within a graphical session share a single audit session ID, which prevents tlog from distinguishing between them and capturing recordings correctly.

  • A logging loop can occur when viewing the journal. When a recorded user views the system journal or /var/log/messages, it generates new logs, which are then recorded and displayed, causing a loop of flooded output.

    To prevent the logging loop, view the journal in real time and filter out the log entries which create the loop: 

    journalctl -f | grep -v 'tlog-rec-session'

    You can also configure tlog to limit the output. For details, see tlog-rec-session.conf man pages.

  • You must configure session recording on the target host for remote execution. For example, if you want to record a user’s session when they use ssh to connect to a remote system, configure the recording on the remote system they connect to.
  • All recordings are lost on reboot if systemd-journald service uses its default configuration to store the journal in-memory.

Enable session recording through SSSD in Identity Management (IdM) to capture terminal activity for specific users or groups. Session recording improves security auditing and helps investigate user activity.

When you configure session recording, you use SSSD to define which users or groups to record by setting the scope option to one of the following values:

  • none to record no sessions
  • some to record only specified users and groups
  • all to record all users

Prerequisites

  • Commands that start with the # command prompt require administrative privileges provided by sudo or root user access. For information on how to configure sudo access, see Enabling unprivileged users to run certain commands.
  • You are using SSSD for authentication.

Procedure

  1. Install the tlog package: 

    # dnf install tlog

  2. Open the sssd-session-recording.conf configuration file: 

    # vi /etc/sssd/conf.d/sssd-session-recording.conf

  3. Specify the scope of session recording and the users and groups to record. For example: 

    [session_recording]
scope = some
users = <user_name_1>, <user_name_2>
groups = <group_name>
exclude_users = <user_name_to_exclude>
exclude_groups = <group_name_to_exclude>

    For more details, see the sssd-session-recording(5) man page on your system.

  4. To enable the SSSD profile, run the following command: 

    # authselect select sssd with-tlog

  5. Restart SSSD to load the configuration changes: 

    # systemctl restart sssd

45.3. Playing back session recordings
Copiar enlace

Review terminal session recordings using the tlog-play utility or the web console to audit user activities and investigate security incidents. Session recordings help ensure compliance and identify unauthorized access attempts.

The system journal stores session recordings. By default, it saves them in-memory, so you lose recordings on reboot unless you configure persistent storage.

You can play back recordings directly from the system journal by using the tlog-play utility. Alternatively, you can install the cockpit-session-recording package to manage and play back recordings on the RHEL web console. .Prerequisites * Terminal sessions have been recorded.

Procedure

  1. Optional: List recorded sessions: 

    $ journalctl COMM=tlog-rec-session

  2. Play back a specific session: 

    # tlog-play --reader=journal --journal-id=<recorded_session_id>

    For more advanced options, such as changing playback speed or fast-forwarding, see the tlog-play man page on your system.

Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2026 Red HatVolver arriba