Re: PostgresSQL and HIPAA compliance

From: "Mike Sofen" <msofen(at)runbox(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Re: PostgresSQL and HIPAA compliance
Date: 2016-06-17 18:11:16
Message-ID: 052301d1c8c3$a5868710$f0939530$@runbox.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

-----Original Message-----
From: Alex John
Sent: Friday, June 17, 2016 3:04 AM
To: pgsql-general(at)postgresql(dot)org
Subject: [GENERAL] PostgresSQL and HIPAA compliance

Hello, I have a few questions regarding the use of PostgreSQL and HIPAA
compliance. I work for a company that plans on storing protected health
information (PHI) on our servers. We have looked at various solutions for
doing so, and RDS is a prime candidate except for the fact that they have
explicitly stated that the Postgres engine is *not* HIPAA compliant.

Users on the IRC channel generally say that the guidelines are more catered
towards building better firewalls and a sane access policy, but I would like
to know if there is anything within the implementation of Postgres itself
that violates said compliance.

If anyone works at a similar company and utilizes postgresql to store PHI,
please let me know.

Thank you,
Alex

---------------------------------------------------------------------

HIPAA compliance does not specify (ever) the technical solution to meet the
requirements, so ANY datastore that can be properly managed within the
context of HIPAA compliance is legal and allowed. Ignore IRCs and search on
securing PHI on relational databases, you'll find lots of details around
data access roles, documentation, processes, data obfuscation, etc.

Mike

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2016-06-17 18:17:51 Re: Regression in query optimizer when upgrading from 9.4.5 to 9.5.2?
Previous Message Paul Jungwirth 2016-06-17 18:09:28 Re: PostgresSQL and HIPAA compliance