Windows Security Log Event ID 528

Operating Systems Windows Server 2000
Windows 2003 and XP
Type Success
Corresponding events
in Windows 2008
and Vista

528: Successful Logon

On this page

Event 528 is logged whenever an account logs on to the local computer, except for in the event of network logons (see event 540). Event 528 is logged whether the account used for logon is a local SAM account or a domain account.

Logon types possible:

Logon Type
 Interactive (logon at keyboard and screen of system) Windows 2000 records Terminal Services logon as this type rather than Type 10.
Network (i.e. connection to shared folder on this computer from elsewhere on network or IIS logon - Never logged by 528 on W2k and forward. See event 540)
Batch (i.e. scheduled task)
Service (Service startup)
Unlock (i.e. unnattended workstation with password protected screen saver)
NetworkCleartext (Logon with credentials sent in the clear text. Most often indicates a logon to IIS with "basic authentication") See this article for more information.
RemoteInteractive (Terminal Services, Remote Desktop or Remote Assistance)
CachedInteractive (logon with cached domain credentials such as when logging on to a laptop when away from the network)

For an explanation of the Logon Process field, see event 515. For an explanation of the Authentication Package field, see event 514.
Logon GUID is not documented. It is unclear what purpose the Caller User Name, Caller Process ID, and Transited Services fields serve.

Source Network Address corresponds to the IP address of the Workstation Name. Source Port is the TCP port of the workstation and has dubious value.

Logon ID is useful for correlating to many other events that occurr during this logon session.

Free Security Log Resources by Randy

Description Fields in 528

  • User Name:
  • Domain: 
  • Logon ID: useful for correlating to many other events that occurr during this logon session
  • Logon Type: %4
  • Logon Process: %5
  • Authentication Package: %6
  • Workstation Name: %7

The following field is not logged in Window 2000:

  • Logon GUID

The following fields are not logged in Windows 2000 or XP:

  • Caller User Name:
  • Caller Domain:
  • Caller Logon ID:
  • Caller Process ID:
  • Transited Services:
  • Source Network Address:
  • Source Port:

Supercharger Free Edition

Your entire Windows Event Collection environment on a single pane of glass.



Examples of 528

Successful Logon:

User Name:administrator

Logon ID:(0x0,0x558DD)
Logon Type:2
Logon Process:User32
Authentication Package:Negotiate
Workstation Name:W2MS
Windows XP and Windows Server 2003 add:
Logon GUID:{d39697e4-34a9-b3e0-f30a-d2ba517eb4a2}
Windows Server 2003 adds these fields:
Caller User Name:-
Caller Domain:-
Caller Logon ID:-
Caller Process ID: -
Transited Services: -
Source Network Address:
Source Port:3165

Top 10 Windows Security Events to Monitor

Free Tool for Windows Event Collection


Additional Resources