Find the right session
Open Sessions or the session tab of a specific node/user. Verify user, node, system login, bastion, time and reason for completion. For a guest connection, there is a link to a temporary grant and a visit. Active panel authorization and SSH session are different entries, leaving the same interface tab is not proof of completion of all user connections.Viewing the terminal recording
Open the record of the selected session. The player supports playback and pause, timeline transition and shortening of long pauses, so it’s convenient to find the moment of error without looking at all the downtime. For an active session, you can watch the incoming output, you can step back through the story and then go back to live, and with a brief viewing cliff, the stream is restored from the last event you received, if access is maintained. Surveillance doesn’t give you control of someone else’s terminal. It’s reading a recorded output with the current rights to write. Once the session is over, the same material is available as a regular story until the shelf life has expired. The recording contains a terminal output, including what the programs have printed on the screen. It is not a structured list of all system changes: some commands may not output the result, and background processes may continue to work after the connection is completed.Viewing rights
Viewing sessions and reading records are separate powers. The auditor does not automatically receive SSH or the ability to run tasks. Project areas and current rights are taken into account when reading a story; long-term access to a node does not guarantee eternal access to its records. Viewing and requesting a record to be uploaded is recorded in the audit, and the fact that the download event is recorded means that it was requested and prepared, rather than confirming that the entire file was received by the client.General audit
Open Audit. Use category, action, and user filters, then navigate through associated nodes and resources. User profiles show events where the user was the performer or receiver; nodes have events of that machine. The log includes account login and protection, import, user changes, roles and grants, SSH trust, connections, record actions and agent policy changes. This is Telepúrte magazine: it is not a substitute for Axottle or Linux audits. Passwords, MFA codes, file contents, and full output of commands are not copied into normal audit events. Open the record to output interactive work, open the task result to automate.An example of an incident
- Select the node and time interval of the problem.
- In the audit, find the issue or change of access and activity during this period.
- In sessions, match the user, system login and time.
- Open the record, find the corresponding moment and conclusion.
- Check the automation tasks and application log on the node.
- Keep the necessary records from being cleared until the investigation is completed.
