Skip to main content
Skip table of contents

V 2.0 : AD Object Events

Vendor Documentation


Rule NameRule TypeCommon EventClassification
V 2.0 : AD Object EventsBase RuleObject AccessedAccess Success
V 2.0 : EVID 5136 : AD Object ModifiedSub RuleObject ModifiedAccess Success
V 2.0 : EVID 5137 : AD Object CreatedSub RuleObject CreatedAccess Success
V 2.0 : EVID 5138 : AD Object RestoredSub RuleDirectory Service Object RestoredOther Audit Success
V 2.0 : EVID 5139 : AD Object MovedSub RuleObject MovedAccess Success
V 2.0 : EVID 5141 : AD Object DeletedSub RuleObject Deleted/RemovedAccess Success

Mapping with LogRhythm Schema  

Device Key in Log MessageLogRhythm SchemaData Type

Schema Description


Identifies 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.


The identifier that the provider used to identify the event.


The version number of the event's definition.


The severity level defined in the event.


The task defined in the event. Task and Opcode are typically used to identify the location in the application from where the event was logged.


The opcode defined in the event. Task and Opcode are typically used to identify the location in the application from where the event was logged.


A bitmask of the keywords defined in the event. Keywords are used to classify types of events (for example, events associated with reading data).


The time stamp that identifies when the event was logged. The time stamp will include either the SystemTime attribute or the RawTime attribute.


The record number assigned to the event when it was logged.


The activity identifiers that consumers can use to group related events together.


Contains information about the process and thread that logged the event.


The channel to which the event was logged.


The name of the computer on which the event occurred.


Multiple modifications are often executed as one operation via LDAP. This value allows you to correlate all the modification events that comprise the operation.


This field always has “-“ value. Not in use.


The SID of account that requested the create object operation.


The name of the account that requested the create object operation.


The 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.


A hexadecimal value that can help you correlate this event with recent events that might contain the same Logon ID.


The name of an Active Directory domain, where new object is created.


Has Active Directory Domain Services value for this event.


The distinguished name of the object that was modified.


The distinguished name of the object that was modified.


Each Active Directory object has globally unique identifier (GUID), which is a 128-bit value that is unique not only in the enterprise but also across the world. GUIDs are assigned to every object created by Active Directory. Each object's GUID is stored in its Object-GUID (objectGUID) property.


The class of the object that was created.

AttributeLDAPDisplayName<account>Text/Stringthe object attribute that was modified.
AttributeValue<responsecode>Text/String/Numberthe value which was added or deleted, depending on the Operation\Type field.
JavaScript errors detected

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

If this problem persists, please contact our support.