Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

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,891 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