Session History
Review, filter, and export audited sessions with full access context
The Session History tab provides a centralized view of all audited sessions across your integrations. You can use it to review session activity, filter results, and download the session metadata report.

This tab displays session metadata for each audited session, including:
User (identity)
Resource
Protocol
Session start / end time
Access Request ID
Permissions
Approvers
Access flow
Number of events
Risk Score
Each session in the Session History tab has a status that reflects its audit capture and upload state. The status can have one of the following values.
Active
The user is connected to the resource, and the session is being recorded.
Pending
The session has ended, and session data is being uploaded to the configured S3 bucket.
Degraded
The session may have incomplete data. This can occur if the upload to S3 did not complete successfully or if the connector could not capture all session data.
Filter the session history
Filters operate on the metadata stored in Apono. Multiple filters can be combined. Filtering the session history can be used to generate a compliance evidence report.

Follow these steps to filter the session list:
On the Session History tab, set the date range to refine the list of sessions. By default, all sessions are listed.
Click a filter dropdown menu.
(Optional) In the Search field, enter a value to filter the options.
Select one or more options. The list of sessions will be filtered.
Click the top or outside of the dropdown menu to close it. The filter turns blue and shows a summary.
(Optional) Repeat steps 2-5 to add more criteria to filter the Session History list.
Download a session report
Admins can download a compliance evidence report for a filtered set of sessions.
Follow these steps to generate and download the report:
Click Download. The Download Report pop-up window appears.
Enter a File name.
(Optional) Select the report format. CSV is the default format.
CSV: (Default) Best for internal analysis, integrations, or bulk data processing
JSON: Best for programmatic processing or when preserving full data structure (nested fields and metadata)
Click Download. When the report has been generated, a notification will appear.
The report includes session metadata enriched with Apono context, such as human user identity, approver, and access flow.
Last updated
Was this helpful?
