Event Details
Operating System->Microsoft Windows->Built-in logs->Windows 2008 or higher->Security Log->Object Access->Kernel Object->EventID 4656 - A handle to an object was requested. [2008]
EventID 4656 - A handle to an object was requested. [2008]
It is generated by corresponding resource manager in multiple subcategories: 
  • File System
  • Kernel Object
  • Registry
  • SAM
  • Other Object Access Events
Event 4656 might occur if the failure audit was enabled for Handle Manipulation using auditpol.

Find more information about this event on ultimatewindowssecurity.com.
A handle to an object was requested.

	Account Name:		IIZHU7$
	Account Domain:		ITSS
	Logon ID:		0x3e7

	Object Server:		Security
	Object Type:		Process
	Object Name:		C:\Windows\System32\lsass.exe
	Handle ID:		0x3e8

Process Information:
	Process ID:		0x4ecc
	Process Name:		C:\Windows\System32\wbem\WmiPrvSE.exe

Access Request Information:
	Transaction ID:		{00000000-0000-0000-0000-000000000000}
	Accesses:		Read from process memory

				Query process information

				Undefined Access (no effect) Bit 12

	Access Mask:		0x1410
	Privileges Used for Access Check:	-
	Restricted SID Count:	0
Description template stored in adtschema.dll:
A handle to an object was requested.

	Security ID:		%1
	Account Name:		%2
	Account Domain:		%3
	Logon ID:		%4

	Object Server:		%5
	Object Type:		%6
	Object Name:		%7
	Handle ID:		%8

Process Information:
	Process ID:		%14
	Process Name:		%15

Access Request Information:
	Transaction ID:		%9
	Accesses:		%10
	Access Mask:		%11
	Privileges Used for Access Check:	%12
	Restricted SID Count:	%13
Log Type: Windows Event Log
 Uniquely Identified By:
Log Name: Security
Filtering Field Equals to Value
OSVersion Windows Vista (2008)
Category Object Access
Source Microsoft-Windows-Security-Auditing
TaskCategory Kernel Object
EventId 4656
Field Matching
FieldDescriptionStored inSample Value
DateTime Date/Time of event origination in GMT format. DateTime 10.10.2000 19:00:00
Source Name of an Application or System Service originating the event. Source Security
Type Warning, Information, Error, Success, Failure, etc. Type Success
User Domain\Account name of user/service/computer initiating event. User RESEARCH\Alebovsky
Computer Name of server workstation where event was logged. Computer DC1
EventID Numerical ID of event. Unique within one Event Source. EventId 576
Description The entire unparsed event message. Description Special privileges assigned to new logon.
Log Name The name of the event log (e.g. Application, Security, System, etc.) LogName Security
Task Category A name for a subclass of events within the same Event Source. TaskCategory
Level Warning, Information, Error, etc. Level
Keywords Audit Success, Audit Failure, Classic, Connection etc. Keywords
Category A name for an aggergative event class, corresponding to the similar ones present in Windows 2003 version. Category Account Logon
Object Name InsertionString7
Whom InsertionString7
Object Type InsertionString6
Class Name InsertionString6
Security ID InsertionString1
Account Name InsertionString2
Account Domain InsertionString3
Subject: Security ID InsertionString1 NT AUTHORITY\SYSTEM
Subject: Account Name InsertionString2 IIZHU7$
Subject: Account Domain InsertionString3 ITSS
Subject: Logon ID InsertionString4 0x3e7
Object: Object Server InsertionString5 Security
Object: Object Type InsertionString6 Process
Object: Object Name InsertionString7 C:\Windows\System32\lsass.exe
Object: Handle ID InsertionString8 0x3e8
Process Information: Process ID InsertionString14 0x4ecc
Process Information: Process Name InsertionString15 C:\Windows\System32\wbem\WmiPrvSE.exe
Access Request Information: Transaction ID InsertionString9 {00000000-0000-0000-0000-000000000000}
Access Request Information: Accesses InsertionString10 Read from process memory
Access Request Information: Access Mask InsertionString11 0x1410
Access Request Information: Privileges Used for Access Check InsertionString12 -
Access Request Information: Restricted SID Count InsertionString13 0
Process Name InsertionString15
You must be logged in to comment