9 replies
by farisland
For the windows nt part, if you didnt have auditing enabled its impossible right now to see what has changed and who accessed what.
Start with changing all password of the users and all services in case of the SAM has been compromised.
You have tostart with enabling auditing for success and failed user logons ( when you changed the passwords and there is a lot of failed logon attempts you can start tracing that) , and for access of the most critical shared data. Make sure the logfilesize is big and make a habit of saving it everyday so you can check back on it.
Make sure your servers are patched against the latest security issues of nt (simply go to the www.windowsupdate.com site and download them or go to the download section of MS todownload the pacthes.
On the servers and on the domain move the everyone group from the logon locally right (this means that everyone can fysically sit behind the servers and logon on, you want only the administrators to do that).
Go to the technet section of MS, the is artickle called securing or hardening a nt server. I will try to look that up.
There is software to detect those issues but I don not know them (+ there is a budget issue :) )
regards,
Leopold
http://www.enteract.com/~lspitz
a beginners hardening nt.
On thec techrepublic site is also a artickle called.
Also 7 tips for greater server security
by farisland
by penguinsrule
I have to agree with poster #1..
do you have a good firewall installed?
by farisland
by penguinsrule
Since you didn't say where the penetration came from, we have to assume the obvious first..
I would:
Turn auditing on for your servers
I would go over the group permissions really well, and lock down as appropriate. Depending on the environment you could have folks with more permissions that they need. I've certainly seen this before.
Like #1 said - make sure you have every possible security patch installed.
You could trace a few things at the packet level using a sniffer.
I'd lock down network properties
Rick
(For Grins - I think you should migrate to secure VMS configured to B2 security - to date, there are NO KNOWN penetrations.) :)
Yes, I'm a VMS bigot - who sometimes does NT/2000 work.
by farisland
by farisland
This discussion is closed to new replies.
Trending Security posts
Sort by Trending