pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Heather Johnson <hjohnson@nypost.com>
Cc: Michael Fuhr <mike@fuhr.org>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] How to Prevent Certain Kinds of Joins?
Date: Tue, 22 Feb 2005 14:51:00 -0600
Message-ID: <1109105459.30529.119.camel@state.g2switchworks.com> (raw)
In-Reply-To: <421B9674.4060807@nypost.com>
References: <421B8D2D.6050800@nypost.com>
	<20050222200915.GA71591@winnie.fuhr.org>
	<421B9674.4060807@nypost.com>

On Tue, 2005-02-22 at 14:30, Heather Johnson wrote:
> One of the tables contains personally identifiable information (PII) 
> (e.g., email, first and last name, etc.). The other contains "click 
> stream" data (information about where on our website users have gone). 
> In order to be sensitive to users privacy, we don't want to ever (even 
> accidentally) run queries that would combine PII and click stream data. 
> So we're looking for ways to put "walls" up against combining the data. 
> We understand that anyone with ample access to the database can 
> deliberately combine the data if they chose to do so in blatent 
> violation of our policies. But we want to set something up that would 
> put an obstacle or two in the path of anyone who might accidentally run 
> such a query.
> 
> The ideas about setting up views might work. I guess we'd just have to 
> change the permissions of users who have access to the db so that they 
> can only use the views and not query the tables directly.

Why not change the keys that currently connect them to something
different (i.e. random noise) and make a NEW table that could join them
with those random keys that is restriced access wise to only the chosen
few.

Or do you need to actually ever re-reference the two datasets?  If not,
then just lose the connecting data when you insert the rows.



view thread (7+ messages)  latest in thread

Message-ID: <1109105459.30529.119.camel@state.g2switchworks.com>
Permalink:  ../1109105459.30529.119.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1109105459.30529.119.camel@state.g2switchworks.com

 · 

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: smarlowe@g2switchworks.com, hjohnson@nypost.com, mike@fuhr.org, pgsql-general@postgresql.org
  Subject: Re: [GENERAL] How to Prevent Certain Kinds of Joins?
  In-Reply-To: <1109105459.30529.119.camel@state.g2switchworks.com>
  References: <421B8D2D.6050800@nypost.com> <20050222200915.GA71591@winnie.fuhr.org> <421B9674.4060807@nypost.com> <1109105459.30529.119.camel@state.g2switchworks.com>

* 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