Dear Steve,
Nothing about your note suggests that the company should feel safe
because of the individual's integrity. This individual could already
"feel" that a termination is brewing. Therefore, risk control demands
more than access blockage. Your system should be searched for
sophisticated, delayed-action Trojan horses.
Look here for a presentation of OS/400 security vulnerabilities:
http://www.unbeatenpathintl.com/BOH-Benefits/source/1.html
You'll see a page in the format of an Optometrist's eye-chart.
Than navigate to these three eye-chart lines to learn how very subtle
Trojan Horses can be left behind:
LPED line ---> read the "Egyptian Stop and Go Lights" item
PECFD line --> read the "Can a Trigger Program be a Trojan horse?" item
CLFPODEHYGQWBR line --> read the "Over-the-Horizon Radar" item
These security vulnerabilities and many others can be found with our
"Bill of Health" Security diagnostics and Rx for iSeries software:
http://www.unbeatenpathintl.com/BOH/source/1.html
If the company had a clean "pre-termination-started-to-brew" Bill of Health
report on file and compared it to a post-termination Bill of Health report,
the net difference would be very instructive for this situation.
Warmest regards,
Milt Habeck
Unbeaten Path International
North America: (888) 874-8008
International: (262) 681-3151
+++++++ +++++++ +++++++ +++++++ +++++++ +++++++
From: Steve Martinson
To: midrange forum
Sent: Tuesday, July 03, 2007 11:29 AM
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
