- Fixed an issue where when viewing the Cryptographic Assets page for the Discovery Source Vault, the PQ Status was not displayed for assets discovered using the Azure Key Vault plugin.
- Fixed an issue where running "Rescue Tenant" on an upgraded tenant caused the rescued admin user to lose the Keysafe5 admin, Discovery Admin, and Appliance Admin rules.
- Fixed an issue where KeySafe5 did not run correctly after upgrading to 10.5.3.
- Fixed an issue where, after upgrading CSP Compliance Manager, the Certificate Manager policies did not run correctly unless you manually synced the data source.
Fixed an issue where restoring a backup on a different VM would not work without enabling Startup Authentication.
Fixed an issue where if an asset is marked as non-compliant by a scheduled run that is later disabled but not removed, if any new schedule used for daily runs resulted in a compliant status, the previous non-compliant status would persist.
Fixed an issue where after upgrading, previously discovered endpoints were deleted due to an issue with CSP Discovery. The next time you run the plugins, the CSP Compliance Manager webGUI will restore the correct endpoint data.
Fixed an issue where two-factor authentication status was incorrectly mapped from the backend API response to the webGUI, and the webGUI would not display the correct status for logged in users.
Fixed an issue where after upgrading CSP Compliance Manager a data source (vault) would be listed as connected in the CSP Compliance Manager, but listed as disconnected in CSP Vault.
Fixed an issue in CSP Discovery where a successful scan may fail at the end with the error "Failed to process container logs: io: read/write on closed pipe".