# Windows Sysmon

Scanner supports Sysmon (System Monitor) logs on Windows, which contain information about process creations, network connections, and changes to file creation time on Windows devices. In order for Scanner to receive Sysmon log events, you need to configure a worfklow to push these logs to an S3 bucket that Scanner is linked to.

## Step 1: Publish to S3

You can use the [Winlogbeats](https://www.elastic.co/guide/en/beats/winlogbeat/current/_winlogbeat_overview.html) agent to write Sysmon log events as JSON to local files. See the following Winlogbeats documentation:

* [Winlogbeats Sysmon Module](https://www.elastic.co/guide/en/beats/winlogbeat/current/winlogbeat-module-sysmon.html)
* [Configure the File output](https://www.elastic.co/guide/en/beats/winlogbeat/current/file-output.html)

You can use the [Fluentd](https://docs.fluentd.org/) agent to read Sysmon logs from local file and write the logs to your S3 bucket. Make sure to configure the output format to be **JSON**. See the following Fluentd documentation articles:

* [Fluentd tail input module](https://docs.fluentd.org/input/tail)
* [Fluentd s3 output module](https://docs.fluentd.org/output/s3)

## Step 2: Ingest via Scanner Collect

Follow the instructions [here](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/custom-logs-aws-s3) to ingest logs from S3 via Scanner Collect