Re: AS400 security WAS: Package Vendor that changes IBM command Defa ults.

>Dean,
>  You're right; there are fewer posts on security.  In my prior job, I was
>security/database/analyst/help desk/programmer/floor washer.  I had to
>understand security as part of what I did.  Here, we have a person who's
>dedicated to security concerns, and I rarely get asked security questions
>any more.  I wonder if specialisation isn't one reason for the lack of
>security related posts?
>Buck Calabro

I think that is true for larger shops that have implemented tight security
measures. I don't think it is true for smaller shops. Then security is more
often implented through menus that restrict access by restricting options
that can be performed. I think a better description is that security is
enforced by what people don't know how to do. For example, a user has
ClientAccess and Access. The assumption is that the data is safe
because the users won't figure out how to configure ODBC to get to
the AS/400 data. I'm not saying that I think it's right, that is just my
observations from the trenches. I have found object security to be the
exception, not the rule even though every company that I've been in the
last 10+ years has had PC's connected via ClientAccess, WinAPPC or
Rumba.

Joe Teff


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