Deploying Philter in a HIPAA Environment
The steps below outline how to configure a Philter deployment for encryption of data at rest and in motion.
Encryption of Data at Rest
Amazon Web Services
Stop the Philter EC2 instance.
Make an AMI of the instance.
Make an encrypted copy of the Philter AMI.
The created AMI is encrypted. EC2 instances launched from the AMI will utilize an encrypted EBS volume and all snapshots will be encrypted. Refer to the AWS documentation Creating an Amazon EBS-Backed Linux AMI for assistance.
Encryption of Data in Motion
Amazon Web Services
If launched from the Amazon Web Services, Google Cloud, or Microsoft Azure marketplace Philter's REST API will be pre-configured with a self-signed certificate. It is recommended you replace the self-signed certificate with a certificate from a trusted certificate authority.
Log in to the Philter EC2 instance via SSH. (On AWS the username is
ec2-user. On Azure the username iscentos.)Stop the Philter service:
sudo systemctl stop philter.serviceEdit Philter's settings to utilize an SSL certificate.
Start the Philter service:
sudo systemctl start philter.serviceConnect to Philter's API and verify the connection succeeds:
curl https://philter:8080/api/statusand returnsHTTP 200 OK.