QUESTION POSED ON: 12 May 2004
We are currently in the process of reviewing our entire system's security. One of the conundrums we've come across is how to prevent user profiles from gaining "unofficial" access to data (i.e. through a system tool such as DFU or
DBU) while still maintaining "official" access (i.e. production end-user
applications) to the data they need to update.
The way our security is set up, the user profiles belong to groups, and those groups have *CHANGE access to the libraries and the data within them (through private auth or AUTLs). So, from OS/400's perspective, it does not distinguish between the two types of access, and thus permits both.
Is there a way that we can set up our system that would allow us to distinguish between these two types of access, and thus secure them differently?
|