Security Compliance
How File Integrity Monitor (FIM) handles actions performed on a network share in SEM
This article provides additional information that will be useful when configuring the SEM FIM (File Integrity Monitor) feature for use with a network share.
First published date
Last published date
Overview
Product section
Resolution
The current version of KD (SWFsFltr.sys v1.1.0.12) handles actions performed on network share in a following way:
|
Action |
SourceAccount in invoked event |
|
FILE Create |
User which performed action |
|
FILE Read |
NT AUTHORITY \ SYSTEM |
|
FILE Write |
User & NT AUTHORITY \ SYSTEM (one event from user + several from System)** !IMPORTANT: some applications invoke SYSTEM user events only! |
|
FILE Delete |
User which performed action |
|
DIR Create |
User which performed action |
|
DIR Delete |
User which performed action |
|
DIR Read* |
NT AUTHORITY \ SYSTEM |
|
Permissions (ACL) Read |
User & NT AUTHORITY \ SYSTEM |
|
Permissions (ACL) Write |
User which performed action |
|
Metadata Read |
User & NT AUTHORITY \ SYSTEM |
|
Metadata Write |
User which performed action Note: "Meta writes" follow "File writes" closely, use this to keep track of username when only SYSTEM user'ed "File writes" are generated by OS |
Notes:
- DIR Read events received by setting File Read op in Connector.
- Depending on the application used to update file, some tend to invoke at least one user addressed events (notepad++), others spawn SYSTEM exclusively (e.g paint).