Event Details
User Activity->Object Access->Registry Object Access->Windows 2000-2003->EventID 560 - Object Open [Win 2000] - Failed
EventID 560 - Object Open [Win 2000] - Failed
 Sample:
        Event Type:	Success Audit
        Event Source:	Security
        Event Category:	Object Access
        Event ID:	560
        Date:		4/17/2009
        Time:		9:21:27 AM
        User:		NT AUTHORITY\SYSTEM
        Computer:	DCCC1
        Description:
        Object Open:
        Object Server:	Security Account Manager
        Object Type:	SAM_SERVER
        Object Name:	SAM
        New Handle ID:	856224
        Operation ID:	{0,532713543}
        Process ID:	280
        Primary User Name:	DCCC1$
        Primary Domain:	LOGISTICS
        Primary Logon ID:	(0x0,0x3E7)
        Client User Name:	DCCC1$
        Client Domain:	LOGISTICS
        Client Logon ID:	(0x0,0x3E7)
        Accesses:	DELETE 
		READ_CONTROL 
		WRITE_DAC 
		WRITE_OWNER 
		ConnectToServer 
		ShutdownServer 
		InitializeServer 
		CreateDomain 
		EnumerateDomains 
		LookupDomain        
        Privileges:	-
Log Type: Windows Event Log
 Uniquely Identified By:
Log Name: Security
Filtering Field Equals to Value
OSVersion Windows 2000
Category Object Access
Source Security
EventId 560
Type Failure Audit
InsertionString2 Key
Field Matching
FieldDescriptionStored inSample Value
When At what date and time a user activity originated in the system. DateTime 12/14/2009 6:59:09 AM
Who Account or user name under which the activity occured. Client User Name DCCC1$
What The type of activity occurred (e.g. Logon, Password Changed, etc.) "Registry Object Access" Registry Object Access
Where The name of the workstation/server where the activity was logged. Computer DC1
Where From The name of the workstation/server where the activity was initiated from. - 10.10.10.10
Severity Specify the seriousness of the event. "High" High
WhoDomain Client Domain LOGISTICS
WhereDomain -
Result Successful or Failed "Failed" Failed
Object Name Object Name C:\script
Object Type Object Type File
Whom -
Comments
You must be logged in to comment