RE: Separation of Duties...

["Gary Monnier" <gary.monnier@xxxxxxxxxxxxx>]

Ken,

This is the type of situation PowerTech's Authority Broker is suited
for.  You minimize Admin initial authorities.  They switch to more
powerful profiles as needed.  Actions taken while switched are audited.
No authority is taken away.  Actions outside their minimum authority are
audited though.

I know this is a HIGHLY unpopular action.  There is much gnashing of
teeth, wails of woe and dire warnings of catastrophe when it is
considered.  But, to me anyway, what the auditors are requesting is akin
to the Generally Accepted Accounting Practices accountants follow.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Graap, Kenneth
Sent: Wednesday, October 31, 2007 8:17 AM
To: Midrange Systems Technical Discussion
Subject: Separation of Duties...


We are in the middle of an IS Audit and the auditor is asking us why we
don't separate the duties of DB Administrator and System Administrator
on our System i platform.

.Historically we have always combined these duties on the System i but
we are now being pressured to come up with a way to separate them.

As anyone else had to do this and if so, how did you define these duties
and set up system security to enforce it?

or ... can anyone share a compelling argument for not separating these
duties?

Kenneth

****************************************
Kenneth E. Graap
IBM Certified Specialist 
iSeries Multiple System Administrator
NW Natural (Gas Services)
keg@xxxxxxxxxxxxx
Phone: 503-226-4211 x5537
FAX:    503-721-2518
****************************************