Guys;
Thanks for the input and I love the philosophical debate about how this happened, what I can do in the future to prevent it, etc.
A little more info; I am being brought in to help consult on this project, the ex-admin is, well, let's just say the local and state law enforcement teams are being brought in today to assist, and therefore the problem is probably pretty deep. He has been a fully entrenched admin since the inception of the agency.
What I really am looking for is some kind of checklist/ information sheet so we don't forget anything major, at least to check.
Depending on what we might find today, the decision is already on the table as to whether we should treat this as a total breech and scrub the whole plant and start over. That remains to be seen.
While an automated solution would be great to have, I don't have time to research them before we get to work. (I am of the belief that they won't work well anyway but that is another debate.)
Does anyone know of a SANS, or GIAC or any other security body who has a "minder" list of some sort? I know others have gone through this and have learned some lessons, both good and bad ones, that I hope they can share.
If not, I will try and document what we do and maybe look to publish something for future reference.
Thanks,
>From: "James Patterson Wicks" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: RE: [Full-Disclosure] Removing FIred admins
>Date: Fri, 13 Feb 2004 08:06:57 -0500
>
>Only the senior administrator and the CTO have the root password to the
>Unix systems. The senior admin does not "own" and servers, but is the
>manager for all of the other admins. Could he get mad and make changes
>to the interpreter, but the server "owner" would notice this and check
>the changes against the change management log. Any unusual events would
>be sent to the CTO.
>
>Like you said, there is no magic button to press and instantly remove an
>admin's influence from an enterprise. BUT if you have a good process in
>place that leverages existing technologies, you can do a good job of
>protecting your enterprise. Admins leave companies all the time, but
>enterprises continue to operate without a problem.
>
>If all else fails, make sure that the company lawyer is in the office
>when you fire the admin. A good threat can go a long way.
>
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Volker
>Tanger
>Sent: Friday, February 13, 2004 2:51 AM
>To: [EMAIL PROTECTED]
>Subject: Re: [Full-Disclosure] Removing FIred admins
>
>Hi!
>
> > We are working on something called "The Button", which is nothing but
> > small script that activates a series of scripts that change all root,
> > local and domain administrator passwords on our Unix and Windows
> > servers when run.
>
>The ex-admin had ROOT access to "his" servers, right? So he can change
>ANYTHING, right? Including the script, e.g. like NOT changing passwords
>or adding secret admin-level accounts, right?
>
>You said "script", so it uses BASH, PERL or something. ROOT can change
>anything, right? So he could have changed the BASH, PERL interpreter or
>something, right?
>
>There is no technical solution to a social problem - well, except in
>this case maybe reformatting the disks and reinstalling from scratch and
>clean media.
>
>Sorry
>
>Volker Tanger
>ITK-Security
>
>_______________________________________________
>Full-Disclosure - We believe in it.
>Charter: http://lists.netsys.com/full-disclosure-charter.html
>
>
>This e-mail is the property of Oxygen Media, LLC. It is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. Distribution or copying of this e-mail or the information contained herein by anyone other than the intended recipient is prohibited. If you have received this e-mail in error, please immediately notify us by sending an e-mail to [EMAIL PROTECTED] and destroy all electronic and paper copies of this e-mail.
>
>
>_______________________________________________
>Full-Disclosure - We believe in it.
>Charter: http://lists.netsys.com/full-disclosure-charter.html
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
