pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dave Ewart <Dave.Ewart@cancer.org.uk>
To: pgsql-admin@postgresql.org
Subject: Re: Database Encryption (now required by law in Italy)
Date: Fri, 5 Mar 2004 09:51:56 +0000
Message-ID: <20040305095156.GC13042@nemesis.ox.icnet.uk> (raw)
In-Reply-To: <0A5B2E3C3A64CA4AB14F76DBCA76DDA44E2DA6@seifur.hnit.is>
References: <0A5B2E3C3A64CA4AB14F76DBCA76DDA44E2DA6@seifur.hnit.is>

On Friday, 05.03.2004 at 09:21 +0000, lnd@hnit.is wrote:

> Is it enough to encrypt some table fields only, i.e. "personnal data"
> personal(social security) number, name-surname and birth data - if one
> can not easily tell whom the data(e.g. bank account) belongs to then
> it may be quite enough? 
>
> Just because "personal" data is quite a loose term: it can be all or
> nearly nothing.

I realise the original poster is from Italy, but in the UK there is a
Data Protection Act which defines personal data.

It says that personal data means "data that relate to a living
individual who can be identified from those data or from those data and
other information in the possession of, or likely to come into the
possession of, the data controller".  This seems like a good definition
to me, although we extend it to also apply to people who have died.

There is an extension which states that "sensitive" personal data is a
subset of personal data where the data is one of several categories,
such as "physical or mental health" (this is most appropriate one of for
us, doing medical research).

I guess there may similar legislation in Italy and elsewhere.

Suggestions:

1. You need to decide which fields in the database should be encrypted.

2. Perhaps keep all 'personal' data in a separate table and control
access to that table more closely with database permissions.
Optionally, encrypt the contents of that table too.

3. Use a loopback-encrypted filesystem.

Dave.
-- 
Dave Ewart
Dave.Ewart@cancer.org.uk
Computing Manager, Epidemiology Unit, Oxford
Cancer Research UK
PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370




view thread (65+ messages)  latest in thread

Message-ID: <20040305095156.GC13042@nemesis.ox.icnet.uk>
Permalink:  ../20040305095156.GC13042@nemesis.ox.icnet.uk/
Also on:    postgresql.org/message-id/20040305095156.GC13042@nemesis.ox.icnet.uk

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: Dave.Ewart@cancer.org.uk
  Subject: Re: Database Encryption (now required by law in Italy)
  In-Reply-To: <20040305095156.GC13042@nemesis.ox.icnet.uk>
  References: <0A5B2E3C3A64CA4AB14F76DBCA76DDA44E2DA6@seifur.hnit.is> <20040305095156.GC13042@nemesis.ox.icnet.uk>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox