Privileged Session Recording20 minutes to read
Organizations depend on privileged accounts to manage critical resources, perform administrative tasks, and access sensitive systems, but this elevated access also introduces significant risks. Additionally, they often rely on web-based applications and services for critical operations. Unmonitored privileged sessions can result in unauthorized actions and security breaches. Additionally, many regulatory frameworks require proactive monitoring and auditing of privileged access to ensure compliance. In the event of security breaches, the absence of detailed session logs hampers effective investigation and remediation. To address these issues, PAM360 offers the Privileged Session Recording feature, enabling organizations to view, record, and monitor user activities on privileged resources and sensitive web applications/services accessed from PAM360 via remote sessions. This feature ensures accountability and enhances security by maintaining a detailed audit trail of all interactions. Recorded sessions are stored securely and can be reviewed later for compliance, identifying potential security risks. By providing a clear, auditable trail of privileged actions, the privileged session recording helps organizations mitigate security risks and meet compliance requirements efficiently. This help document covers the following topics in detail:
1. How Secure is Session Recording?PAM360 ensures the security of session recording by employing an advanced, browser-based remote login mechanism, which allows users to initiate secure, reliable, and fully emulated Windows RDP, SSH, Telnet, and website sessions directly from any HTML5-compatible browser. With a single click, users can establish privileged sessions without requiring additional plug-ins or agent software, reducing dependency on external components that could introduce vulnerabilities. All remote connections are tunneled through the PAM360 server, eliminating the need for direct connectivity between the user’s device and the remote host. This architecture enhances security by ensuring that privileged credentials, such as passwords, are never exposed at the browser level. By isolating user access from direct host connections, PAM360 significantly reduces the attack surface while maintaining reliable session performance. PAM360 comes bundled with RDP, SSH, and Telnet session gateways. These gateways enable users to initiate remote terminal sessions directly within their browser, eliminating the need to install additional software on endpoints. The only prerequisite is an HTML5-compatible browser, such as Internet Explorer 9 or later, Firefox 3.5 or later, Safari 4 or later, or Chrome. 2. Configuring Privileged Session RecordingImportant Notes: The recordings will be stored by default in the directory path <PAM360_Installation_Folder\PAM360\recorded_files>. This external location to store recordings can be changed at any time from the Session Configuration window. To access the session configuration window, navigate to Admin >> Connections >> Session Configuration. Notes:
Caution: When a user launches a website or an HTTPS Gateway connection to a configured URL, they must select the appropriate session tab in the session consent window to record the connection. If the user selects the 'Entire Screen' option, the recording will capture not only the configured URL launched from PAM360 but the entire screen that may include personal information. Privileged session recording in PAM360 can be configured at two different levels:
2.1 Configuring Session Recording for Specific ResourcesAdministrators can enable session recording for selected resources or accounts that require closer monitoring. It is ideal for tracking privileged actions on critical systems, sensitive databases, or high-risk applications. By enabling session recording at the resource level, organizations can maintain precise control over what activities are captured, ensuring that only essential sessions are monitored. This granular approach minimizes unnecessary data collection while aligning with compliance and security policies. Follow these steps to configure privileged session recording for specific resources:
2.2 Configuring Session Recording GloballyPAM360 allows administrators to configure session recording settings globally to ensure uniform oversight of RDP, VNC, web, HTTPS gateway, SSH, Telnet, and SQL sessions. These settings can be customized to suit organizational needs, providing flexibility, enhanced security, and compliance with regulatory requirements. Follow these steps to configure privileged session recording globally:
Note: The Record website sessions and Record HTTPS gateway sessions checkboxes are available only from PAM360 builds 7400 and above. Only the website and HTTPS gateway connections launched to configured URLs with autofill and auto logon functions will be recorded if the Record Configured Resource URL checkbox is not enabled. For a more granular level configuration, configure session recording at the resource level while adding the resource or editing the resource. Note: For MSP, you should apply the above settings for each client ORG account individually. 3. Viewing Recorded SessionsYou can view the recorded privileged sessions from the Audit tab. To access the session recordings: (Procedure Applicable from Builds 7400 and Above)
4. Splitting Recorded SessionsPAM360 offers a robust provision to split recorded privileged sessions into several small files and encrypt them individually. This option applies to session recording files larger than 10 MB in size. By default, PAM360 encrypts all privileged session recordings in your local storage. However, for lengthy sessions resulting in large file sizes, there is a risk of encryption failure during storage. To mitigate this, PAM360 automatically splits the recordings into smaller segments, each not exceeding 10 MB, and ensures that every segment is securely encrypted. Despite being stored as multiple encrypted files, these recordings are merged seamlessly during playback, appearing as a single continuous file. This approach not only guarantees successful encryption but also optimizes playback performance, eliminating buffering delays and ensuring a smooth user experience. For instance, if a session recording generates a file of 25 MB, PAM360 will split it into three segments: two of 10 MB each and one of 5 MB. By default, the session splitting feature is disabled in PAM360, meaning all session recordings are stored as a single file regardless of size. Follow the steps outlined in this document to enable session splitting and take advantage of this feature. Enabling this option ensures efficient encryption and optimized playback for large recordings. Notes:
5. Shadowing Active Privileged SessionsEffective oversight of privileged sessions is crucial to maintaining the security and integrity of IT resources. PAM360 addresses this need with Session Shadowing or Real-time Monitoring, empowering administrators to oversee active sessions on highly sensitive resources. This feature ensures accountability by enabling administrators to monitor user activities as they happen and allows them to intervene when necessary. Whether to mitigate potential security risks, terminate suspicious activities, or provide real-time assistance during troubleshooting, PAM360’s session shadowing offers a seamless way to maintain control and ensure compliance. With this capability, organizations can strengthen their security posture and enhance operational efficiency in managing privileged access. To monitor an active privileged session:
Note: PAM360 does not support the Session Shadowing feature for active website sessions. 6. Deleting Recorded SessionsDeleting a privileged session recording allows administrators to manage storage space and ensure compliance with data retention policies. This feature lets you permanently remove specific session recordings that are no longer needed, ensuring efficient management of recorded data while maintaining system security. To delete a privileged session recording,
Note: Deleting a session recording from the PAM360 database requires approval from at least one other administrator in your environment. Therefore, two administrators are required to delete a recorded session. Note: In scenario 2, if a deletion request is approved by the administrator, but the process is pending due to device unavailability, PAM360 will temporarily restrict access to the session recordings. During this time, the recordings cannot be viewed, even by administrators, until the recording is deleted. 7. Configuring FFmpeg for Session RecordingFollow these steps to configure FFmpeg in your environment:
Note: Ensure the paths are accurately defined to avoid configuration errors. | |