Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > How File Integrity Monitor (FIM) handles actions performed on a network share

How File Integrity Monitor (FIM) handles actions performed on a network share

Created by Seamus.Enright, last modified by MindTouch on Jun 23, 2016

Views: 1,781 Votes: 2 Revisions: 7

Overview

This article describes how File Integrity Monitor (FIM) handles actions performed on a network share. 

Environment

All versions of LEM

Details

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).

 

 

 

Last modified

Tags

Classifications

Public