X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 6552CD1D10B for ; Fri, 5 Mar 2004 09:52:01 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 46584-05 for ; Fri, 5 Mar 2004 05:51:59 -0400 (AST) Received: from magic.lif.icnet.uk (magic.lif.icnet.uk [143.65.100.6]) by svr1.postgresql.org (Postfix) with ESMTP id 25718D1D104 for ; Fri, 5 Mar 2004 05:51:56 -0400 (AST) Received: from atlantis.ox.icnet.uk (atlantis.ox.icnet.uk [143.65.27.60]) by magic.lif.icnet.uk (8.9.3p2/8.9.3) with ESMTP id JAA02545 for ; Fri, 5 Mar 2004 09:51:57 GMT Received: from nemesis.ox.icnet.uk (mail@nemesis.ox.icnet.uk [143.65.27.59]) by atlantis.ox.icnet.uk (8.12.6/8.12.6) with ESMTP id i259puPS005862 for ; Fri, 5 Mar 2004 09:51:56 GMT Received: from davee by nemesis.ox.icnet.uk with local (Exim 3.36 #1 (Debian)) id 1AzBzo-0003nj-00 for ; Fri, 05 Mar 2004 09:51:56 +0000 Date: Fri, 5 Mar 2004 09:51:56 +0000 From: Dave Ewart To: pgsql-admin@postgresql.org Subject: Re: Database Encryption (now required by law in Italy) Message-ID: <20040305095156.GC13042@nemesis.ox.icnet.uk> Mail-Followup-To: pgsql-admin@postgresql.org References: <0A5B2E3C3A64CA4AB14F76DBCA76DDA44E2DA6@seifur.hnit.is> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0A5B2E3C3A64CA4AB14F76DBCA76DDA44E2DA6@seifur.hnit.is> User-Agent: Mutt/1.5.5.1+davee+cvs20040105i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/30 X-Sequence-Number: 12600 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