> For the complete documentation index, see [llms.txt](https://docs.scanner.dev/scanner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/ossec.md).

# OSSEC

Scanner supports OSSEC logs, which contain a wide range of security-related information gathered from various sources on a system for host-based intrusion detection. In order for Scanner to see them, you need to push these logs to an S3 bucket that Scanner is linked to. In this guide, we use Wazuh to write OSSEC logs to a local file and then use Fluentd to push these logs to S3.

## Step 1: Publish to S3

Wazuh has a module called **fluent-forward** that will publish OSSEC logs to Fluentd. You can then use Fluentd to write logs to an S3 bucket.

Follow the Wazuh documentation to configure the **fluent-forward** module. Make sure to set the log format to **json**. See these Wazuh documentation articles for more information:

* [Forward alerts with Fluentd](https://wazuh.com/blog/forward-alerts-with-fluentd/)
* [fluent-forward](https://documentation.wazuh.com/current/user-manual/reference/ossec-conf/fluent-forward.html)

Follow the Fluentd documentation to configure it to write logs to S3. Make sure to configure the output format to be **JSON**. See: [Fluentd s3 output module](https://docs.fluentd.org/output/s3).

## Step 2: Ingest via Scanner Collect

Follow the [Create an Index Rule](/scanner/using-scanner-complete-feature-reference/data-ingestion/create-an-index-rule.md) guide to ingest logs from S3 via Scanner Collect.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/ossec.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.