Dan Heath
1f6e000357
* docs: Reorg session recording operations * docs: Improve linking and meta content * docs: Add redirect for old "Manage" topic * docs: Updates to data store validation topic * docs: Fix link name in index topic
24 lines
1.6 KiB
Plaintext
24 lines
1.6 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Recorded sessions operations
|
|
description: |-
|
|
How to work with Boundary's recorded sessions
|
|
---
|
|
|
|
# Recorded sessions operations
|
|
|
|
Boundary provides [auditing](/boundary/docs/concepts/auditing) capabilities via [session recording](/boundary/docs/configuration/session-recording).
|
|
In Boundary, a session represents a set of connections between a user and a host from a target.
|
|
The session begins when an authorized user requests access to a target, and it ends when that access is terminated.
|
|
When you enable session recording on a target, any user session that connects to the target is automatically recorded.
|
|
An administrator can later view the recordings to investigate security issues, review system activity, or perform regular assessments of security policies and procedures.
|
|
|
|
Recorded sessions are stored in an external storage bucket that you create.
|
|
Storing session recordings in a system external to Boundary means those recordings can be accessed, modified, deleted, and even restored independently of Boundary.
|
|
You can view any sessions that Boundary recorded in your storage provider or via the CLI.
|
|
|
|
For more information about working with recorded sessions, refer to the following topics:
|
|
|
|
- [Find and view recorded sessions](/boundary/docs/operations/session-recordings/manage-recorded-sessions)
|
|
- [Validate the integrity of session recordings](/boundary/docs/operations/session-recordings/validate-session-recordings)
|
|
- [How Boundary validates data integrity in the external data store](/boundary/docs/operations/session-recordings/validate-data-store) |