data encryption

Does anyone have experience using the feature in PG 8.4 (maybe earlier
versions too??) to store specific columns in an encrypted format? We are
gathering sensitive data for medical studies and want to use Postgresql,
however, we need to insure that the data is secure to satisfy federal
HIPAA regulations. One way to do that would be to store some or all of i=
t
in an encrypted format.

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
lcarson [ Di, 24 November 2009 19:49 ] [ ID #2023825 ]

Re: data encryption

On Tue, Nov 24, 2009 at 10:49 AM, <lcarson [at] ucsd.edu> wrote:
> Does anyone have experience using the feature in PG 8.4 (maybe earlier
> versions too??) to store specific columns in an encrypted format? =A0We a=
re
> gathering sensitive data for medical studies and want to use Postgresql,
> however, we need to insure that the data is secure to satisfy federal
> HIPAA regulations. =A0One way to do that would be to store some or all of=
it
> in an encrypted format.

Here is a presentation that give a high level view of how to secure the dat=
a.

http://momjian.us/main/writings/pgsql/securing.pdf


--
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Richard Broersma [ Di, 24 November 2009 20:51 ] [ ID #2023826 ]

Re: data encryption

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB0A508291BEE2E0F1E0EFCB5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

lcarson [at] ucsd.edu wrote:
> Does anyone have experience using the feature in PG 8.4 (maybe earlier
> versions too??) to store specific columns in an encrypted format? We a=
re
> gathering sensitive data for medical studies and want to use Postgresql=
,
> however, we need to insure that the data is secure to satisfy federal
> HIPAA regulations. One way to do that would be to store some or all of=
it
> in an encrypted format.

See:
http://www.postgresql.org/docs/8.4/interactive/pgcrypto.html

But the tricky part is the key management more so than the encryption.

Joe


--------------enigB0A508291BEE2E0F1E0EFCB5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iQIcBAEBCAAGBQJLDDoxAAoJEDfy90M199hlUaAP/Ana12ikcefThO5bbBxX 70xX
epxU374UZtcxErTnL6MtTjoC3r/gyOxzMxasWcSdShzO0Ok3Qek9vuxIxJ3K T4Sf
dBTWfM8yH9+NpQbj44zuBrFXCypDlIHNH2Og5LJKS2jFMQ4KznmaW2soBVhK 6GtF
MUIraYmqUfj3hiWxZKpxraVUDufCnD4Z8HmHM/Po9//uckACFuhkaMjugndj obJX
PRCvEGA2SlvtD6O0IHBCtygqbDXKe/BnTwM5UmcAlZqBKPjvHJgyqxcNVqBX eczT
WqvL9J7uEi2FPIXwju9qGqEDIyeEYWMUkUfpGvHkDI0+zFsT2f2WxsTlGs0/ W4cP
RAfFvx8tgTMS4r7IepyYb2wGgEOj0kQpvly3cqeIoIZ4RcKD++Z9wlmQC63Z kcWQ
4Mx7sl0Cf5LUY6rWtZTj2M+0zL9ri8FcmGA2/aXdWocS08+TFiYS4sIxpnUi KdRa
L+LA5oe9styF0fbxhCdFan3wtxn7uQCN/2Ok8LBqR7k0mVNZ+vhe4+o/+vHq rJZW
QGwr4qBTD1ISTIWnvS4ZSYvNtVg3BCYrIWVk1M32yiw5oO4TpMgWpOMeqEuB Bdij
HWeh23laFnTDE+wCfhVvnhTqrJEJFja1Fg6zyPJrxveuRezYSGrR+VM2h6xk ziy0
PbwcRYsurB/L0yGcPFwj
=TDWA
-----END PGP SIGNATURE-----

--------------enigB0A508291BEE2E0F1E0EFCB5--
Joe Conway [ Di, 24 November 2009 20:55 ] [ ID #2023827 ]
Datenbanken » gmane.comp.db.postgresql.admin » data encryption

Vorheriges Thema: WAL file compatibility
Nächstes Thema: Recovering (slowly!) from database corruption