If you are serious about security, then you must schedule time to
examine your security logs. If this means that you are swamped with data, then either
filter the events, or change your policy to collect less
data. This section concentrates on configuring and interpreting account logon
entries in the event viewer.
You can configure Windows Server 2003 audit settings in several places.
Please check BOTH these locations:
Active Directory Users and Computers
\domain\properties\group policy.
All Programs, Administrative Tools, Domain Controller Security Policy.
Once you open the policy, navigate
to this path: (See Diagram Below)
Computer Configuration\Windows Settings\Security Settings\Local
Policies\Audit Policy.
If all else fails then call for the built in help and it will give you a link to
the correct path.
Policy for Domain
Controllers or the Default Domain Policy
2) Distinguish between
these two settings:
Audit Account Logon - Means people connecting across the network
Audit Logon Events - Means a keyboard logon, someone at the very
Domain Controller
3) The default auditing is for success only, so check the
Failure box if you want to see Events 675 and 680.
Guy Recommends: SolarWinds LANSurveyor
LANSurveyor will produce a neat diagram of your network topology. But that's
just the start;
LANSurveyor can
create an inventory of the hardware and software
of your machines and network devices. Other neat features include dynamic
update for when you add new devices to your network. I also love the ability to export
the diagrams
to Microsoft Visio.
Finally, Guy bets that if you take a free trial of LANSurveyor then you will
find a device on your network that you had forgotten about, or someone else
installed without you realizing!
Now we switch to the Event Viewer (All Programs, Administrative Tools). Amongst the numerous events in the Security Log, here are
ID numbers to
look out for. To refine your search, select View (menu), Filter.
672 An authentication service (AS)
ticket was successfully issued and validated.
673 A ticket granting service (TGS) ticket was granted.
674 A security principal renewed an AS ticket or TGS ticket.
675 Pre-authentication failed. This event is generated on a Key Distribution
Center (KDC) when a user types in an incorrect password.
678 An account was successfully mapped to a domain account.
680 Successful or Failed logon attempt - see Description
682 A user has reconnected to a disconnected terminal server session.
683 A user disconnected a terminal server session without logging off.
The following events are not generated in Windows XP or in the Windows
Server 2003 family. So must come from NT 4.0 or Windows 9x machines.
677 A
TGS ticket was not granted.
676 Authentication ticket request failed.
681 Logon failure. A domain account logon was attempted.
Use
the View (Menu) filter and enter 675 in the Event ID. If you do
not get any of these events, then deliberately logon to the domain
controller with the wrong password or account.
Once you
double click an event check the extra information in the
Description.
Here are some useful codes: 0x6 The
username does not exist 0x17 The account has expired 0x18
Username exists, but password is wrong 0x25 Workstation's clock is
out of synch
Troubleshooting: if you do not get any 675 when
you log on with the wrong password check Traps.
3221225572 User logon with misspelled user account
3221225578 User logon with misspelled password
3221225584 User logon from unauthorized workstation
3221225585 User logon with expired password
3221225586 User logon to account disabled
3221225875 User logon with expired account
3221226036 User logon with account locked
Network security is complex. As an MCT trainer, I can thoroughly recommend
TrainSignal because they
provide practical hands on training. In particular, I like the way TrainSignal cover all learning methods, instructor lead, video and of course text material. You can either take one module, for example
Network Security or go for
a combination of modules.
See more about Network Security training here
