Skip to content

Update considerations for file integrity monitoring #535

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Tungsten66 wants to merge 2 commits into
base: public
Choose a base branch
from
Open

Update considerations for file integrity monitoring #535

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d16812a
Update considerations for file integrity monitoring
Tungsten66 Jul 10, 2026
9c36ecb
Merge branch 'public' into patch-5
Tungsten66 Jul 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions defender-for-cloud/file-integrity-monitoring-enable-defender-endpoint.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,8 +143,8 @@ Disable as follows:

## Considerations and limitations

The current Linux sensor doesn't distinguish between Create and Modify actions.
It identifies both as Modify actions. As a result, when a new file is created, the event is logged as a Modify event rather than a Create event.
- Custom file and directory path monitoring rules are currently supported only for Azure virtual machines. Custom path monitoring isn't supported for non-Azure machines connected through Azure Arc.
- The current Linux sensor doesn't distinguish between Create and Modify actions. It identifies both as Modify actions. As a result, when a new file is created, the event is logged as a Modify event rather than a Create event.

## Related content

Expand Down
Loading