Philter
Mountain FogPhilter
Search…
Philter 1.12.0
Introduction
Introduction
What is Philter?
Applicability to PII and PHI
Quick Start
Upgrading Philter
Evaluating Philter's Performance
Filters
Filters
Filter Profiles
Sample Filter Profiles
Configuration
Settings
UI
Dashboard
API
API
SDKs
Advanced Features
Alerts
Consistent Anonymization
Custom NLP Models
Replacements Store
Span Disambiguation
Monitoring and Management
Management
Metrics
Logging
Resources
AWS AMIs
How Tos
How to Use an Apache Reverse Proxy with Philter
How to Use a Signed SSL Certificate with Philter
Solutions
Apache NiFi and Philter
Monitoring Philter in AWS
Managing Philter’s Configuration in an Auto-Scaling Environment
Deploying Philter in a HIPAA Environment
Consistent Anonymization with Redis
Deploying Philter in AWS via a CloudFormation Template
Using AWS Kinesis Firehose Transformations to Filter Sensitive Information from Streaming Text
Using Philter with Microsoft Power Automate (Flow)
Links
Philter
Mountain Fog
Philter on AWS
Philter on Azure
Philter on Google Cloud
Powered By GitBook
Deploying Philter in a HIPAA Environment
Describes how to deploy Philter in a HIPAA environment.
This is not intended to be a comprehensive or legal HIPAA guide so please refer to your HIPAA compliance or security officer prior to deploying and using Philter in a PHI environment.
Third-party products, such as Philter, launched via a cloud platform's marketplace may not be pre-configured for encryption of data at rest. 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
  1. 1.
    Stop the Philter EC2 instance.
  2. 2.
    Make an AMI of the instance.
  3. 3.
    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

The following steps are the same for both Amazon Web Services and Microsoft Azure.
If using Philter via its REST API:
If launched from the Amazon Web Services 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.
  1. 1.
    Log in to the Philter EC2 instance via SSH. (On AWS the username is ec2-user. On Azure the username is centos.)
  2. 2.
    Stop the Philter service: sudo systemctl stop philter.service
  3. 3.
    Edit Philter's settings to utilize an SSL certificate.
  4. 4.
    Start the Philter service: sudo systemctl start philter.service
  5. 5.
    Connect to Philter's API and verify the connection succeeds: curl https://philter:8080/api/status and returns HTTP 200 OK.
If using Philter via it's Apache Kafka consumer:
  1. 1.
    Your Apache Kafka broker(s) must be configured to accept secure connections from clients.
  2. 2.
    Log in to the Philter EC2 instance via SSH. (On AWS the username is ec2-user. On Azure the username is centos.)
  3. 3.
    Stop the Philter service: sudo systemctl stop philter.service
  4. 4.
    Edit Philter's settings to specify the certificate to use to communicate with Apache Kafka.
  5. 5.
    Start the Philter service: sudo systemctl start philter.service
  6. 6.
    Verify Philter is successfully consuming messages from Apache Kafka.
Solutions - Previous
Managing Philter’s Configuration in an Auto-Scaling Environment
Next - Solutions
Consistent Anonymization with Redis
Last modified 2yr ago
Copy link
Contents
Encryption of Data at Rest
Encryption of Data in Motion
Related Links