For the insanely paranoid
Now the next part is for those of you who are really paranoid.
And that is not only locking out the true admin account, but disabling it all together.
The first part of this is that you need to enable a lockout threshold. I suggest between 3-5 attempts. And your lockout duration needs to be indefinite.
Now the inherent problem with the true admin account, is that it can not be locked out. However, using a small tool called admnlock from microsoft. You canallow the true admin account to be locked out.
Now that does not automatically lock it out. It just "allows" it to be locked out.
So, you manually force it to be locked out. Assuming you have already set up your copied admin account. And youhave assigned a strong password to the true admin account.
Log off as the true admin account. Go to another machine and start to log on as the true admin account with a bad password. Keep doing it until you lock out the admin account.
We arenot done yet. Make sure you have auditing set up for failures. Just doing all of this work means nothing if you are not going to log it.
One of the best books to read on this subject is the Hacking Exposed series. Foundstone has some great advice. Plus they books written just for 2K, Linux, and Web applications. There latest being Java and J2EE.
I hope you enjoyed my little nuggets of crap.
3nj0y & h@99y H@c71ng!