Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

February 15, 2005 12:00 AM

Identifying Web Site Logons in the Security Log

Windows IT Pro
InstantDoc ID #45214
Rating: (0)

I run a Windows Server 2003 Web site that requires basic authentication over Secure Sockets Layer (SSL) for logon. In the Security log, can I distinguish logons to the Web site from other logons such as console logons or logons from the trusted internal network (e.g., Terminal Services logons, network connection logons)?

Enable the Audit logon events policy on your Web server, then look for occurrences of event ID 540 (Successful Network Logon) in which the logon process is Advapi and the logon type is 8. Figure 1 shows an example of such an event. Event ID 540 indicates that a client has connected to the computer from over the network to, for example, access a shared folder or log on to the server via Microsoft IIS. Advapi is the logon process IIS uses for handling Web logons. Logon type 8 indicates a network logon that uses a clear-text password, which is the case when someone uses basic authentication to log on to IIS. Of course, because the browser and server have already established an SSL session, the clear-text password isn't visible to eavesdroppers.

Because some other types of connections can generate an event ID 540 with logon type 8, you should ensure that IIS generated the event by checking the Caller Process ID field. This field's value will match the process identifier (PID) of the W3wp process—IIS's core process. You can find W3wp's PID by looking in Windows Task Manager on the Processes tab. You might need to use View, Select Columns to add the PID column to Task Manager. Event ID 540 also provides the IP address of the Web client in the Source Network Address field.

Note that it's normal for an event ID 576 (Special privileges assigned to new logon) to follow an event ID 540 and an event ID 552 (Logon attempt using explicit credentials) to precede it. If your server has good Windows default security settings, users who log on will quite likely have the SeChangeNotifyPrivilege (aka Bypass traverse checking) privilege, which isn't a security problem. And Windows logs event ID 552 whenever a process impersonates another account, such as IIS impersonating the Web user.

Related Content:

ARTICLE TOOLS

Comments
  • Anonymous User
    7 years ago
    Feb 20, 2005

    I thought Basic Auth logins were processed as "logon locally" under IIS (unless this has changed for v6?). I seem to remember that you had to grant the "logon locally" right in user privileges (which was always a major pain...).

    http://www.microsoft.com/resources/documentation/iis/6/all/proddocs/en-us/sec_auth_basicauth.mspx

    cheers,
    Steve

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.