Viewing Audit Logs for Encryption Operations
The AppViewX audit logs provide a comprehensive view of system activity, allowing users
to track and monitor various events. Whenever the tenant administrator enables the
encryption of the AppViewX Master Key, all subsequent operations are also recorded in
the logs.
The following table lists the log events recorded in the context of the
AppViewX Master Key Encryption:
Note: For instructions on viewing and reading the audit
logs, click here.
| Action | Log Message |
|---|---|
| Tenant Admin initiates encryption of AppViewX Master Key. | User:<User Name> initiated to enable AppViewX Master Key encryption with HSM:<HSM Name> |
| AppViewX Master Key encryption is successful | HSM:<HSM Name> is successfully configured by user:<User Name> to encrypt sensitive data. |
| AppViewX Master Key encryption has failed | HSM:<HSM Name> configuration to encrypt sensitive data failed due to <reason>. |
| AppViewX retrieved the plaintext AppViewX MEK successfully. | Connected with HSM:<HSM Name> for decrypting AppViewX MEK and it is a success. |
| AppViewX failed to retrieve the plaintext AppViewX MEK. | Connected with HSM:<HSM Name> for decrypting AppViewX MEK and it failed. |
| KMS Key created during onboarding is scheduled for deletion after enabling AppViewX MEK encryption. | KMS Key will be deleted within seven days as AppViewX Master Key encryption through HSM is enabled. |
| Scheduled health check of HSM is successful. | Scheduled validation of Master Key with HSM:<HSM Name> is successful. |
| Scheduled health check of HSM failed. | Scheduled validation of Master Key with HSM:<HSM Name> is failed due to <reason>. |
| Scheduled health check of the HSM failed due to removal of the User's Master Key. | Scheduled validation of Master Key with HSM:<HSM Name> is failed because MEK is not available. So, AppViewX MEK is flushed from memory. |
| Scheduled health check of the HSM failed due to three continuous failures. | Scheduled validation of Master Key with HSM:<HSM Name> is failed continuously for the third time. So, AppViewX MEK is flushed from memory. |
| The user initiated a health check from the GUI and it succeeded. | User:<User Name> initiated validation of Master Key with HSM:<HSM Name> and it is a success. |
| The user initiated a health check from the GUI and it failed. | User:<User Name> initiated validation of Master Key with HSM:<HSM Name> and it failed due to <reason>. |
| The user initiated a health check from the GUI and it failed due to removal of the User's Master Key. | User:<User Name> initiated validation of Master Key with HSM:<HSM Name> and it is failed because MEK not available. So, AppViewX MEK is flushed from memory. |
