RE: Documenting / Managing iSeries security

Rob,

Don't quite understand where you are coming from.  Does every application
have it's own library?  Do you have one library for AP, one for AR, ect?

What do Betty, Sam, Peter, and Julie do?

As I understand it, the idea is a group profiles groups users of similar
needs.  So my users doing receiving are all in one group, my accounting
people are all in another group.  I even stick users by themselves into a
group.  Why? Simple really,  if I ever need to add a user, or the user is
replaced then it's just a matter of copying a profile.  Since the authority
to the objects are given to the group via the authorization list, I don't
need to update the authorization lists for the new user.

An example from my own setup:

I have the following group profiles:
GRPACEMPLY      Accounting Dept--full access    
GRPACINTRN      Accounting Dept--limited access for interns 
GRPPUEMPLY      Purchasing Dept--full access    

And here are the authorization lists:
ACLIMIT         Accounting Limited Access    
                        GRPACEMPLY      *USE     
                        GRPACINTRN      *USE     
                        *PUBLIC         *EXCLUDE 
ACRESTRICT      Accounting Restricted Access 
                        GRPACEMPLY      *USE     
                        *PUBLIC         *EXCLUDE 
VENDMAINT       Vendor Maintenance Access 
                        GRPACEMPLY      *USE      
                        GRPPUEMPLY      *USE      
                        *PUBLIC         *EXCLUDE  


Charles

   


> -----Original Message-----
> From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
> Sent: Thursday, May 27, 2004 1:24 PM
> To: Security Administration on the AS400 / iSeries
> Subject: RE: [Security400] Documenting / Managing iSeries security
> 
> 
> On issue 1.  I agree that owner profiles shouldn't be any 
> part of a group 
> profile.  Instead authorization lists should be used.  We're 
> moving in 
> that direction.
> 
> On issue 2.  We had a team of IBMers dialed in to resolve the 
> length of 
> the SAVSYS.  Soon as we started blasting the supplemental groups it 
> started behaving again.  The supplemental groups were increasing the 
> private authorities.  PRTPVTAUT was used.
> 
> I fail to see how you would like group profiles and still 
> feel that an 
> owner shouldn't be a group profile.
> 
> How would group profiles help in the following case:
> Betty should have access to libraries X and Z.
> Sam should have access to libraries Y and Z.
> Peter should have access to only library X.
> Julie should have access to libraries X and Y.
> 
> In our case each library has their own owner and their own 
> authorization 
> list.  We put Betty in authorization lists X and Y, Sam in Y 
> and Z, Peter 
> in X and Julie in X and Y.  We use authorization lists instead of the 
> object itself so that the objects within that library can be 
> secured with 
> that same authorization list.  Makes it easier to add/ delete 
> new users 
> and/or objects within the library.
> 
> 
> Rob Berendt
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
> 
> 
> 
>