> 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-posture-management/agentless-file-integrity-monitoring/create-an-agentless-fim-policy.md).

# Create an agentless FIM policy

Create an agentless file integrity monitoring policy that applies FIM rule groups to the cloud VMs in selected asset groups.

An agentless FIM policy applies one or more FIM rule groups to a scope of cloud VMs. Agentless FIM monitors the files and directories that the rule groups define on every VM in the policy scope.

### Prerequisites for creating an agentless FIM policy

Before you create an agentless FIM policy, make sure that you have the following:

* A Cortex Cloud role with the **Device Control: View** and **Compute Policies: View/Edit** permissions.
* At least one FIM rule group that uses the **Host** monitoring mode. For more information, see [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) for agentless FIM.
* An asset group that includes the VMs to monitor.
* To create an asset group from the policy wizard, the **Asset Groups: View/Edit** permission.
* Cloud accounts that are onboarded with ADS turned on.

### How to create an agentless FIM policy

To create an agentless FIM policy, do the following:

1. Select **Inventory** → **Endpoints** → **File Integrity Monitoring** → **Agentless policy**.
2. Click **Create policy**.
3. In **General**, enter the following information and then click **Next**:
   * **Policy name:** A name for the policy.
   * **Description:** A description of the policy.
4. In **Rules**, click **Add rule groups**.
5. Select one or more rule groups and click **Add**. Only rule groups that use the **Host** monitoring mode appear in the list.
6. Click **Next**.
7. Select one or more **Asset groups**. To see the VMs that the selected asset groups include, click **Preview**.
8. Click **Next**.
9. In the **Summary**, review the policy settings.
10. Click **Create policy**.

### Results of creating an agentless FIM policy

Cortex shows a message confirming that the policy was created. The policy appears in the **Agentless Policy** page.

ADS scans cloud VMs on a periodic basis and compares each scan with the previous one. The first scan of the VM instance establishes a baseline. Starting with the second scan, agentless FIM reports any changes detected since the previous scan.

To change the files and directories that agentless FIM monitors, edit the **Rule Groups**.

{% hint style="info" %}
**Note**: Changing the rules in a rule group restarts the baseline. The next scan records a new baseline and doesn't report events.
{% endhint %}

#### Next steps after creating an agentless FIM policy

* After at least two scans of the VMs in the policy scope, you can [View agentless FIM events](https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/agentless-file-integrity-monitoring/view-agentless-fim-events.md).
* After creating a policy, you can **Edit**, **Disable**, or **Delete** from the **Agentless Policy** list.


---

# 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-posture-management/agentless-file-integrity-monitoring/create-an-agentless-fim-policy.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.
