Skip to main content
Skip table of contents

V 2.0 : Object Access Events

Vendor Documentation

Classification

Rule NameRule TypeCommon EventClassification
V 2.0 : Object Access EventsBase RuleGeneral Audit MessageOther Audit
V 2.0 : EVID 4656 : Object Handle OpenedSub RuleObject AccessedAccess Success
V 2.0 : EVID 4656 : Failed to Open ObjectSub RuleAccess Object FailureAccess Failure
V 2.0 : EVID 4658 : Object Handle ClosedSub RuleObject Handle ClosedOther Audit Success
V 2.0 : EVID 4660 : Object DeletedSub RuleObject Deleted/RemovedAccess Success
V 2.0 : EVID 4661 : Object Handle OpenedSub RuleObject AccessedAccess Success
V 2.0 : EVID 4661 : Failed to Open ObjectSub RuleAccess Object FailureAccess Failure
V 2.0 : EVID 4663 : Operation Performed On ObjectSub RuleObject AccessedAccess Success
V 2.0 : EVID 4670 : Object Permissions ChangedSub RulePolicy Modified : ObjectPolicy
V 2.0 : EVID 4818 : Central Access Policy DifferenceSub RuleObject OperationOther Audit Success
V 2.0 : EVID 4691 : ALPC Port AccessedSub RuleObject AccessedAccess Success
V 2.0 : EVID 4656 : Object Handle OpenedSub RuleObject AccessedAccess Success
V 2.0 : EVID 4656 : Failed to Open ObjectSub RuleAccess Object FailureAccess Failure
V 2.0 : EVID 4659 : Object Open for DeletionSub RuleObject AccessedAccess Success

Mapping with LogRhythm Schema  

Device Key in Log MessageLogRhythm SchemaData TypeSchema Description
ProviderN/AN/AIdentifies the provider that logged the event. The Name and GUID attributes are included if the provider used an instrumentation manifest to define its events. The EventSourceName attribute is included if a legacy event provider (using the Event Logging API) logged the event.
EventID<vmid>

NumberThe identifier that the provider used to identify the event.
VersionN/A N/AThe version number of the event's definition.
Level<severity>String/NumberThe severity level defined in the event.
Task<vendorinfo>String/NumberThe task defined in the event. Task and Opcode are typically used to identify the location in the application from where the event was logged.
OpcodeN/A N/AThe opcode defined in the event. Task and Opcode are typically used to identify the location in the application from where the event was logged.
Keywords<result>
<tag1>
Text/StringA bitmask of the keywords defined in the event. Keywords are used to classify types of events (for example, events associated with reading data).
TimeCreatedN/A N/AThe time stamp that identifies when the event was logged. The time stamp will include either the SystemTime attribute or the RawTime attribute.
EventRecordIDN/A N/AThe record number assigned to the event when it was logged.
CorrelationN/A N/AThe activity identifiers that consumers can use to group related events together.
ExecutionN/A N/AContains information about the process and thread that logged the event.
ChannelN/A N/AThe channel to which the event was logged.
Computer<dname>Text/StringThe name of the computer on which the event occurred.
SubjectUserSidN/A N/AThe SID of account that requested a handle to an object.
SubjectUserName<login>N/AThe name of the account that requested a handle to an object.
SubjectDomainName<domainorigin>Text/StringThe subject’s domain or computer name. Formats vary, and include the following:
  • Domain NETBIOS name example: CONTOSO
  • Lowercase full domain name: contoso.local
  • Uppercase full domain name: CONTOSO.LOCAL
  • For some well-known security principals, such as LOCAL SERVICE or ANONYMOUS LOGON, the value of this field is NT AUTHORITY.
  • For local user accounts, this field will contain the name of the computer or device that this account belongs to.
SubjectLogonId<session>Text/StringA hexadecimal value that can help you correlate this event with recent events that might contain the same Logon ID.
ObjectServer<object>Text/StringThe Security value for this event.
ObjectType<objecttype>Text/StringThe type of an object that was accessed during the operation.
ObjectName<objectname>Text/StringThe name and other identifying information for the object for which access was requested. For example, for a file, the path would be included.
HandleIdN/AN/AA hexadecimal value of a handle to Object Name. This field can help you correlate this event with other events that might contain the same Handle ID.
TransactionIdN/A Text/String/NumberThe unique GUID of the transaction. This field can help you correlate this event with other events that might contain the same Transaction ID.
AccessList<subject>Text/String/NumberThe list of access rights which were requested by Subject\Security ID. These access rights depend on ObjectType.
AccessReasonN/A N/AThe list of access check results. The format of this varies, depending on the object. For kernel objects, this field does not apply.
AccessMask<status>Text/String/NumberA hexadecimal mask for the requested or performed operation.
PrivilegeListN/A N/AThe list of user privileges which were used during the operation, for example, SeBackupPrivilege. This parameter might not be captured in the event, and in that case appears as “-” string.
RestrictedSidCountN/A NumberNumber of restricted SIDs in the token. Applicable to only specific ObjectTypes.
ProcessId<processid>NumberA hexadecimal Process ID of the process through which the access was requested. Process ID (PID) is a number used by the operating system to uniquely identify an active process.
ProcessName<process>Text/StringThe full path and the name of the executable for the process.
ResourceAttributesN/A Text/StringThe attributes associated with the object. For some objects, the field does not apply and “-“ is displayed.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.