Skip to main content
Skip table of contents

V 2.0 : EVID 4964 : Special Groups Assigned to Log

Vendor Documentation

Classification

Rule Name

Rule Type

Common Event

Classification

V 2.0 : EVID 4964 : Special Groups Assigned to LogBase RuleSpecial Groups Assigned to New LogonOther Audit Success

Mapping with LogRhythm Schema  

Device Key in Log MessageLogRhythm SchemaData TypeSchema Description
Provider N/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>Text/StringThe severity level defined in the event.
Task<vendorinfo>Text/StringThe 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>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 logon for New Logon account. Event Viewer automatically tries to resolve SIDs and show the account name.
SubjectUserName<login>Text/StringThe name of the account that requested logon for New Logon account.
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>NumberA hexadecimal value that can help you correlate this event with recent events that might contain the same Logon ID.
LogonGuidN/A N/AA GUID that can help you correlate this event with another event that can contain the same Logon GUID.
TargetUserSidN/A N/AThe SID of account that performed the logon.
TargetUsername<account>Text/StringThe name of the account that performed the logon.
TargetDomainName<domainimpacted>Text/StringThe target'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.
TargetLogonId N/AN/AA hexadecimal value that can help you correlate this event with recent events that might contain the same Logon ID.
TargetLogonGuidN/A N/AA GUID that can help you correlate this event with another event that can contain the same Logon GUID.
SidList<group>NumberThe list of special group SIDs, which New Logon\Security ID is a member of.
JavaScript errors detected

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

If this problem persists, please contact our support.