Not a major thing, but also check any job schedule entries run under their
user id.
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 Steve Martinson
Sent: Tuesday, July 03, 2007 12:30 PM
To: midrange forum
Subject: Preparing for a High-profile Termination
Situation:
High-profile, knowledgeable staff member soon to be terminated (employment,
not by Ahh-nold); has "keys to the kingdom" for both the System i and the
network; likely knows passwords for many service and/or utility profiles on
the iSeries.
Requirement:
Prior to term date, analyze system for vulnerabilities associated with a
position like the one described above and prepare a task list that will
address the situation both before and after the termination.
Areas to be reviewed include system values, network attributes (exit points
too), directory entries, SST, job descriptions, subsystem routing entries,
all user and group profile parameters and their implications, authorities to
libraries, directory (WRKLNK) authorities, etc.
Can anyone think of anything else that could be a critical hole that should
be reviewed/covered?
Best regards and TIA,
Steven W. Martinson, CISSP, CISM
Sheshunoff Management Services, LP.
Senior Consultant - Technology & Risk Management
2801 Via Fortuna, Suite 600 | Austin, TX 78746
Direct: 281.758.2429 | Mobile: 512.779.2630
e.Mail: smartinson@xxxxxxxxx
midrange.com
