RE: Robot/SCHEDULE Security

Steve,
We are definitely using the 'Maintain Secured Objects' method, and
it works great. We have some developers who we wanted to allow access to
Robot for certain functions like looking at jobs, but we needed to prevent
them from updating Robot records. Many admin. Type tasks are locked down
also and it works fine.

Larry

Larry Ketzes | Senior iSeries System Administrator | AIG / ALICO - American
Life Insurance Company
One ALICO Plaza, 600 N. King Street, AMIS | Wilmington, DE 19801 | *:
302.594.2146 | 7: 302.830.4524| *: larry.ketzes@xxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steven Martinson
Sent: Tuesday, April 29, 2008 1:01 PM
To: Midrange List
Subject: Robot/SCHEDULE Security

Hello all you purveyors of iSeries "hackish amusements," with your
self-replicating RPG programs... (Sorry, I couldn't resist ;-)...

Is anyone out there using Robot/SCHEDULE application security vs. just using
the default *PUBLIC access that is used when the "Do you want to use ROBOT
security system" parameter is set to "N" on the General System Defaults
screen? If so, are you using the profile-level controls found within the
"Maintain Secured Objects" screens or are you using an authorization list
(or lists)? Are you using the "Authorized Objects" screens to control
objects referenced when users setup/manage Robot jobs?

I am working on closing some exposures for my current client and I don't
have the luxury of a separate test system for Robot. I am curious to know
what other's experiences have been.

TIA for any input!

Best regards,

Steve

Steven W. Martinson, CISA, CISM, CISSP
Security Consultant
Cypress, Texas


Smart-Consultant@xxxxxxxxxxxxx
Mobile: 713.277.5845
Fax: 281.758.2429