Microsoft-Windows-Management-SecureAssessment

11 events across 1 channel

Event	Title	Channel	Sample
100	An error was encountered.	Operational	N
101	A process was forcibly terminated.	Operational	N
200	A new lockdown request has been received.	Operational	N
201	Creating a lockdown context for the app.	Operational	N
202	Enrolling the device succeeded.	Operational	N
203	Enrolling the device failed.	Operational	N
204	Lockdown policies were successfully applied.	Operational	N
205	Lockdown is enforced.	Operational	N
206	Lockdown request completed successfully.	Operational	N
207	Device enrollment was skipped for this lockdown session.	Operational	N
208	Unenrollment completed successfully.	Operational	N

Event ID 100: An error was encountered.

Provider: Microsoft-Windows-Management-SecureAssessment
Channel: Operational
Opcode: Info

Description

An error was encountered. (error code = ErrorCode; function = Function; line number = LineNumber).

Message #

An error was encountered. (error code = %1; function = %2; line number = %3)

Fields #

Name	Description
`ErrorCode` HexInt32
`Function` AnsiString
`LineNumber` UInt32

Event ID 101: A process was forcibly terminated.

Provider: Microsoft-Windows-Management-SecureAssessment
Channel: Operational
Opcode: Info

Description

A process was forcibly terminated. (process name = ProcessName; result = TerminationResult).

Message #

A process was forcibly terminated. (process name = %1; result = %2)

Fields #

Name	Description
`ProcessName` UnicodeString
`TerminationResult` Boolean

Event ID 200: A new lockdown request has been received.

Provider: Microsoft-Windows-Management-SecureAssessment
Channel: Operational
Task: Lockdown

Description

A new lockdown request has been received. (enable lockdown = Enable; already locked down = CurrentlyEnabled).

Message #

A new lockdown request has been received. (enable lockdown = %1; already locked down = %2)

Fields #

Name	Description
`Enable` Boolean
`CurrentlyEnabled` Boolean

Event ID 201: Creating a lockdown context for the app.

Provider: Microsoft-Windows-Management-SecureAssessment
Channel: Operational
Task: Lockdown

Description

Creating a lockdown context for the app. (Create new = NewContextCreated).

Message #

Creating a lockdown context for the app. (Create new = %1)

Fields #

Name	Description
`NewContextCreated` Boolean

Event ID 202: Enrolling the device succeeded.

Provider: Microsoft-Windows-Management-SecureAssessment
Channel: Operational
Task: Lockdown

Description

Enrolling the device succeeded. (enrollment ID = EnrollmentID).

Message #

Enrolling the device succeeded. (enrollment ID = %1)

Fields #

Name	Description
`EnrollmentID` UnicodeString

Event ID 203: Enrolling the device failed.

Provider: Microsoft-Windows-Management-SecureAssessment
Channel: Operational
Task: Lockdown

Description

Enrolling the device failed. (error = ErrorCode).

Message #

Enrolling the device failed. (error = %1)

Fields #

Name	Description
`ErrorCode` HexInt32

Event ID 204: Lockdown policies were successfully applied.

Provider: Microsoft-Windows-Management-SecureAssessment
Channel: Operational
Task: Lockdown

Description

Lockdown policies were successfully applied. (enrollment ID = EnrollmentID).

Message #

Lockdown policies were successfully applied. (enrollment ID = %1)

Fields #

Name	Description
`EnrollmentID` UnicodeString

Event ID 205: Lockdown is enforced.

Provider: Microsoft-Windows-Management-SecureAssessment
Channel: Operational
Task: Lockdown

Description

Lockdown is enforced. (enrollment ID = EnrollmentID; caller ID = CallerID).

Message #

Lockdown is enforced. (enrollment ID = %1; caller ID = %2)

Fields #

Name	Description
`EnrollmentID` UnicodeString
`CallerID` UnicodeString

Event ID 206: Lockdown request completed successfully.

Provider: Microsoft-Windows-Management-SecureAssessment
Channel: Operational
Task: Lockdown

Description

Lockdown request completed successfully. (Enable = Enable).

Message #

Lockdown request completed successfully. (Enable = %1)

Fields #

Name	Description
`Enable` Boolean

Event ID 207: Device enrollment was skipped for this lockdown session.

Provider: Microsoft-Windows-Management-SecureAssessment
Channel: Operational
Task: Lockdown

Description

Device enrollment was skipped for this lockdown session.

Message #

Device enrollment was skipped for this lockdown session.

Event ID 208: Unenrollment completed successfully.

Provider: Microsoft-Windows-Management-SecureAssessment
Channel: Operational
Task: Lockdown

Description

Unenrollment completed successfully. (enrollment ID = EnrollmentID).

Message #

Unenrollment completed successfully. (enrollment ID = %1)

Fields #

Name	Description
`EnrollmentID` UnicodeString

Provenance

Where this provider's schema came from, and which Windows build it was observed on. Windows can change a provider's event schema between builds, so use this to judge whether it matches the build you collect from.

ETW provider GUID a329cf81-57ec-46ed-ab7c-261a52b0754a

Defined in Windows.Management.SecureAssessment.Diagnostics.dll, which carries the event manifest.

Observed on:

Win11-26200.6584, schema read from the registered manifest, binary version 10.0.26100.1, captured 2026-06-02

Downloads

Microsoft-Windows-Management-SecureAssessment registered manifest XML (in the Win11-26200.6584 manifest pack, 2.0 MB) manifest-xml

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)