> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/agentless-file-integrity-monitoring/agentless-file-integrity-monitoring.md).

# Agentless file integrity monitoring

Agentless file integrity monitoring (FIM) detects when monitored files and directories on your cloud VMs are created, modified or deleted, without installing an agent.

{% hint style="info" %}
**License**: Requires Cortex Cloud Runtime Security and the FIM add-on.
{% endhint %}

Agentless file integrity monitoring (FIM) is a capability of Agentless disk scanning (ADS) that detects when monitored files and directories on cloud virtual machines (VMs) are created, modified, or deleted.

Agentless FIM extends file monitoring to cloud VMs where you can’t or don’t want to install an agent. ADS scans cloud VMs periodically and compares each scan with the previous one. When a policy is created or modified, the first scan of a VM establishes a baseline. Starting with the second scan, agentless FIM reports any changes detected since the previous scan.

Agentless FIM provides the following benefits:

* **Increased FIM coverage**: Agentless FIM monitors file changes on cloud VMs where you can’t or don't want to install an agent.
* **No impact on workloads**: Agentless FIM monitoring doesn't affect the performance or stability of your applications.
* **Focused monitoring**: You choose the files and directories to monitor and the types of changes to track.
* **Agentless FIM events visibility and investigation**: Agentless FIM events are visible in the **Agentless** tab on the **File Integrity Monitoring → Events** page. They are also displayed in the asset inventory card as an insight named **FIM Events Detected**, along with aggregated findings. You can also use XQL query to search agentless FIM events.

To set up agentless FIM, complete the following tasks:

1. [Create a FIM rule group](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/protect-your-endpoints/endpoint-protection/file-integrity-monitoring-fim#add-a-new-fim-rule-group) or re-use the predefined rule groups that define the files and directories to monitor.
2. [Create an agentless FIM policy](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/agentless-file-integrity-monitoring/create-an-agentless-fim-policy.md) to apply the rule groups to your VMs.
3. [View agentless FIM events](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/agentless-file-integrity-monitoring/view-agentless-fim-events.md) to review the file changes.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/agentless-file-integrity-monitoring/agentless-file-integrity-monitoring.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.
