Validating Monitoring Data

If required, you can enable validation of the monitoring data received from Windows Clients, which allows you to check that the data integrity in the database has not been altered. Validation can be enabled for the PostgreSQL and MS SQL databases.

Two types of monitoring data validation are available:

• Calculating hash codes for monitoring data: In this case, the hash codes will be calculated for each screen capture and metadata record received from Windows Clients.

• Signing monitoring data with a certificate: In this case, each screen capture and metadata record received from Windows Clients will be signed with a trusted certificate.

NOTE: If both types of validation are enabled, only the “Signing monitoring data with a certificate” validation type will be used.

NOTE: For SaaS deployments, please contact your Syteca vendor or the Syteca Support team to enable this feature in your environment.

After validation of the monitoring data is enabled or the validation type is changed, all previously recorded sessions of Windows Clients will be considered to be invalid.

When validation of the monitoring data is enabled, the integrity of the monitoring data within a Windows Client session is checked when the session is opened using the Session Player. If any screen captures or metadata records have been deleted or modified, the warning message “Session data is not valid!” will be displayed in the Session Player.

NOTE: When validation of the monitoring data is enabled, CPU usage will increase while viewing the Client sessions in the Session Player.

NOTE: When enabling validation of the monitoring data for existing sessions that have not been viewed before, screen captures will not be shown.