Re: Programing Question/Authority...

["alan shore" <SHOREA@xxxxxxxx>]

Maybe I was trying to make my point in too simplistic a manner. I agree that if 
a record needs to be updated, then a view should be used. The point I was 
trying to make was that if you have access to the application, you have access 
to the data. The answer is to lock down BOTH the application AND the data. If 
you get acces to the application, you need not neccessarily have access to the 
data.


>>> "John Taylor" <jtaylor@rpg2java.com> 07/27/01 01:30PM >>>
Alan,

I think the approach you advocate --base all security at the object level--
is impractical.  Just because I want Sally to be able to update a customer
record through an application interface, doesn't mean that I want Sally to
have direct access to the Customer Master. There is a world of difference
between the two methods of access.

The only workable solution that I've found is to lock down the database
altogether, and provide application level access through adopted authority.
In those (very few) situations where direct access to a file is required,
it's handled through a view.


John Taylor


----- Original Message -----
From: "alan shore" <SHOREA@dime.com>
To: <RPG400-L@midrange.com>
Sent: Friday, July 27, 2001 10:18
Subject: RE: Programing Question/Authority...


> PLEASE NOTE : No sarcasm is intended, however, I know that sarcasm WILL be
projected from my response to this.
>
> Lets take this from the sublime to the WAY ridiculous.
>
> Somebody requires access to High level Top secret documents, but to obtain
this data "they then have to jump through all sorts of hoops."
>
> So lets make it easier to obtain this data. Oh, did'nt they do that at
some military installation in California just recently.
> Sarcasm switch now turned off.
>
> Implementing a security procedure is NOT easy, and it is (or should be)
ALWAYS  revised. If it is hard for a person to be able to obtain data, then
surely the security is working.
> Letting an application handle the security (even if users only see the
options they need to see) is NOT (this is strictly my opinion) the procedure
to use. If fred Bloggs should never have access to the payroll master file,
then the security should be in place that he is NOT allowed access, even
through the application, thet he may or may not have. If he should have
access to the payroll master file, give him direct access. If not, he falls
into the category of PUBLIC *EXCLUDE.
>
>


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com 
+---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---