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.
Brgds, Laimis > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Silvana Di Martino > Sent: 5. mars 2004 09:54 > To: [EMAIL PROTECTED] > Subject: [ADMIN] Database Encryption (now required by law in Italy) > > > The new italian law about personal data protection (aka > "privacy") requires > the use of cryptography _both_ for protecting the network > traffic _and_ for > protecting the (personal) data stored on the hard disk. > > While I can see how to protect a PGSQL connection using SSH > tunneling or a > VPN, I cannot see any way to encrypt a PGSQL database stored > on a hard disk, > put aside the possibility to encrypt the hosting file system > with LoopAES. > > Is there any (native/third party) tool for encrypting a PGSQL > database on the > disk? Is there any PGSQL option for encrypting data on the fly? > > Many thanks in advance for your attention. > > NOTE: the italian law on privacy ("Decreto Legge 196/03", > Dicembre 2003) is > available on the net: > http://www.garanteprivacy.it http://www.interlex.it Of course, just in italian... ----------------------------------------- Alessandro Bottoni and Silvana Di Martino [EMAIL PROTECTED] [EMAIL PROTECTED] ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
