> For the complete documentation index, see [llms.txt](https://docs.fourclover.org/v0.1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fourclover.org/v0.1/owasp-four-clover-documentation.md).

# OWASP Four Clover Documentation

Learn how to get up and running with OWASP Four Clover (OFC) through tutorials and platform resources.

{% hint style="warning" %}
**Important:** Please keep in mind that Four Clover is still under active development and full backward compatibility is not guaranteed before reaching v1.0.0. Four Clover is not recommended for production critical applications yet, unless you are fine with reading the changelog and applying some manual migration steps from time to time.
{% endhint %}

## Overview

OWASP Four Clover (OFC) is a versatile file integrity monitoring tool designed to bolster cybersecurity by ensuring the integrity of files, configurations, and critical data. By monitoring and detecting unauthorized changes, the tool provides a crucial layer of defense against malware, intrusions, and security breaches. Whether you’re safeguarding system files, tracking configuration modifications, or enforcing security policies, OFC simplifies the process with user-friendly commands and insightful reports.

> File integrity monitoring (FIM) plays a pivotal role in cybersecurity, serving as a critical defense mechanism against unauthorized changes and ensuring the integrity of digital assets. In a rapidly evolving threat landscape, FIM offers several key benefits that are essential for maintaining a secure and trustworthy computing environment.
>
> — Trust.

## Quick links

{% content-ref url="/pages/XnrGVqwg9oWo27fFVo1u" %}
[Getting Started](/v0.1/overview/getting-started.md)
{% endcontent-ref %}

{% content-ref url="/pages/oWX326z1nv9osOuufa0z" %}
[Our Features](/v0.1/overview/our-features.md)
{% endcontent-ref %}

## Get Started

We've put together some helpful guides for you to get setup with our product quickly and easily.

{% content-ref url="/pages/sb46kKBVXnc4pqOCKyND" %}
[Performing Scans on Directories and Files](/v0.1/tool-guides/performing-scans-on-directories-and-files.md)
{% endcontent-ref %}

{% content-ref url="/pages/QrmbNxLkw16nmdaQUnX2" %}
[Initiating a Comparison](/v0.1/tool-guides/initiating-a-comparison.md)
{% endcontent-ref %}

{% content-ref url="/pages/zMOavHhE84HS9EbMGDBq" %}
[Performing Scans Based on Policies](/v0.1/tool-guides/performing-scans-based-on-policies.md)
{% endcontent-ref %}


---

# 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.fourclover.org/v0.1/owasp-four-clover-documentation.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.