* Client event queries are targeted by label group.
* Sysmon will be installed automatically and events will be forwarded.
---
## Viewing Sysmon events relayed to the server

---
## Turning artifacts into a detection
* We have previously looked at log enable/disable by examining registry keys.
* Can we detect when these registry keys are changing?
* The diff() plugin periodically runs a query and reports on changes.
* Install the `Windows.Events.EventLogModifications` artifact
---
## Windows.Events.EventLogModifications

---
## System changes relayed to server
Good for slow changes

---
# USN Journal monitoring
## File modification monitoring at scale.
---
## USN Journal
* We have previously seen that the USN journal is useful for
recovering evidence of file modification.
* Sadly in practice the USN journal rolls over fairly quickly (days!)
* Wouldn't it be nice to feed the events to the server continuously?
---
## Windows.Detection.USN
* Enable the Windows.Detection.USN artifact - target paths of
interest.

---
## Inspect streaming results
* See direct evidence of execution, tasks creation etc.
