Re: Censoring SQL access -- ideas? -- MIDRANGE-L

Subject: Re: Censoring SQL access -- ideas?
From: rob@xxxxxxxxx
Date: Wed, 16 Mar 2011 08:27:26 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

My belief is that the read triggers are an "after" thing. Instead of
valet asking for id before they turn over your car it's more like "hey, I
just gave the wrong guy this car". I suspect you do not want that.

Exit points may be the way to go.

Another thought is, instead of playing whack a mole with ways people can
access the data, you could just secure out all people from all data. Then
they could only access data from your stored procedures.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.