# FIM and Windows Updates Best Practices

**URL:** <https://discuss.elastic.co/t/fim-and-windows-updates-best-practices/366415>\
**Category:** SIEM\
**Created:** [September 11, 2024, 2:04pm UTC](https://discuss.elastic.co/t/fim-and-windows-updates-best-practices/366415 "2024-09-11T14:04:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![csmith](https://avatars.discourse-cdn.com/v4/letter/c/74df32/32.png) [@csmith](https://discuss.elastic.co/u/csmith)\
**Post date:** [September 11, 2024, 2:04pm UTC](https://discuss.elastic.co/t/fim-and-windows-updates-best-practices/366415/1 "2024-09-11T14:04:26Z")

</div>

Hi all,

When using the File Integrity Module integration, is there a way to tune out expected behavior from Windows updates? Been having a lot of alerts following regular updates.

EDIT: I thought about adding an exception to the alert for TrustedInstaller but pretty sure with enough effort, attackers can act as TrustedInstaller

---

<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:** [October 9, 2024, 2:04pm UTC](https://discuss.elastic.co/t/fim-and-windows-updates-best-practices/366415/2 "2024-10-09T14:04:44Z")

</div>

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