This guide assumes that your Virtru Private Keystore (VPK) for Google Workspace is up and running. Follow these steps if you have recently deployed VPK, upgraded your TLS/SSL certificate, or added additional servers.
Initial System and Certificate Check
Verify Server Status
Begin by checking the status of your VPK server to ensure it is operational:
Validate Your SSL/TLS Certificate
Confirm that your SSL/TLS certificate is properly installed and valid:
- Run the following command to check the certificate details:
openssl s_client -connect csesrv.yourdomain.com:443 -servername csesrv.yourdomain.com
- Verify the certificate chain to ensure it is complete and correctly installed.
Encryption and Decryption Google Workspace Document Test
Send an Encrypted Content
To further validate encryption functionality, test Google Workspace document encryption:
- Log into Google Drive.
- Click New and navigate to Docs, Sheets, or Slides.
- Select Blank encrypted document.
- Share the document with someone in your organization.
- Ensure that the recipient can access and edit the document.
Verify Decryption
- Have the other user within the organization open the encrypted content.
- Ensure that you and the recipient can successfully decrypt the message.
- If decryption is successful, your VPK is functioning correctly.
Service Disruption Test
If the encrypted document is accessible, proceed with the following steps to further test system resilience:
Access the Server
- SSH into your VPK server:
ssh user@your-vpk-server
- Identify the running container:
docker ps
Stop the Container
- Obtain the container ID from the
docker ps
command output. - Stop the container using:
docker stop <container_ID>
Verify System Behavior
During this time:
- FQDN Access: Attempt to access https://csesrv.yourdomain.com/status. It should be unreachable.
- Google Workspace Document Access: Refresh the content or close and reopen. Attempt to access the encrypted document in Drive. Access should be denied.
- Confirm that both you and the other person are unable to decrypt the content.
Restart the Container
- Restart the container using:
docker start <container_ID>
- Reattempt email decryption and access the encrypted content to ensure that the VPK is functioning again.
Troubleshooting
If email or document decryption fails at any point, follow these troubleshooting steps:
Verify SSL/TLS Certificate Chain
- Ensure that your certificate is correctly installed and the chain is complete.
- Run:
openssl s_client -connect csesrv.yourdomain.com:443 -servername csesrv.yourdomain.com -showcerts
By following this process, you can verify that your VPK setup is functioning correctly and securely.