Sign in
Catalog / Hands-on lab

Lab: Record and review a privileged session

A real Monopam and a Linux server, with recording switched off for the whole tenant. Turn it on, grant access through a policy that denies a risky command, run an SSH session and review its recording with a shared note.

Monopam University Pass 45 minIntermediate DE · EN · ES · TR Administrator Security analyst

Version 5 · updated Nov 9, 2026What changed?

Hands-on lab
Sign in to start

Included with University Pass.

What you will learn

  • Find out why sessions are not recorded and turn recording on
  • Control command rules through a Resource Access policy
  • Review a recorded session and leave a shared note

Your lab environment

YOUR LAB SERVERYour browserpamadmin, thendenizMonosignSign-in to MonopamLab userspamadminadministrator, denizoperatorMonopamSettings, policies,PrivilegedCommands,RecordingsMonopam gatewayApplies commandrules, records thesessionlinux-01SSH server with/root/keep.txtRecordingstorageThe lab's ownMinIOSigns inIdentityRecording
Your lab environment: deniz's SSH session to linux-01 passes the Monopam gateway, which applies the command rules and stores the recording

Lab tasks

Each task is checked automatically against the real state of your lab environment.

  1. 1. As pamadmin, turn session recording back on for the tenant
  2. 2. Create a Resource Access policy that gives deniz linux-01 with its root account
  3. 3. Deny the rm command on linux-01 for deniz with a privileged command rule attached to that policy
  4. 4. As deniz, connect to linux-01, try rm /root/keep.txt, run touch /tmp/rec-proof and disconnect
  5. 5. Open the recording and add a shared note about the denied command