Skip to main content
Skip table of contents

V 2.0 : Cryptographic Next Generation Events

Vendor Documentation

Classification

Rule Name

Rule Type

Common Event

Classification

V 2.0 : Cryptographic Next Generation EventsBase RuleCryptographic OperationOther Audit Success
V 2.0 : EVID 5063 : CNG - Successful Provider OperationSub RuleCryptographic OperationOther Audit Success
V 2.0 : EVID 5063 : CNG - Failed Provider OperationSub RuleCryptographic FailureError
V 2.0 : EVID 5064 : CNG - Successful Context OperationSub RuleCryptographic OperationOther Audit Success
V 2.0 : EVID 5064 : CNG - Failed Context OperationSub RuleCryptographic FailureError
V 2.0 : EVID 5065 : CNG - Successful Context ModificationSub RuleCryptographic OperationOther Audit Success
V 2.0 : EVID 5065 : CNG - Failed Cont. ModificationSub RuleCryptographic FailureError
V 2.0 : EVID 5066 : CNG - Successful Function OperationSub RuleCryptographic OperationOther Audit Success
V 2.0 : EVID 5066 : CNG - Failed Function OperationSub RuleCryptographic FailureError
V 2.0 : EVID 5067 : CNG - Successful Function ModificationSub RuleCryptographic OperationOther Audit Success
V 2.0 : EVID 5067 : CNG - Failed Function ModificationSub RuleCryptographic FailureError
V 2.0 : EVID 5068 : CNG - Successful Function ProviderSub RuleCryptographic OperationOther Audit Success
V 2.0 : EVID 5068 : CNG - Failed Function Provider Oper.Sub RuleCryptographic FailureError
V 2.0 : EVID 5069 : CNG - Successful Function PropertySub RuleCryptographic OperationOther Audit Success
V 2.0 : EVID 5069 : CNG - Failed Function Property Oper.Sub RuleCryptographic FailureError
V 2.0 : EVID 5070 : CNG - Successful Function PropertySub RuleCryptographic OperationOther Audit Success
V 2.0 : EVID 5070 : CNG - Failed Function Prop ModificationSub RuleCryptographic FailureError

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/AN/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/AN/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>
<tag2>
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/AN/AThe time stamp that identifies when the event was logged. The time stamp will include either the SystemTime attribute or the RawTime attribute.
EventRecordIDN/AN/AThe record number assigned to the event when it was logged.
CorrelationN/AN/AThe activity identifiers that consumers can use to group related events together.
ExecutionN/AN/AContains information about the process and thread that logged the event.
ChannelN/AN/AThe channel to which the event was logged.
Computer<dname>Text/StringThe name of the computer on which the event occurred.
JavaScript errors detected

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

If this problem persists, please contact our support.