| From: | Raphaël Jacquot <sxpert(at)sxpert(dot)org> |
|---|---|
| To: | sanjay sharma <sanksh(at)hotmail(dot)com> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Submission of Feature Request : RFC- for Implementing Transparent Data Encryption in P |
| Date: | 2008-04-17 11:57:44 |
| Message-ID: | 1208433464.30931.29.camel@sxpert.obs.ujf-grenoble.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2008-03-31 at 18:21 +0000, sanjay sharma wrote:
> overkill. Compliance requirement for storing private data arises from
> each organizations own declared privacy policies and statutory bodies
> like privacy commissioners and other privacy watchdogs. These
> standards are not as strict as PCI, HIPPA or Sarnabes-Oxley
>
> Compliance with HIPPA regulation requires not only maintaining all
> records of who created and updated the record but also who accessed
> and viewed records, when and in what context.
you'd be much better served in this case by implementing se-postgresql
with an appropriate policy...
it would allow you to do all that you need and more :-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-04-17 12:30:12 | Re: [COMMITTERS] pgsql: Repair two places where SIGTERM exit could leave shared memory |
| Previous Message | PFC | 2008-04-17 09:20:11 | Re: count(*) performance improvement ideas |