# File Integrity Monitoring for Windows Using Elastic Agent

**URL:** https://discuss.elastic.co/t/file-integrity-monitoring-for-windows-using-elastic-agent/289476
**Category:** Endpoint Security
**Created:** [November 17, 2021, 3:46pm UTC](https://discuss.elastic.co/t/file-integrity-monitoring-for-windows-using-elastic-agent/289476 "2021-11-17T15:46:35Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![afarley](https://avatars.discourse-cdn.com/v4/letter/a/3ab097/32.png) [@afarley](https://discuss.elastic.co/u/afarley)
#### Post date: [November 17, 2021, 3:46pm UTC](https://discuss.elastic.co/t/file-integrity-monitoring-for-windows-using-elastic-agent/289476/1 "2021-11-17T15:46:35Z")

</div>

Hello all,

I have been looking into how to implement Elastic Security most effectively to meet PCI requirements and a snag I've run into with other tools is successfully implementing FIM in a Windows environment. I am not sure to what extent the Elastic agent is capable of doing this and would greatly appreciate some insight into how others have done it. I know you can utilize OSQuery to enable FIM (via iNotify) pretty easily in Linux, but OSQuery for Windows has given me plenty of trouble in the past. Any thoughts?

I am also aware you can use Beats to enable the FIM module. This question is strictly pertaining to the agent.

Thank you!

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 15, 2021, 3:46pm UTC](https://discuss.elastic.co/t/file-integrity-monitoring-for-windows-using-elastic-agent/289476/2 "2021-12-15T15:46:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
