FAQs-Supporting User Master Key
- How does AppViewX connect with the HSM?
The cloud connector facilitates all communication and interactions between AppViewX and the User's resources, which includes the Hardware Security Module (HSM).
- Is the data that is sent to the Cloud Connector encrypted during
transit?
Yes. The communication between AppViewX and the AppViewX cloud connector is through a TLS-encrypted channel.
- What is the impact after enabling AppViewX Master Key Encryption if the
virtual machine or server hosting the AppViewX Cloud Connector experience
health issues?
The AppViewX cloud connector is required for any communication with the HSM. If there are issues between AppViewX and the AppViewX cloud connector, it can result in a service disruption. To ensure high availability, it is recommended to deploy multiple cloud connectors across various data centers and also ensure that all deployed cloud connectors can interact with the HSM.
- Can you explain the reason for not rotating the AppViewX Master Key when the
User opts to utilize a User Master
Key?
AppViewX uses envelope encryption to enhance the security of confidential data. This technique involves encrypting the AppViewX Master Key with the User's Master Key, thus allowing the User to retain control over their data. To ensure the security of the AppViewX Master Key, AppViewX never stores it in plain text format and instead uses AWS KMS to encrypt it. When the user opts to encrypt the AppViewX Master Key, all existing keys of that tenant in the KMS are discarded, rendering any previous data backups useless. The tight security measures in place eliminate the need for rotating the AppViewX Master Key, saving the cost and effort of re-encrypting all secure materials.
- Can you provide an overview of the actions that an MFA-disabled local user
can carry out if the User Master Key is removed from
the HSM?
In the event that the Master Key is removed, AppViewX will be in a near-read-only state, where only non-sensitive data, such as audit logs, can be viewed. Any actions requiring access to sensitive information will be disabled, even for a local user without multi-factor authentication. This added layer of security ensures the protection of confidential data and reinforces AppViewX's commitment to data privacy and security.
- What are the consequences if the password for the HSM is modified and not
updated within AppViewX?
AppViewX conducts regular health checks on the HSM where the User Master Key is stored. In the event that the HSM is deemed unhealthy after three consecutive failures, AppViewX will flush the plain text AppViewX MEK from its cache. This measure is necessary to protect the confidentiality of the data, but it may result in a temporary service disruption.
- Are there any notifications to alert us in the event that the HSM is not
functioning optimally or if the Master Key is removed?
When enabling the AppViewX MEK encryption, users can set up notifications for the health of the Hardware Security Module (HSM). By configuring a list of email addresses, users can stay informed about the status of the HSM.
- Since there is a dependency on the AWS KMS, is the service highly
available?
Yes AWS KMS is highly available within an AWS region.
- After enabling AppViewX Master Key encryption by User Master Key do we have
the option to revert back?
No. After enabling AppViewX MEK encryption there is no option to revert back to using the AWS KMS. We can switch the HSM that stores the User's Master Key.
- Does AppViewX support rotating the User Master Key stored in the
HSM?
Currently, we do not support the rotation of the User Master Key.
- Does AppViewX rotate the Master Key stored in the AWS KMS?
Yes, the Master Key stored in the AWS KMS is rotated every 90 days.
- Can you provide details regarding the algorithm and size of the AppViewX
Master Key?
Algorithm: AES
Size: 256-Bit Key
