Update considerations for file integrity monitoring#535
Conversation
Added current limitation - 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.
|
@Tungsten66 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
@Tungsten66 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit d16812a: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 9c36ecb: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Adds an explicit limitation to the File Integrity Monitoring documentation so readers understand where custom path monitoring is supported.
Changes:
- Documented that custom file/directory path monitoring rules are supported only on Azure virtual machines (not Arc-connected non-Azure machines).
- Reformatted the “Considerations and limitations” section into a bullet list and preserved the existing Linux sensor Create/Modify limitation.
|
|
||
| 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. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
Added current limitation - 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.