Critical windows file modified

This rule is part of a beta feature. To learn more, contact Support.
This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Goal

Detect modifications of critical Windows system file.

Strategy

Various compliance frameworks, including PCI DSS, SOC, and CIS, require monitoring of critical system files and binaries. On Windows, critical system binaries are typically stored in C:\Windows\system32. This rule tracks any modifications to that directory.

Triage and response

  1. Identify which user or process changed the critical system binaries.
  2. If these changes were not authorized, and you cannot confirm the safety of the changes, roll back the host or container in question to an acceptable configuration.

Requires Agent version 7.52 or later

PREVIEWING: rtrieu/product-analytics-ui-changes