Go Up
You are here: AdministrationMonitoring PlansAdd Items for MonitoringWindows File Share

Windows File Share

Complete the following fields:

Option Description
General

Specify Windows file share

Provide UNC path to a shared resource. See the section below for special considerations.

NOTE: Do not specify a default file share mapped to a local drive (e.g., \\Server\e$).

Specify the account for collecting data

Select the account that will be used to collect data for this item. If you want to use a specific account (other than the one you specified during monitoring plan creation), select Custom account and enter credentials. The credentials are case sensitive.

NOTE: A custom account must be granted the same permissions and access rights as the default account used for data collection. See Data Collecting Account for more information.

Scope

Specify monitoring restrictions

Specify restriction filters to narrow your monitoring scope (search results, reports and Activity Summaries). All filters are applied using AND logic.

Refer to Configure Scope for detailed instructions on how to narrow your monitoring scope.

TIP: In addition to the restrictions for a monitoring plan, you can use the *.txt files to collect more granular audit data. Note that the new monitoring scope restrictions apply together with previous exclusion settings configured in the *.txt files. Review the following for more information: Exclude Objects from Monitoring Scope

Configure Scope

You can narrow your monitoring scope by adding exclusions.

Click Add Exclusion, then in the Specify Filters dialog do the following:

  1. Provide the path to the file share where you are going to exclude some audit data. Use the path format as it appears in the "What" column of reports and Activity Summaries — for example, \\corpsrv\shared.

    NOTE: You can use a wildcard (*) only if you need to exclude user activity on this file share. For other data types (state-in-time or all data) wildcards are not supported. This refers to the specified shared folder, its subfolders and files.

  2. Select what type of data you want to exclude:

    Option Description Example
    All Data

    Select if you want to completely exclude the specified file share from being audited.

    The product will not collect any user activity or state-in-time data.

    NOTE: In this case,Netwrix Auditor does not adjust audit settings automatically for the selected folders.

    A Security Officer wants to monitor a file share but s/he does not have access to a certain folder on this share. Thus, s/he configures the product not to monitor this folder at all.
    State-in-Time Select to configure Netwrix Auditor to exclude data for the state-in-time reports from the monitoring scope. A Security Officer wants to monitor a file share, but it contains a folder with a huge amount of objects, so s/he does not want Netwrix Auditor to collect state-in-time data for this folder.
    User Activity

    Select to exclude actions performed by specific users on the selected file share. See the procedure below for details.

    NOTE: In this case, the product still collects stat-in-time data for this share.

    A Security Officer wants to monitor a file share that contains a public folder for which s/he does not want to collect Read operations.

    To exclude specific user activity:

    1. Specify what user accounts should be excluded:

      • All Users — select to exclude the activity of any user on the file share you specified.
      • These users — select to exclude specific users' activity. Provide user names as shown in the "Who" column in reports and Activity Summaries, e.g., MyDomain\user1. To enter multiple accounts, use comma as a separator.
    2. Specify what actions should be excluded:

      • All actions — exclude all actions of the selected users
      • These actions: — use the drop-down list to select the actions to exclude, e.g. Added and Moved.

After configuring all filters, click Add to save them and return to the item settings.

Working with DFS File Shares

Netwrix Auditor supports auditing of DFS and clustered file servers if Object Access Auditing is enabled on DFS file shares or on every cluster node.

  • When adding a cluster file server for auditing, it is recommended to specify a server name of the Role server or a UNC path of the shared folder located on the Role server.
  • When adding a DFS file share for auditing, specify a Windows file share item and provide the UNC path of the whole namespace or UNC path of the DFS link (folder). For example:
    • "\\domain\dfsnamespace\" (domain-based namespace) or "\\server\dfsnamespace\" (in case of stand-alone namespace);
    • "\\domain\dfsnamespace\link" (domain-based namespace) or "\\server\dfsnamespace\link" (in case of stand-alone namespace).
  • For recommendations on configuring DFS replication, refer to this Knowledge Base article.

Working with Mount Points

You can specify a mount point as a monitored item. However, consider the following:

  • If a mount point represents a shared folder, then the objects in its root will be initially collected by Netwrix Auditor and appear as processed by System account. Wait for the next data collections - then all actions for these objects will be monitored in a normal way.
  • To monitor the mount points targeted at the subfolder of a file share, provide network path to the target subfolder.

Go Up