Netwrix Auditor Installation Configuration Guide
Netwrix Auditor Installation Configuration Guide
Installation and
Configuration Guide
Version: 8.0
5/17/2016
Legal Notice
The information in this publication is furnished for information use only, and does not constitute a
commitment from Netwrix Corporation of any features or functions, as this publication may describe
features or functionality not applicable to the product release or version you are using. Netwrix makes
no representations or warranties about the Software beyond what is provided in the License Agreement.
Netwrix Corporation assumes no responsibility or liability for the accuracy of the information presented,
which is subject to change without notice. If you believe there is an error in this publication, please report
it to us in writing.
Netwrix is a registered trademark of Netwrix Corporation. The Netwrix logo and all other Netwrix
product or service names and slogans are registered trademarks or trademarks of Netwrix Corporation.
Microsoft, Active Directory, Exchange, Exchange Online, Office 365, SharePoint, SQL Server, Windows,
and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries. All other trademarks and registered trademarks are property of
their respective owners.
Disclaimers
This document may contain information regarding the use and installation of non-Netwrix products.
Please note that this information is provided as a courtesy to assist you. While Netwrix tries to ensure
that this information accurately reflects the information provided by the supplier, please refer to the
materials provided with any non-Netwrix product and contact the supplier for confirmation. Netwrix
Corporation assumes no responsibility or liability for incorrect or incomplete information provided about
non-Netwrix products.
2016 Netwrix Corporation.
All rights reserved.
2/182
Table of Contents
1. Introduction
1.1. Netwrix Auditor Overview
2. System Requirements
7
7
10
10
12
12
12
13
14
16
16
19
19
19
20
20
20
21
23
24
33
33
34
37
43
48
50
50
3/182
51
53
54
55
67
67
70
71
72
72
73
73
4.5.3. Configure Audit Settings for CIFS File Shares on EMC VNX/ VNXe/ Celerra
74
86
86
88
91
91
4.7.1.1. Prerequisites
91
92
92
92
95
4.7.2.1. Prerequisites
96
96
98
98
102
112
113
113
4/182
113
114
115
116
118
119
122
124
124
125
126
127
127
129
129
130
132
134
135
135
137
141
141
142
143
145
146
155
155
156
156
5/182
158
159
160
161
162
5.5.10. Assign Change and Create files/Write Data Permissions to Upload Subscriptions to
File Server
162
5.5.11. Create Role on NetApp Clustered Data ONTAP 8 and Enable AD User Access
163
5.5.12. Assign Audit Logs, Mail Recipients and View-Only Configuration Admin Roles to
Account
164
165
166
167
168
170
170
172
8. Appendix
173
173
174
176
176
176
177
179
6/182
1. Introduction
This guide is intended for administrators who are going to install and configure Netwrix Auditor.
The guide provides detailed instructions on how best to deploy and set up the product to audit your IT
infrastructure. It lists all product requirements, necessary rights and permissions and guides you through
the installation and audit configuration processes.
Change auditing and alerting: Netwrix Auditor detects all configuration, content and security
changes across your entire IT infrastructure. Reports and real-time alerts include the critical who,
what, when and where details, including before and after values, enabling quick and effective
response.
AuditIntelligence interactive search: Netwrix Auditor enables you to easily search through audit
data and fine-tune sorting and filtering criteria so you can quickly hone in on exactly the information
you need.
Configuration assessment: State-in-time reports show configuration settings at any point in time,
such as group membership or password policy settings as they were configured a year ago.
Access auditing: Monitoring of and reporting on successful and failed access to systems and data
helps keep sensitive data safe.
Predefined reports and diagrams: Netwrix Auditor includes more than 150 predefined reports and
diagrams. Reports can be exported to a range of formats, including PDF and XLS, and stakeholders
can subscribe to reports to stay informed automatically by email.
7/182
AuditArchive: Netwrix Auditors scalable two-tiered storage system (file- based + SQL database)
holds consolidated audit data for more than 10 years.
Unified platform: Many vendors require multiple standalone tools that are hard to integrate, but
Netwrix Auditor is a unified platform that can audit the entire IT infrastructure.
Features
Netwrix Auditor for Active Directory detects and reports on all changes
Directory
Netwrix Auditor for Exchange detects and reports on all changes made
Exchange
Netwrix Auditor for Office 365 detects and reports on all changes made
365
Netwrix Auditor for Windows File Servers detects and reports on all
File Servers
Netwrix Auditor for EMC detects and reports on all changes made to
EMCCelerra, VNX/VNXe and Isilon storages, including modifications of
files, folders, shares and permissions, as well as failed and successful
access attempts.
8/182
Application
Features
Netwrix Auditor for NetApp detects and reports on all changes made to
NetApp Filer appliances both in cluster- and 7- modes, including
modifications of files, folders, shares and permissions, as well as failed
and successful access attempts.
Netwrix Auditor for SharePoint detects and reports on read access and
SharePoint
SQLServer
Netwrix Auditor for VMware detects and reports on all changes made to
ESX servers, folders, clusters, resource pools, virtual machines and their
virtual hardware configuration.
Netwrix Auditor for Windows Server detects and reports on all changes
Server
9/182
2. System Requirements
This section lists the requirements for the systems that are going to be audited with Netwrix Auditor, and
for the computer where the product is going to be installed. It also contains the information on the
SQLServer versions supported by the Audit Database. Refer to the following sections for detailed
information:
l
Supported Versions
Active Directory
Exchange
Exchange Online
Windows File Servers
Windows Server OS (32 and 64-bit): Windows Server 2008 SP2/2008 R2,
Windows Server 2012/2012 R2
EMC
NetApp
NetApp Clustered Data ONTAP 8.2.1 - 8.2.3, 8.3, 8.3.1, 8.3.2 (CIFS
10/182
Audited System
Supported Versions
configuration only)
SharePoint
SQLServer
VMware
Windows Server
Windows Server OS (32 and 64-bit): Windows Server 2008 SP2/2008 R2,
Windows Server 2012/2012 R2
Cisco
Cisco ASA 5500 Series Adaptive Security Appliance Software Release 8.0
DNS
Windows Server OS (32 and 64-bit): Windows Server 2008 SP2/2008 R2,
Windows Server 2012/2012 R2
Event Log
Windows Server OS (32 and 64-bit): Windows Server 2008 SP2/2008 R2,
Windows Server 2012/2012 R2
Any Linux system using Syslog (event collection rules must be created
manually)
IIS
User Activity
Windows Server OS (32 and 64-bit): Windows Server 2008 SP2/2008 R2,
Windows Server 2012/2012 R2
11/182
Hardware Requirements
Software Requirements
Deployment Options
Minimum
Recommended
Processor
RAM
2 GB
8 GB
Component
Disk space
Full installation1 TB
The disk space required for Netwrix Auditor to function properly depends on
the average number of changes per day in the audited environment, the
Audit Database location and the Long-Term Archive retention settings.
NOTE: Netwrix Auditor informs you if you are running out of space on a
system disk where the Long-Term Archive is stored by default. You
will see events in the Netwrix Auditor System Health log once the
free disk space starts approaching minimum level. When the free
disk space is less than 3 GB all Netwrix services will be stopped.
Screen resolution
Client installation200 MB
1280 x 1024
12/182
Component
Full installation
Operating system
Framework
To audit...
Exchange Online
Active Directory*
Exchange*
File Servers
SharePoint*
network
Any computer in the audited
domain or domain where
your audited system resides.
It is not recommended to
install Netwrix Auditor on a
domain controller.
NOTE: The computer where Netwrix Auditor Administrator
Console is installed must be able to access the Central
Administration website on the audited SharePoint Farm by
its name and port number.
Netwrix Auditor for SharePoint Core Service must be
installed on the computer where SharePoint Central
Administration is installed.
l
SQL Server
VMware
Windows Server*
13/182
To audit...
Cisco
DNS*
Event Log
Group Policy*
IIS
Edition
14/182
Version
Edition
The following SQLServer Reporting Services versions are supported: 2008 R2 and above.
NOTE: It is recommended to consider the maximum database size in different SQL Server versions, and
make your choice based on the size of the environment you are going to monitor, the number of
users and other factors. Note that the maximum database size in SQL Server Express editions may
be insufficient.
SQL Server is not included in the product installation package and must be installed manually or
automatically through the Audit Database Settings wizard. This wizard automatically installs SQL Server
2014 Express Edition with Advanced Services and configures Reporting Services.
For your convenience, Netwrix provides instructions on the manual installation of Microsoft SQL Server
with Advanced Services. See Install Microsoft SQL Server for more information. For full installation and
configuration details, refer to the documentation provided by Microsoft.
NOTE: If you install Netwrix Auditor on a read-only domain controller, SQL Server installation will fail (both
manual or automatic through the Audit Database Settings wizard). This is a known issue, for
details refer to the following Microsoft Knowledge base article: You may encounter problems when
installing SQL Server on a domain controller. To fix the issue, install Netwrix Auditor on another
computer, or install SQL Server manually on a different computer that can be accessed by the
product.
You can also configure Netwrix Auditor to use an existing SQL Server instance.
NOTE: If you have more than one Netwrix Auditor Server running in your network, make sure to configure
them to use different SQL Server instances. The same SQL Server instance cannot be used to store
audit data collected by several Netwrix Auditor Servers.
15/182
16/182
3. Follow the instructions of the setup wizard. When prompted, accept the license agreement.
4. On the Select Installation Type step, you will be prompted to select the installation type:
l
Full installationSelect if you are going to install Netwrix Auditor for the first time. In this case
both Netwrix Auditor Administrator Console and the Netwrix Auditor client will be installed.
Client installation Select if you have been already auditing your IT infrastructure with
Netwrix Auditor and now you want to install the client console on a remote machine to provide
access to your audit results (e.g., generate reports and search your audit data).
17/182
NOTE: Netwrix recommends to install Netwrix Auditor on a workstation, not a domain controller. See
Deployment Options for more information. But if you want to install Netwrix Auditor on a readonly domain controller anyway, prior to running the installation, perform the following steps:
1. On a writable domain controller, create the following groups using the Active Directory
Users and Computers snap-in: Netwrix Auditor Administrators and Netwrix Auditor
Client Users.
2. Add a user who is going to install Netwrix Auditor to these groups.
3. Wait for the changes to be replicated on a read-only domain controller.
18/182
Netwrix Auditor for SharePoint Core Service is going to be installed on the computer that hosts
SharePoint Central Administration in the audited SharePoint farm.
The SharePoint Administration (SPAdminV4) service is started on the target computer. See
Configure SharePoint Farm for Auditing for more information.
Is a member of the local Administrators group on SharePoint server, where the Core Service
will be deployed.
NOTE: During the Netwrix Auditor for SharePoint Core Service installation / uninstallation your SharePoint
sites may be unavailable.
19/182
Before installing Netwrix Auditor User Activity Core Service to audit user activity, make sure that:
l
The Data Processing Account has access to the administrative shares. See Configure Data Processing
Account Rights and Permissions for more information.
To install Netwrix Auditor User Activity Core Service to audit user activity
1. Navigate to %ProgramFiles% (x86)\Netwrix Auditor\User Activity Video Recording and copy the
UACoreSvcSetup.msi file to the audited computer.
2. Run the installation package.
3. Follow the instructions of the setup wizard. When prompted, accept the license agreement and
specify the installation folder.
4. On the Core Service Settings page, specify the host server (i.e., the name of the computer where
Netwrix Auditor is installed) and the server TCP port.
20/182
NOTE: Make sure that the folder is accessible from computers where the Netwrix Auditor clients are
going to be deployed. You must grant the Read permissions on this folder to these computer
accounts.
2. Copy Netwrix_Auditor_client.msi to the shared folder.
3. Right-click the newly created GPO and select Edit from the pop-up menu.
4. In the Group Policy Management Editor dialog, expand the Computer Configuration node on the
left and navigate to Policies Software Settings Software installation.
5. In the right page, right-click and select New Package.
6. In the dialog that opens, locate Netwrix_Auditor_client.msi and click Open.
21/182
8. In the Netwrix Auditor Properties dialog, select the Deployment tab and click Advanced.
9. In the Advanced Deployment Options dialog, select the Ignore language when deploying this
package checkbox.
22/182
The product will be automatically installed on computers affected by the newly created Group Policy after
reboot.
Description
/i
Run installation.
/q
Specify the user interface (UI) that displays during installation. You
can append other options, such as n to hide the UI.
install_all
1Full installation
23/182
Required configuration
Active Directory
(including Group
Policy)
The ADSI Edit utility must be installed on any domain controller in the
audited domain. See Install ADSI Edit for more information.
The following policies must be set to "Success" for the effective domain
controllers policy:
The Audit logon events policy must be set to "Success" (or "Success" and
"Failure") for the effective domain controllers policy.
The Maximum Security event log size must be set to 4GB. The retention
method of the Security event log must be set to Overwrite events as
needed.
OR
Auto archiving must be enabled to prevent audit data loss if log overwrites
occur.
24/182
Audited system
Required configuration
l
Customize the retention period for the backup logs if necessary (by default,
it is set to "50").
Exchange
The ADSI Edit utility must be installed on any domain controller in the
audited domain. See Install ADSI Edit for more information.
The following policies must be set to "Success" for the effective domain
controllers policy:
The Audit logon events policy must be set to "Success" (or "Success" and
"Failure") for the effective domain controllers policy.
The Maximum Security event log size must be set to 4GB. The retention
method of the Security event log must be set to Overwrite events as
needed.
OR
Auto archiving must be enabled to prevent audit data loss if log overwrites
occur.
In order to audit mailbox access, the Logons logging level must be set to
"Minimum" via the Exchange Management Shell.
NOTE: This is only required if you disable Netwrix Auditor Mailbox Access
Core Service when auditing mailbox access on Exchange 2007 and
2010.
In order to audit mailbox access, native audit logging must be enabled for
user, shared, equipment, linked, and room mailboxes.
l
25/182
Audited system
Required configuration
FolderBind, SendAs, SendOnBehalf, Create
Customize the retention period for the backup logs, if necessary (by default,
it is set to "50").
Exchange Online
Native audit logging must be enabled for user, shared, equipment, linked,
and room mailboxes.
l
NOTE: This is only required for auditing non-owner mailbox access within
your Exchange Online organization.
Window File
Servers
For a security principal (e.g., Everyone), the following options must be set to
"Success" and "Fail" in the Advanced Security Auditing settings for the
audited shared folders:
l
Write Attributes
Delete
Change Permissions
Take Ownership
The Audit object access policy must set to "Success" and "Failure".
The following Advanced audit policy settings can be configured if you want
to narrow the scope of events collected by the product:
l
26/182
Audited system
Required configuration
or later) security option must be enabled.
l
The Security event log maximum size must be set to 4GB. The retention
method of the Security event log must be set to Overwrite events as
needed.
EMC Isilon
27/182
Audited system
Required configuration
EMC Celerra/
VNX/VNXe
The Audit object access policy must be set to "Success" and "Failure" in the
Group Policy of the OU where the audited EMC VNX/VNXe/Celerra appliance
belongs to.
Audit settings must be configured for CIFS File Shares. For a security principal
(e.g., Everyone ), the following options must be set to "Success" and "Fail" in
the Advanced Security Auditing settings for the audited shared folders:
NetApp Filer
Write Attributes
Delete
Change Permissions
Take Ownership
Qtree Security must be configured. The volume where the audited file shares
are located must be set to the "ntfs" or "mixed" security style.
28/182
Audited system
Required configuration
events.enable and the cifs.audit.account_mgmt_
events.enable options must be set to "off".
l
cifs.audit.autosave.onsize.enable on
cifs.audit.autosave.file.extension timestamp
The Security Log shared folder must be configured if you are not going to
detect in automatically via Netwrix Auditor Administrator Console.
Audit settings must be configured for CIFS File Shares. For a security principal
(e.g., Everyone ), the following options must be set to "Success" and "Fail" in
the Advanced Security Auditing settings for the audited shared folders:
l
Write Attributes
Delete
Change Permissions
29/182
Audited system
Required configuration
l
SharePoint
Take Ownership
The Audit Log Trimming setting must be set to "Yes" and Specify the
number of days of audit log data to retain must be set to 7 days.
The SPAdminV4 service must be enabled (required for the Netwrix Auditor
Core Service for SharePoint installation).
SQL Server
No configuration is required
VMware
No configuration is required
Windows Server
(including DNS)
The Audit
Security
Group
Management,
Audit
User
Account
The Security event log maximum size must be set to 4 GB. The retention
method of the Security event log must be set to Overwrite events as
needed.
30/182
Audited system
Required configuration
l
NOTE: If the audited servers are behind the Firewall, for configuration details refer
to the following Netwrix Knowledge Base articles: How to audit servers
located in another subnet behind firewall and Ports required to monitor
servers over the firewall.
Event Log
(including Cisco)
IIS
The Remote Registry service must be running and its Startup Type must be
set to "Automatic".
Logon Activity
The following policies must be set to "Success" and "Failure" for the effective
domain controllers policy:
The Audit system events policy must be set to "Success" for the effective
domain controllers policy.
The Maximum Security event log size must be set to 4GB. The retention
method of the Security event log must be set to Overwrite events as
needed or "Archive the log when full".
31/182
Audited system
User Activity
Required configuration
l
Refer to the following topics for detailed instructions depending on the system you are going to audit:
l
32/182
Automatically through the Active Directory Audit Configuration wizard integrated in Netwrix
Auditor Administrator Console
With this wizard you can configure audit settings for Active Directory, Exchange and Group Policy. On
each step, the wizard checks your audit settings and provides a report on their current values. If any
of your current settings conflict with the configuration required for the product to function properly,
these conflicts will be listed. In this case, you can choose whether you want to adjust your audit
settings automatically and override your current settings, or if you want to configure them manually.
For detailed instructions, refer to Netwrix Auditor Administrator's Guide.
Manually. To configure your domain for auditing manually, perform the following procedures:
l
Configure Basic Domain Audit Policies or Configure Advanced Audit Policies. Either local or
advanced audit policies must be configured to track changes to accounts and groups, and to
identify workstations where changes were made.
NOTE: Netwrix recommends you to exclude read-only domain controllers from the Active Directory
auditing scope. See Netwrix Auditor Administrator Guide for more information.
33/182
1. Open the Group Policy Management console on any domain controller in the target domain:
navigate to Start Administrative Tools Group Policy Management.
2. In the left pane, navigate to Forest: <forest_name> Domains <domain_name> Domain
Controllers. Right-click the effective domain controllers policy (by default, it is the Default Domain
Controllers Policy), and select Edit from the pop-up menu.
3. In the Group Policy Management Editor dialog, expand the Computer Configuration node on the
left and navigate to Policies Windows Settings Security Settings Local Policies Audit
Policy.
4. Configure the following audit policies.
Policy
Audit Events
"Success"
"Success"
NOTE: The Audit logon events policy is only required to collect the information on the originating
workstation, i.e., the computer from which a change was made. This functionality is optional
and can be disabled. See Netwrix Auditor Administrator's Guide for more information.
5. Navigate to Start Run and type "cmd". Input the gpupdate /force command and press Enter.
The group policy will be updated.
34/182
5. Navigate to Start Run and type "cmd". Input the gpupdate /force command and press Enter.
The group policy will be updated.
35/182
DS Access
Logon/Logoff
Policy Name
l
Audit Logoff
Audit Logon
Audit Events
"Success"
"Success"
"Success"
5. Navigate to Start Run and type "cmd". Input the gpupdate /force command and press Enter.
The group policy will be updated.
36/182
3. Right-click the <domain_name> node and select Properties. Select the Security tab and click
Advanced. In the Advanced Security Settings for <domain_name> dialog, select the Auditing tab.
37/182
38/182
c. Make sure that the Apply these auditing entries to objects and/or containers within
this container only checkbox is cleared. Also, make sure that the Apply onto parameter
is set to "This object and all descendant objects".
l
39/182
40/182
41/182
c. Make sure that the Apply these auditing entries to objects and/or containers within
this container only checkbox is cleared. Also, make sure that the Apply onto parameter
is set to "This object and all descendant objects".
l
42/182
To increase the maximum size of the Security event log and set its retention method
To increase the maximum size of the Security event log and set its retention method
1. Open the Group Policy Management console on any domain controller in the target domain:
navigate to Start Administrative Tools Group Policy Management.
2. In the left pane, navigate to Forest: <forest_name> Domains <domain_name> Domain
Controllers. Right-click the effective domain controllers policy (by default, it is the Default Domain
43/182
4. In the Maximum security log size Properties dialog, select Define this policy setting and set
maximum security log size to"4194240" kilobytes (4GB).
44/182
5. Select the Retention method for security log policy. In the Retention method for security log
Properties dialog, check Define this policy and select Overwrite events as needed.
45/182
6. Navigate to Start Run and type "cmd". Input the gpupdate /force command and press Enter.
The group policy will be updated.
46/182
47/182
NOTE: If the CleanAutoBackupLogs registry value is set to "0", you will have to remove the old
automatic backups manually, or you may run out of space on your hard drive.
48/182
49/182
Automatically through the Active Directory Audit Configuration wizard integrated in Netwrix
Auditor Administrator Console
With this wizard you can configure audit settings for Active Directory, Exchange and Group Policy. On
each step, the wizard checks your audit settings and provides a report on their current values. If any
of your current settings conflict with the configuration required for the product to function properly,
these conflicts will be listed. In this case, you can choose whether you want to adjust your audit
settings automatically and override your current settings, or if you want to configure them manually.
For detailed instructions, refer to Netwrix Auditor Administrator's Guide.
Manually. You need to adjust the same audit settings as those required for auditing Active Directory.
See Configure Domain for Auditing Active Directory for more information.
If your Exchange organization is running Exchange 2010 or 2013, you must also configure the
Administrator Audit Logging (AAL)settings. If you want to audit non-owner access in addition to
Exchange auditing, configure mailbox audit. See Configure Exchange for Auditing Mailbox Access for
more information.
50/182
Exchange 2010
Set-AdminAuditLogConfig -AdminAuditLogEnabled $true AdminAuditLogAgeLimit 30 -AdminAuditLogCmdlets *
Exchange 2013
Set-AdminAuditLogConfig -AdminAuditLogEnabled $true AdminAuditLogAgeLimit 30 -AdminAuditLogCmdlets * -LogLevel Verbose
3. On the computer where Netwrix Auditor is installed, browse to the %Netwrix Auditor installation
folder%/Active Directory Auditing folder, locate the SetAALExcludedCmdlets.ps1 file and copy it to
Exchange.
4. In Exchange Management Shell, in the command line, execute this file by specifying the path to it:
<Path_To_ SetAALExcludedCmdlets_File>\SetAALExcludedCmdlets.ps1
This file contains a list of cmdlets that must be excluded from Exchange logging to reduce server
load.
51/182
Selected mailboxes
Perform the steps in the table below to start auditing your mailboxes.
Audit...
All mailboxes
Steps...
1. On the computer where the audited Exchange is installed, navigate to Start
Programs Exchange Management Shell.
NOTE: If you have already configured Netwrix Auditor to audit mailbox access,
you can find the full list of audited Exchange servers on the computer
where Netwrix Auditor resides. Navigate to C:\ProgramData\Netwrix
Auditor\Non-owner Mailbox Access Reporter for
Exchange\Default.xml
2. Execute the following command:
Get-MailboxDatabase -Server {0} | foreach { Get-Mailbox RecipientTypeDetails UserMailbox, SharedMailbox,
EquipmentMailbox, LinkedMailbox, RoomMailbox | Set-Mailbox
-AuditEnabled $true -AuditAdmin Update,Copy,Move,
MoveToDeletedItems,SoftDelete,HardDelete,FolderBind,
SendAs,SendOnBehalf,MessageBind,Create -AuditDelegate
Update,Move,MoveToDeletedItems,SoftDelete,HardDelete,
FolderBind,SendAs,SendOnBehalf,Create }
Where the {0} character must be replaced with your audited server FQDN
name (e.g., stationexchange.enterprise.local).
NOTE: If you are going to audit multiple Exchange servers, repeat these steps for
each audited Exchange.
Selected
mailbox
52/182
Audit...
Steps...
l
NOTE: If you are going to audit multiple individual mailboxes, repeat these steps for
each mailbox on each Exchange server.
Automatically when creating a Managed Object. If you select to configure audit on the target
Exchange Online automatically, your current audit settings will be checked on each data collection
and adjusted if necessary.
Manually. Special manual configuration steps only required if you are going to audit non-owner
mailbox access within your Exchange Online organization. In this case, you need to create a remote
Shell session to Exchange Online. For detailed instructions on how to create a remote session, read
the following Microsoft article: Connect to Exchange Online using remote PowerShell.
Perform the steps in the table below to start auditing mailbox access your Exchange Online organization.
To...
Audit all
mailboxes
Do...
1. On the local computer, navigate to Start Programs Windows Power
Shell.
2. Connect to your Exchange Online.
3. Execute the following command:
Get-Mailbox -RecipientTypeDetails
UserMailbox,SharedMailbox,EquipmentMailbox,LinkedMailbox,
RoomMailbox | Set-Mailbox -AuditEnabled $true AuditAdmin
Update,Copy,Move,MoveToDeletedItems,SoftDelete,HardDelete,
FolderBind,SendAs,SendOnBehalf,MessageBind,Create
AuditDelegate Update,Move,MoveToDeletedItems,SoftDelete,
HardDelete,FolderBind,SendAs,SendOnBehalf,Create
Audit selected
mailbox
53/182
To...
Do...
2. Connect to Exchange Online.
3. Execute the following command:
Set-Mailbox -Identity {0} -AuditEnabled $true AuditAdmin
Update,Copy,Move,MoveToDeletedItems,SoftDelete,HardDelete,
FolderBind,SendAs,SendOnBehalf,MessageBind,Create
AuditDelegate Update,Move,MoveToDeletedItems,SoftDelete,
HardDelete,FolderBind,SendAs,SendOnBehalf,Create
Where the {0} character must be replaced with one of the following:
l
LegacyExchangeDN. Example:
/o=EnterpriseDev/ou=Exchange Administrative Group
(FYDIBOHF23SPDLT)
/cn=Recipients/cn=97da560450c942aba81b2da46c60858aanalyst
NOTE: If you are going to audit multiple individual mailboxes, repeat these steps for
each mailbox.
54/182
If you specify a single computer name, Netwrix Auditor will audit all shared folders on this computer.
Note that Netwrix Auditor does not track content changes on folders whose name ends with the $
symbol (which are either hidden or administrative/system folders). In order for the report
functionality to work properly, you need to configure audit settings for each share folder on the
computer separately. Otherwise, reports will contain limited data and warning messages.
For your convenience, if your file shares are stored within one folder (or disk drive), you can configure
audit settings for this folder only. As a result, you will receive reports on all required access types
applied to all file shares within this folder. It is not recommended to configure audit settings for
system disks.
You can configure yourfile shares for auditing in one of the following ways:
l
Manually. To configure your file servers for auditing manually, perform the following procedures:
l
Description
Successful modifications
Commonly used option to track important data. Helps find out who
created, modified, moved, renamed or removed files and when these
changes were done.
Used to track suspicious activity on your file server. Helps find out who
tried to change or delete files, etc., but failed to do it. Investigate
incidents with AuditIntelligence and figure out why that user tried to do
it.
Successful reads
55/182
Access Type
Description
privileged users only. Browse your audit data in the Netwrix Auditor
client and discover who accessed important files besides your trusted
users.
NOTE: Netwrix recommends not to enable this option for frequently
used files in public shares as it will lead to logging a great many
read events in your Audit Database.
Used to track suspicious activity. Helps find out who was trying to read
files, but failed to do it. Investigate your incidents with AuditIntelligence
and figure out why that user tried to do it.
NOTE: Netwrix recommends not to enable this option for frequently
used files in public shares as it will lead to logging a great many
read events in your Audit Database.
56/182
4. In a separate Advanced Security Settings for <Share_Name> dialog, click Add to add a principal.
You can select Everyone (or another user-defined group containing users that are granted special
permissions) and click Edit.
NOTE: You can specify any other user group, but in this case Netwrix Auditor will send emails with
warnings on incorrect audit configuration. This will not affect the reports or data searches
performed in the Netwrix Auditor client and the product will only audit user accounts that
belong to the selected group.
5. Apply settings to your Auditing Entries depending on the access types that you want to audit. If you
want to audit all access types (successful reads, modifications as well as failed reads and modification
attempts), you need to add separate Auditing Entries for each file share. Otherwise, reports will
contain limited data and warning messages. Review the following for additional information:
l
Successful reads
Successful modifications
57/182
Auditing Entry
Successful reads
The Auditing Entry below shows Advanced Permissions for auditing successful reads only:
Make sure that the Apply these auditing entries to objects and/or containers within this
container only checkbox is cleared.
Successful modifications
The Auditing Entry below shows Advanced Permissions for auditing successful modifications only:
58/182
Auditing Entry
Write attributes
Delete
Change permissions
Take ownership
Make sure that the Apply these auditing entries to objects and/or containers within this
container only checkbox is cleared.
59/182
Auditing Entry
Failed read attempts
The Auditing Entry below shows Advanced Permissions for auditing failed read attempts only:
Make sure that the Apply these auditing entries to objects and/or containers within this
container only checkbox is cleared.
Failed modification attempts
The Auditing Entry below shows Advanced Permissions for auditing failed modification attempts
only:
60/182
Auditing Entry
Write attributes
Delete
Change permissions
Take ownership
Make sure that the Apply these auditing entries to objects and/or containers within this
container only checkbox is cleared.
61/182
NOTE: If no data is present in reports, or the Who field contains the "system" value, refer to Netwrix
Knowledge Base articles.
4. Click Add to add a new principal. You can select Everyone (or another user-defined group containing
users that are granted special permissions) and click Edit.
5. In the Auditing Entry for <Folder_Name> dialog, click the Select a principal link and specify
Everyone.
NOTE: You can specify any other user group, but in this case Netwrix Auditor will send emails with
warnings on incorrect audit configuration. The product will audit only user accounts that
belong to the selected group.
6. Apply settings to your Auditing Entries depending on the access types that you want to audit. If you
want to audit all access types (successful reads, modification as well as failed read and modification
attempts), you need to add separate Auditing Entries for each file share. Otherwise, reports will
contain limited data and warning messages. Review the following for additional information:
62/182
Successful reads
Successful modifications
The Auditing Entry below shows Advanced Permissions for auditing successful reads only:
TypeSet to "Success".
Make sure that the Only apply these auditing settings to objects and/or containers
within this container checkbox is cleared.
Successful modifications
The Auditing Entry below shows Advanced Permissions for auditing successful modifications only:
63/182
Auditing Entry
TypeSet to "Success".
Advanced permissions:
Write attributes
Delete
Change permissions
Take ownership
Make sure that the Only apply these auditing settings to objects and/or containers
within this container checkbox is cleared.
Failed read attempts
The Auditing Entry below shows Advanced Permissions for auditing failed read attempts:
64/182
Auditing Entry
TypeSet to "Fail".
Make sure that the Only apply these auditing settings to objects and/or containers
within this container checkbox is cleared.
Failed modification attempts
The Auditing Entry below shows Advanced Permissions for auditing failed read and modification
attempts:
65/182
Auditing Entry
TypeSet to "Fail".
Advanced permissions:
Write attributes
Delete
Change permissions
Take ownership
Make sure that the Only apply these auditing settings to objects and/or containers
within this container checkbox is cleared.
NOTE: If no data is present in reports, or the Who field contains the "system" value, refer to Netwrix
Knowledge Base articles.
66/182
Policy Name
Audit Events
Audit Policy
To configure advanced audit policy on Windows Server 2008 R2 / Windows 7 and above
67/182
68/182
To configure advanced audit policy on Windows Server 2008 R2 / Windows 7 and above
In Windows Server 2008 R2 and Windows 7 and above, Advanced audit policies are integrated with Group
Policies, so they can be applied via Group Policy Object or Local Security Policies. The procedure below
describes how to apply Advanced policies via Local Security Policy console.
1. On the audited server, open the Local Security Policy snap-in: navigate to Start Administrative
Tools Local Security Policy.
2. In the left pane, navigate to Security Settings Advanced Audit Policy Configuration System
Audit Policies Object Access.
3. Configure the following audit policies.
Policy Name
l
Audit Events
"Success" and/or "Failure" depending on the
type of events you want to track.
NOTE: You can check your current effective settings by executing the following command:
auditpol /get /category:"Object Access".
69/182
70/182
2. In the Services dialog, locate the Remote Registry service, right-click it and select Properties.
3. In the Remote Registry Properties dialog, make sure that the Startup type parameter is set to
"Automatic" and click Start.
71/182
4. In the Services dialog, ensure that Remote Registry has the "Started" (on pre-Windows Server 2012
versions) or the "Running" (on Windows Server 2012 and above) status.
72/182
Automatically when creating a Managed ObjectPartially. Only audit settings for file shares will be
configured. If you select to automatically configure audit in the target environment, your current
audit settings will be periodically checked and adjusted if necessary.
NOTE: This method is recommended for evaluation purposes in test environments.
Manually. To configure EMC Celerra/VNX/VNXe for auditing, perform the following procedures:
l
Configure Security Event Log Maximum Size to avoid overwriting of the security logs; it is
recommended to set security log size to a maximum (4GB).
By default, the security log is set to overwrite events that are older than 10 days, and its size is
set to 512 KB. The default location for the security.evt log is C:\security.evt , which
corresponds to the root partition of the Data Mover. To be able to increase the security log size,
you must move it from the Data Mover root folder.
Configure Audit Object Access Policy. Set the Audit object access policy set to "Success" and
"Failure" in the Group Policy of the OU where your EMC VNX/VNXe/Celerra appliance belongs
to. For more information on VNX/VNXe/Celerra GPO support, refer to documentation provided
by EMC.
Configure Audit Settings for CIFS File Shares on EMC VNX/ VNXe/ Celerra
73/182
1. Open the Group Policy Management console on any domain controller in the target domain:
navigate to Start Administrative Tools Group Policy Management.
2. In the left pane, navigate to Forest: <forest_name> Domains <domain_name>, right-click
<OU_name> and select Create a GPO in this domain and Link it here.
3. Enter the name for the new GPO.
4. Right-click the newly created GPO and select Edit.
5. In the Group Policy Management Editor dialog, expand the Computer Configuration node on the
left and navigate to Policies Windows Settings Security Settings Local Policies Audit
Policy.
Policy Subnode
Policy Name
Audit Events
Audit Policy
"Success"and"Failure"
6. Navigate to Start Run and type "cmd". Input the gpupdate /force command and press Enter.
The group policy will be updated.
Description
Successful modifications
Commonly used option to track important data. Helps find out who
created, modified, moved, renamed or removed files and when these
74/182
Access Type
Description
changes were done.
Used to track suspicious activity on your file server. Helps find out who
tried to change or delete files, etc., but failed to do it. Investigate
incidents with AuditIntelligence and figure out why that user tried to do
it.
Successful reads
Used to track suspicious activity. Helps find out who was trying to read
files, but failed to do it. Investigate your incidents with AuditIntelligence
and figure out why that user tried to do it.
NOTE: Netwrix recommends not to enable this option for frequently
used files in public shares as it will lead to logging a great many
read events in your Audit Database.
To configure audit settings for the CIFS file shares, perform the following procedure on the audited file
share:
l
To configure audit settings for the CIFS file shares from computers running pre-Windows Server
2012 versions
To configure audit settings for the CIFS file shares from computers running Windows Server 2012
and above
To configure audit settings for the CIFS file shares from computers running pre-Windows Server 2012
versions
1. Navigate to the target file share, right-click it and select Properties.
2. In the <Share_Name> Properties dialog, select the Security tab and click Advanced.
3. In the Advanced Security Settings for <Share_Name> dialog, navigate to the Auditing tab, click
Edit.
75/182
4. In a separate Advanced Security Settings for <Share_Name> dialog, click Add to add a principal.
You can select Everyone (or another user-defined group containing users that are granted special
permissions) and click Edit.
NOTE: You can specify any other user group, but in this case Netwrix Auditor will send emails with
warnings on incorrect audit configuration. This will not affect the reports or data searches
performed in the Netwrix Auditor client and the product will only audit user accounts that
belong to the selected group.
5. Apply settings to your Auditing Entries depending on the access types that you want to audit. If you
want to audit all access types (successful reads, modifications as well as failed reads and modification
attempts), you need to add separate Auditing Entries for each file share. Otherwise, reports will
contain limited data and warning messages. Review the following for additional information:
l
Successful reads
Successful modifications
76/182
Auditing Entry
Successful reads
The Auditing Entry below shows Advanced Permissions for auditing successful reads only:
Make sure that the Apply these auditing entries to objects and/or containers within this
container only checkbox is cleared.
Successful modifications
The Auditing Entry below shows Advanced Permissions for auditing successful modifications only:
77/182
Auditing Entry
Write attributes
Delete
Change permissions
Take ownership
Make sure that the Apply these auditing entries to objects and/or containers within this
container only checkbox is cleared.
78/182
Auditing Entry
Failed read attempts
The Auditing Entry below shows Advanced Permissions for auditing failed read attempts only:
Make sure that the Apply these auditing entries to objects and/or containers within this
container only checkbox is cleared.
Failed modification attempts
The Auditing Entry below shows Advanced Permissions for auditing failed modification attempts
only:
79/182
Auditing Entry
Write attributes
Delete
Change permissions
Take ownership
Make sure that the Apply these auditing entries to objects and/or containers within this
container only checkbox is cleared.
80/182
NOTE: If no data is present in reports, or the Who field contains the "system" value, refer to Netwrix
Knowledge Base articles.
To configure audit settings for the CIFS file shares from computers running Windows Server 2012 and
above
1. Navigate to the target file share, right-click it and select Properties.
2. In the <Share_Name> Properties dialog, select the Security tab and click Advanced.
3. In the Advanced Security Settings for <Share_Name> dialog, navigate to the Auditing tab.
4. Click Add to add a new principal. You can select Everyone (or another user-defined group containing
users that are granted special permissions) and click Edit.
5. In the Auditing Entry for <Folder_Name> dialog, click the Select a principal link and specify
Everyone.
NOTE: You can specify any other user group, but in this case Netwrix Auditor will send emails with
warnings on incorrect audit configuration. The product will audit only user accounts that
belong to the selected group.
6. Apply settings to your Auditing Entries depending on the access types that you want to audit. If you
want to audit all access types (successful reads, modification as well as failed read and modification
attempts), you need to add separate Auditing Entries for each file share. Otherwise, reports will
81/182
contain limited data and warning messages. Review the following for additional information:
l
Successful reads
Successful modifications
The Auditing Entry below shows Advanced Permissions for auditing successful reads only:
TypeSet to "Success".
Make sure that the Only apply these auditing settings to objects and/or containers
within this container checkbox is cleared.
Successful modifications
The Auditing Entry below shows Advanced Permissions for auditing successful modifications only:
82/182
Auditing Entry
TypeSet to "Success".
Advanced permissions:
Write attributes
Delete
Change permissions
Take ownership
Make sure that the Only apply these auditing settings to objects and/or containers
within this container checkbox is cleared.
Failed read attempts
The Auditing Entry below shows Advanced Permissions for auditing failed read attempts:
83/182
Auditing Entry
TypeSet to "Fail".
Make sure that the Only apply these auditing settings to objects and/or containers
within this container checkbox is cleared.
Failed modification attempts
The Auditing Entry below shows Advanced Permissions for auditing failed read and modification
attempts:
84/182
Auditing Entry
TypeSet to "Fail".
Advanced permissions:
Write attributes
Delete
Change permissions
Take ownership
Make sure that the Only apply these auditing settings to objects and/or containers
within this container checkbox is cleared.
NOTE: If no data is present in reports, or the Who field contains the "system" value, refer to Netwrix
Knowledge Base articles.
85/182
Using the configure_ifs.sh shell script that comes with Netwrix Auditor. See To configure EMCIsilon
cluster in Normal and Enterprise mode via shell script for more information.
Manually. See To configure EMC Isilon cluster in Normal and Enterprise mode manually for more
information.
To configure EMCIsilon cluster in Normal and Enterprise mode via shell script
1. On the computer where Netwrix Auditor Administrator Console resides, navigate to C:\Program Files
(x86)\Netwrix Auditor\File Server Auditing and copy the configure_ifs.sh shell script to /ifs/data catalog
on your cluster.
2. Navigate to your cluster command prompt through the SSH connection.
3. Log in to your cluster as a root user.
4. Run the shell script by executing the following command:
sh /ifs/data/configure_ifs.sh -z zone1 -a 15
where
zone1 is the name of the audited access zone on your file server.
15 is a combination of the bitwise flags. The table below shows the example combination of 4 flags:
Successful modifications
Successful reads
Total:
15
86/182
Execute command...
Successful modifications
Audit Success:
l
write
delete
set_security
rename
Failed modification
attempts
Audit Failure:
l
create
write
87/182
To enable filter...
l
delete
set_security
rename
Successful reads
Execute command...
Audit Failure:
l
create
read
7. Create the "netwrix_audit" role and add the required privileges to this role. For example:
isi auth roles create --name=netwrix_audit
isi auth roles modify netwrix_audit --add-priv-ro="ISI_PRIV_LOGIN_PAPI,ISI_
PRIV_AUTH,ISI_PRIV_AUDIT,ISI_PRIV_IFS_BACKUP"
isi auth roles modify netwrix_audit --add-group="BUILTIN\Administrators"
Using the configure_ifs.sh shell script that comes with Netwrix Auditor. See To configure EMCIsilon
cluster in Compliance mode via shell script for more information.
Manually. See To configure EMCIsilon cluster in Compliance mode manually for more information.
88/182
zone1 is the name of the audited access zone on your file server.
15 is a combination of the bitwise flags. The table below shows the example combination of 4 flags:
Successful modifications
Successful reads
Total:
15
5. Create a shared folder named netwrix_audit$ on a system zone. This folder points to /ifs:
isi smb shares create --name=netwrix_audit$ --path=/ifs/ --zone=system -browsable=true
6. Add the BUILTIN\Administrators group in the share permissions for netwrix_audit$ folder with
"full access" rights:
isi smb shares permission create --share=netwrix_audit$ -group=BUILTIN\Administrators --permission-type=allow --permission=full -zone=system
7. Grant your Data Processing Account "read access" rights to the catalog /ifs/.ifsvar/audit :
isi zone modify system --add-user-mapping-rules="Enterprise\Administrator
++ compadmin [group]"
Where Enterprise\Administrator is your Data Processing Account name.
89/182
Execute command...
Successful modifications
Audit Success:
l
write
delete
set_security
rename
Failed modification
attempts
Audit Failure:
l
create
write
delete
set_security
rename
Successful reads
Audit Failure:
l
create
read
7. Create the "netwrix_audit" role and add the required privileges to this role. For example:
isi auth roles create --name=netwrix_audit
isi auth roles modify netwrix_audit --add-priv-ro="ISI_PRIV_LOGIN_PAPI,ISI_
PRIV_AUTH,ISI_PRIV_AUDIT,ISI_PRIV_IFS_BACKUP"
isi auth roles modify netwrix_audit --add-group="BUILTIN\Administrators"
90/182
Manually. To configure your NetApp appliance for auditing, perform the following procedures:
l
Configure NetAppData ONTAP 7 and 8 in 7-mode for Auditing or Configure NetApp Clustered
Data OnTap 8 for Auditing
Prerequisites
4.7.1.1. Prerequisites
NOTE: CIFS must be set up on your NetApp filer in advance.
The instructions in this section apply to the default VFiler. To audit several VFiler instances, you must
perform these configuration steps for each of them.
NOTE: Currently, Netwrix Auditor can be configured to audit non-default VFiler using HTTP only.
The following commands are used:
l
91/182
Tree
-------
------
---- ------
vol0
vol0
--------
vol1
Vol2
apphost01>
legacy
httpd.admin.enable
off
httpd.admin.hostsequiv.enable off
httpd.admin.max_connections
512
httpd.admin.ssl.enable
on
httpd.admin.top-page.authentication on
apphost01>
92/182
cifs.audit.autosave.onsize.enable on
cifs.audit.autosave.file.extension timestamp
3. Disable the cifs.audit.liveview.enable option since it interferes with the normal Security log
behavior and prevents Netwrix Auditor from processing audit data properly.
4. To set up old logs deletion, you can configure the cifs.audit.autosave.file.limit option by
specifying the maximum number of files to be stored, or set retention in Netwrix Auditor.
5. Perform any test actions with a file share to ensure the log is created.
Make sure there is enough disk space allotted to the security logs archives. Depending on the file access
activity, audit data may grow rapidly, and the location specified for the security log (and security log auto
archives) must be large enough to hold data until it is processed by Netwrix Auditor (by default, data
collection runs every 24
hours).
To set up
93/182
94/182
6. NOTE: If the CleanAutoBackupLogs registry value is set to "0", you will have to remove the old logs
manually, or you may run out of space on your hard drive.
Mount Point
Description
----
-----------
-----------
ETC$
/etc
Remote Administration
C$
/vol/vol0/shares/share1
everyone / Full Control
3. Perform any test actions with a file share to ensure the log is created.
Prerequisites
95/182
4.7.2.1. Prerequisites
Netwrix assumes that you are aware of Clustered Data ONTAP basic installation and configuration steps. If
not, refer to the following administration and management guides.
Clustered Data ONTAP
Related documentation
version
Clustered Data ONTAP 8.2
Perform the steps below before proceeding with Clustered Data ONTAP configuration:
1. Configure CIFSserver and make sure it functions properly.
NOTE: NFS file shares are not supported.
2. Configure System Access Control List (SACL) on your file share. See Configure Audit Settings for CIFS
File Shares for more information.
3. Set the Security Style for Volume or Qtree where the audited file shares are located to the "ntfs" or
"mixed".
4. Configure audit manually. Review the Auditing NAS events on SVMs with FlexVol volumes section
in Clustered Data ONTAP 8.3 File Access Management Guide for CIFS.
NOTE: The current version of Netwrix Auditor do not supports auditing of Infinite Volumes.
96/182
vserver
Vserver
Type
Service
Name
Description
Enabled
----------
-------
--------
-----------------------
------
ontapi
true
vs1
data
Support
4. Enable HTTP/HTTPS access. For example:
cluster1::> vserver services web modify -vserver vs1 -name ontapi -enabled true
5. Enable only SSL access (HTTPS in Netwrix Auditor Administrator Console). For example:
cluster1::> vserver services web modify -vserver vs1 -name ontapi -enabled true -ssl-o
nly true
6. Make sure that the builtin vsadmin role or a custom role (e.g., fsa_role) assigned to your Data
Processing Account can access ONTAPI. For example:
cluster2::> vserver services web access show -vserver vs2
Vserver
Type
Service Name
Role
--------------
-------
------------
---------------
vs2
data
ontapi
fsa_role
vs2
data
ontapi
vsadmin
vs2
data
ontapi
vsadmin-protocol
vs2
data
ontapi
vsadmin-readonly
vs2
data
ontapi
vsadmin-volume
97/182
Enabled
Logging
------------
------------
-------
cluster1-01
true
false
3. If firewall disabled, complete the configuration. If not, allow HTTP/HTTPS. For example:
cluster1::> system services firewall policy modify -policy pol1 -service
http -action allow -ip-list 192.168.1.0/24
cluster1::> system services firewall policy modify -policy pol1 -service
https -action allow -ip-list 192.168.1.0/24
where pol1 is your Firewall policy name and -ip-list 192.168.1.0/24 is your subnet where
Netwrix Auditor Administrator Console resides.
98/182
Setting
Auditing State
true
file-ops
NOTE: Only required if you use ONTAP 8.3.
You cannot select event categories if
you use Clustered Data ONTAP 8.2.
Log Format
"XML"or "EVTX"
99/182
100/182
6. NOTE: If the CleanAutoBackupLogs registry value is set to "0", you will have to remove the old logs
manually, or you may run out of space on your hard drive.
101/182
3. Review the list of available file shares on your SVM. For example:
vs1::> vserver cifs share show
Vserver
Share
Path
Properties
Comment
ACL
--------- -----------------
vs1
admin$
browsable
vs1
c$
oplocks
BUILTIN\Administrators
/ Full Control
browsable
changenotify
vs1
ipc$
browsable
4. Perform any test actions with a file share to ensure the log is created.
Description
Successful modifications
Commonly used option to track important data. Helps find out who
created, modified, moved, renamed or removed files and when these
changes were done.
Used to track suspicious activity on your file server. Helps find out who
tried to change or delete files, etc., but failed to do it. Investigate
incidents with AuditIntelligence and figure out why that user tried to do
it.
Successful reads
Used to track suspicious activity. Helps find out who was trying to read
files, but failed to do it. Investigate your incidents with AuditIntelligence
and figure out why that user tried to do it.
NOTE: Netwrix recommends not to enable this option for frequently
used files in public shares as it will lead to logging a great many
read events in your Audit Database.
102/182
To configure audit settings for the CIFS file shares from computers running pre-Windows Server
2012 versions
To configure audit settings for the CIFS file shares from computers running Windows Server 2012
and above
To configure audit settings for the CIFS file shares from computers running pre-Windows Server 2012
versions
1. Navigate to the root share folder, right-click it and select Properties.
2. In the <Share_Name> Properties dialog, select the Security tab and click Advanced.
NOTE: If there is no such tab, it means a wrong security style has been specified for the volume
holding this file share.
3. In the Advanced Security Settings for <Share_Name> dialog, navigate to the Auditing tab, click
Edit.
4. In a separate Advanced Security Settings for <Share_Name> dialog, click Add to add a principal.
You can also select Everyone (or another user-defined group containing users that are granted
special permissions) and click Edit.
103/182
NOTE: You can specify any other user group, but in this case Netwrix Auditor will send emails with
warnings on incorrect audit configuration. This will not affect the Reports functionality and
the product will only audit user accounts that belong to the selected group.
5. Apply settings to your Auditing Entries depending on the access types that you want to audit. If you
want to audit all access types (successful reads, modifications as well as failed reads and
modifications attempts), you need to add three separate Auditing Entries for each file share.
Otherwise, reports will contain limited data and warning messages. Review the following for
additional information:
l
Successful reads
Successful modifications
The Auditing Entry below shows Advanced Permissions for auditing successful reads only:
104/182
Auditing Entry
l
Make sure that the Apply these auditing entries to objects and/or containers within this
container only checkbox is cleared.
Successful modifications
The Auditing Entry below shows Advanced Permissions for auditing successful modifications only:
Write attributes
105/182
Auditing Entry
Delete
Change permissions
Take ownership
Make sure that the Apply these auditing entries to objects and/or containers within this
container only checkbox is cleared.
Failed read attempts
The Auditing Entry below shows Advanced Permissions for auditing failed read attempts only:
Make sure that the Apply these auditing entries to objects and/or containers within this
container only checkbox is cleared.
106/182
Auditing Entry
Failed modification attempts
The Auditing Entry below shows Advanced Permissions for auditing failed modification attempts
only:
Write attributes
Delete
Change permissions
107/182
Auditing Entry
l
Take ownership
Make sure that the Apply these auditing entries to objects and/or containers within this
container only checkbox is cleared.
To configure audit settings for the CIFS file shares from computers running Windows Server 2012 and
above
1. Navigate to the root shared folder, right-click it and select Properties.
2. In the <Share_Name> Properties dialog, select the Security tab and click Advanced.
NOTE: If there is no such tab, it means a wrong security style has been specified for the volume
holding this file share. See Configure Audit Settings for CIFS File Shares for more information.
3. In the Advanced Security Settings for <Share_Name> dialog, navigate to the Auditing tab, click
Edit.
4. Click Add to add a new principal. You can also select Everyone (or another user-defined group
containing users that are granted special permissions) and click Edit.
5. In the Auditing Entry for <Folder_Name> dialog, click the Select a principal link and specify
Everyone.
108/182
NOTE: You can specify any other user group, but in this case Netwrix Auditor will send emails with
warnings on incorrect audit configuration. In this case, the product will only monitor user
accounts that belong to the selected group.
6. Apply settings to your Auditing Entries depending on the access types that you want to audit. If you
want to audit all access types (successful reads, modification as well as failed reads and modifications
attempts), you need to add three separate Auditing Entries for each file share. Otherwise, reports will
contain limited data and warning messages. Review the following for additional information:
l
Successful reads
Successful modifications
The Auditing Entry below shows Advanced Permissions for auditing successful reads only:
TypeSet to "Success".
Make sure that the Only apply these auditing settings to objects and/or containers
within this container checkbox is cleared.
109/182
Auditing Entry
Successful modifications
The Auditing Entry below shows Advanced Permissions for auditing successful modifications only:
TypeSet to "Success".
Advanced permissions:
Write attributes
Delete
Change permissions
Take ownership
Make sure that the Only apply these auditing settings to objects and/or containers
within this container checkbox is cleared.
110/182
Auditing Entry
Failed read attempts
The Auditing Entry below shows Advanced Permissions for auditing failed read attempts:
TypeSet to "Fail".
Make sure that the Only apply these auditing settings to objects and/or containers
within this container checkbox is cleared.
Failed modification attempts
The Auditing Entry below shows Advanced Permissions for auditing failed read and modification
attempts:
111/182
Auditing Entry
TypeSet to "Fail".
Advanced permissions:
Write attributes
Delete
Change permissions
Take ownership
Make sure that the Only apply these auditing settings to objects and/or containers
within this container checkbox is cleared.
112/182
Automatically when creating a Managed Object. If you select to configure audit in the target
SharePoint farm automatically, your current audit settings will be checked on each data collection
and adjusted if necessary.
Also, after collecting data from site collections, Netwrix Auditor will trim events older than 1 day.
Set Automatically trim the audit log for this site to "Yes".
In Specify the number of days of audit log data to retain set retention to 7 days.
NOTE: You may keep the existing audit log retention provided that it is set to 7 days or less.
113/182
1. On the computer where SharePoint Central Administration is installed and where you intend to
deploy Netwrix Auditor for SharePoint Core Service, open the Services Management Console.
Navigate to Start Administrative Tools Services.
2. Locate the SharePoint Administration service (SPAdminV4), right-click it and select Properties.
3. In the General tab, set Startup type to "Automatic" and click Apply.
4. Click Start to start the service.
114/182
2. In the Services dialog, locate the Remote Registry service, right-click it and select Properties.
3. In the Remote Registry Properties dialog, make sure that the Startup type parameter is set to
"Automatic" and click Start.
115/182
4. In the Services dialog, ensure that Remote Registry has the "Started" (on pre-Windows Server 2012
versions) or the "Running" (on Windows Server 2012 and above) status.
5. Locate the Windows Management Instrumentation service and repeat these steps.
Set Value
Create Subkey
Delete
Write DAC
Write Owner
To configure Windows registry audit settings on Windows Server 2012 and above
Set Value
Create Subkey
Delete
Write DAC
Write Owner
116/182
7. Repeat the same steps for the HKEY_LOCAL_MACHINE\SYSTEM and HKEY_USERS\.DEFAULT keys.
To configure Windows registry audit settings on Windows Server 2012 and above
1. On your target server, open Registry Editor: navigate to Start Run and type "regedit".
2. In the registry tree, expand the HKEY_LOCAL_MACHINE key, right-click SOFTWARE and select
Permissions from the pop-up menu.
3. In the Permissions for SOFTWARE dialog, click Advanced.
4. In the Advanced Security Settings for SOFTWARE dialog, select the Auditing tab and click Add.
5. Click Select a principal link and specify the Everyone group in the Enter the object name to
select field.
6. Set Type to "Success" and Applies to to "This key and subkeys".
7. Click Show advanced permissions and select the following access types:
l
Set Value
Create Subkey
Delete
Write DAC
Write Owner
117/182
8. Repeat the same steps for the HKEY_LOCAL_MACHINE\SYSTEM and HKEY_USERS\.DEFAULT keys.
Services
Windows registry
Scheduled tasks
You can also configure advanced audit policies for same purpose. See Configure Advanced Audit Policies
for more information.
NOTE: There are several methods to configure local audit policies, and this guide covers just one of them.
Consider the possible impact on your environment and select the method that best suits your
purposes. Note that if you follow the procedures below, audit settings will be applied to the whole
domain.
118/182
Audit Events
"Success"
"Success"
7. Navigate to Start Run and type "cmd". Input the gpupdate /force command and press Enter.
The group policy will be updated.
119/182
Services
Windows registry
Scheduled tasks
To configure advanced audit policies on Windows Server 2008 R2 / Windows Vista and above
120/182
Audit Registry
121/182
To configure advanced audit policies on Windows Server 2008 R2 / Windows Vista and above
In Windows Server 2008 R2 and Windows 7 and above, Advanced audit policies are integrated with Group
Policies, so they can be applied via Group Policy Object or Local Security Policies. The procedure below
describes how to apply Advanced policies via Local Security Policy console.
1. On the audited server, open the Local Security Policy snap-in: navigate to Start Administrative
Tools Local Security Policy.
2. In the left pane, navigate to Security Settings Advanced Audit Policy Configuration System
Audit Policies.
3. Configure the following audit policies.
Policy Subnode
Account
Management
Object Access
Policy Name
l
Audit Registry
Audit Events
"Success"
"Success"
122/182
123/182
124/182
2. In the Services dialog, locate the Remote Registry service, right-click it and select Properties.
3. In the Remote Registry Properties dialog, make sure that the Startup type parameter is set to
"Automatic" and click Start.
125/182
4. In the Services dialog, ensure that Remote Registry has the "Started" (on pre-Windows Server 2012
versions) or the "Running" (on Windows Server 2012 and above) status.
To configure a Syslog daemon to redirect events for Red Hat Enterprise Linux 5
1. Open the /etc/syslog.conf file.
2. Add the following line: authpriv.* @FQDN/Netbios name or authpriv.* @ComputerIP.
NOTE: FQDN/Netbios name and ComputerIP must be the name and IP address of the computer
where Netwrix Auditor is installed.
3. Navigate to the /etc/sysconfig/syslog file.
126/182
Automatically through the Active Directory Audit Configuration wizard integrated in Netwrix
Auditor Administrator Console
With this wizard you can configure audit settings for Active Directory, Exchange and Group Policy. On
each step, the wizard checks your audit settings and provides a report on their current values. If any
of your current settings conflict with the configuration required for the product to function properly,
these conflicts will be listed. In this case, you can choose whether you want to adjust your audit
settings automatically and override your current settings, or if you want to configure them manually.
For detailed instructions, refer to Netwrix Auditor Administrator's Guide.
Manually. You need to adjust the same audit settings as those required for auditing Active Directory.
See Configure Domain for Auditing Active Directory for more information.
127/182
128/182
Manually. To configure your domain manually for auditing Logon Activity, perform the following
procedures:
l
Audit Events
"Success"
129/182
5. Navigate to Start Run and type "cmd". Input the gpupdate /force command and press Enter.
The group policy will be updated.
130/182
audit policy category settings and make sure that policy setting is set to "Enabled".
5. Navigate to Start Run and type "cmd". Input the gpupdate /force command and press Enter.
The group policy will be updated.
Logon/Logoff
Policy Name
l
Audit Logoff
Audit Logon
Audit Events
"Success" and
"Failure"
"Success"
"Success" and
"Failure"
System
"Success"
131/182
5. Navigate to Start Run and type "cmd". Input the gpupdate /force command and press Enter.
The group policy will be updated.
132/182
4. In the Maximum security log size Properties dialog, select Define this policy setting and set
maximum security log size to"4194240" kilobytes (4GB).
5. Select the Retention method for security log policy. In the Retention method for security log
133/182
Properties dialog, check Define this policy and select Overwrite events as needed.
6. Navigate to Start Run and type "cmd". Input the gpupdate /force command and press Enter.
The group policy will be updated.
134/182
NOTE: Before configuring computers, make sure that the User Activity Core Service is installed on the
audited computers. See Install Netwrix Auditor User Activity Core Service for more information.
The Windows Management Instrumentation and the Remote Registry services are running and
their Startup Type is set to "Automatic". See To check the status and startup type of Windows
services for more information.
The File and Printer Sharing and the Windows Management Instrumentation features are
allowed to communicate through Windows Firewall. See To allow Windows features to communicate
through Firewall for more information.
Local TCP Port 9004 is opened for inbound connections on the computer where Netwrix Auditor is
installed. This is done automatically on the product installation.
Local TCP Port 9003 is opened for inbound connections on the audited computers. See To open
Local TCP Port 9003 for inbound connections for more information.
Remote TCP Port 9004 is opened for outbound connections on the audited computers. See To open
Remote TCP Port 9004 for outbound connections for more information.
135/182
3. Check that the Startup Type is set to "Automatic". If it is not, double-click the service. In the Remote
Registry Properties dialog, in the General tab, select "Automatic" from the drop-down list.
4. Perform the steps above for the Windows Management Instrumentation service.
Setting
Rule Type
Program
Program
Action
Profile
Applies to Domain
Name
5. Double-click the newly created rule and open the Protocols and Ports tab.
6. In the Protocols and Ports tab, complete the steps as described below:
l
136/182
Setting
Rule Type
Program
Program
Action
Profile
Applies to Domain
Name
5. Double-click the newly created rule and open the Protocols and Ports tab.
6. In the Protocols and Ports tab, complete the steps as described below:
l
Microsoft Internet Explorer 7.0 and above must be installed and ActiveX must be enabled.
Internet Explorer security settings must be configured properly. See To configure Internet Explorer
security settings for more information.
Internet Explorer Enhanced Security Configuration (IE ESC) must be disabled. See To disable Internet
Explorer Enhanced Security Configuration (IE ESC) for more information.
The user must belong to the Netwrix Auditor Client Users group that has access to the Netwrix_
137/182
UAVR$ shared folder where video files are stored. Both the group and the folder are created
automatically by Netwrix Auditor. See To add an account to Netwrix Auditor users for more
information.
l
A dedicated codec must be installed. This codec is installed automatically on the computer where
Netwrix Auditor is deployed, and on the monitored computers. To install it on a different computer,
download it from http:/www.Netwrix.com/download/ScreenPressorNetwrix.zip.
The Ink and Handwriting Services , Media Foundation , and Desktop Experience Windows
features must be installed on the computer where Netwrix Auditor Administrator Console is
deployed. These features allow enabling Windows Media Player and share video recordings via DLNA.
See To enable Windows features for more information.
138/182
To enable JavaScript
1. In Internet Explorer, navigate to Tools Internet Options.
2. Switch to the Security tab and select Internet. Click Custom Level.
3. In the Security Settings Internet Zone dialog, scroll down to Scripting and make sure Active
scripting is set to "Enable".
If Netwrix Auditor Administrator Console is installed on Windows Server 2012 and above:
1. Navigate to Start Server Manager.
2. In the Server Manager window, click Add roles and features.
3. On the Select Features step, select the following Windows features:
l
Media Foundation
139/182
Microsoft article: Fix Windows corruption errors by using the DISM or System Update
Readiness tool.
4. Restart your computer to complete features installation.
140/182
Description
Netwrix Auditor
administrator
A user who can run the Netwrix Auditor client, perform searches on
audit data and generate reports.
See Configure Netwrix Auditor User Rights and Permissions for more
information.
account
141/182
Members of the local Netwrix Auditor Client Users group on the computer where Netwrix Auditor
Server resides. See To add an account to Netwrix Auditor users for more information.
Granted the Browser role on the Report Server/specific reports on the Report Server. See To assign
the Browser role to a user for more information.
Granted the Read permission on file shares where report subscriptions will be saved. See To assign
Read permission on a shared folder where report subscriptions will be stored for more information.
NOTE: Report subscriptions are saved to file shares\Netwrix Auditor host under the Default Data
Processing Account, but users who are going to access them must be granted read access to
these shares. It is recommended to create a dedicated folder and grant access to the entire
Netwrix Auditor Client Users group.
It is recommended to grant read access only to those employees who deal with data collected across all
audited systems, such as IT managers, security officers and internal auditors. Granting read permissions to
a significant number of employees may lead to uncontrollable audit data distribution.
142/182
Navigate to...
All reports
On the Home page, navigate to Folder Settings and click New Role
Assignment (the path can slightly vary depending on your SQL
Server version).
Reports on a certain
audited system
Folder Settings, select the Security tab and click Edit Item
Security and then New Role Assignment.
Specific reports
3. Specify an account in the following format: domain\user. The account must belong to the same
domain where Netwrix Auditor is installed, or to a trusted domain.
4. Select Browser.
To assign Read permission on a shared folder where report subscriptions will be stored
NOTE: The procedure below applies to Windows Server 2012 R2 and may vary slightly depending on your
OS.
1. Navigate to a folder where report subscriptions will be stored, right-click it and select Properties.
2. In the <Share_Name> Properties dialog, select the Sharing tab and click Advanced Sharing.
3. In the Advanced Sharing dialog, click Permissions.
4. In the Permissions for <Share_Name> dialog, add accounts one for one or specify the Netwrix
Auditor Client Users group, then check the Allow flag next to Read.
143/182
4. Click Search next to Login Name and specify the user that you want to assign the db_owner role to.
5. Select Server roles on the left and assign the dbcreator role to the new login.
6. Select the User Mapping tab. Select all databases used by Netwrix Auditor to store audit data in the
upper pane and check db_owner in the lower pane.
NOTE: If the account that you want to assign the db_owner role to has been already added to SQL
Server Logins, expand the Security Logins node, right-click the account, select Properties
from the pop-up menu, and edit its roles.
144/182
145/182
The Log on as a batch job policy must be defined for this accountis
applied automatically
If event logs autobackup is enabled: the Share Read and Write permissions
and the Security Full control permissions for the logs backup folder
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
file servers under the Default Data Processing Account.
146/182
Audited system
Exchange
The Log on as a batch job policy defined for this accountis applied
automatically
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
file servers under the Default Data Processing Account.
Exchange Online
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
147/182
Audited system
Windows File
Servers
Audit logs
Mail Recipients
View-Only Configuration
The Log on as a batch job policy must be defined for this account
The Manage auditing and security log policy must be defined for this
account on a file server
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
file servers under the Default Data Processing Account.
EMC Isilon
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
148/182
Audited system
The Read permissions on to the folder where audit events are logged
(/ifs/.ifsvar/audit/)
readonly
Auth (ISI_PRIV_AUTH)
readonly
Audit (ISI_PRIV_AUDIT)
readonly
Backup (ISI_PRIV_IFS_BACKUP)
readonly
NOTE: An account used to connect to a cluster put into compliance mode must
comply with some specific requirements.
EMC Celerra/
VNX/VNXe
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
file servers under the Default Data Processing Account.
149/182
Audited system
NetApp Filer
The Log on as a batch job policy must be defined for this account
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
file servers under the Default Data Processing Account.
login-http-admin
api-vfiler-list-info
api-volume-get-root-name
api-system-cli
api-options-get
cli-cifs
version
readonly
volume
readonly
vserver audit
readonly
all
readonly
150/182
Audited system
SharePoint
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
file servers under the Default Data Processing Account.
Required for the automatic installation of Netwrix Auditor for SharePoint Core
Service:
l
SQL Server
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
151/182
Audited system
VMware
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
file servers under the Default Data Processing Account.
Windows Server
(including DNS)
The Manage auditing and security log policy must be defined for this
account
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
file servers under the Default Data Processing Account.
Event Log
(including Cisco,
IIS)
The Log on as a batch job policy must be defined for this account
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
152/182
Audited system
Group Policy
The Log on as a batch job policy defined for this accountis applied
automatically
If event logs autobackup is enabled: the Share Read and Write permissions
and the Security Full control permissions for the logs backup folder
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
file servers under the Default Data Processing Account.
Inactive Users in
Active Directory
The Log on as a batch job policy must be defined for this account
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
Logon Activity
The account must belong to one of the following domain groups: Backup
153/182
Audited system
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
file servers under the Default Data Processing Account.
Password
Expiration in
Active Directory
The Log on as a batch job policy must be defined for this account
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
User Activity
The Write permission on the folder where the Long-Term Archive is going to
be stored (by default C:\ProgramData\Netwrix Auditor\Data)
The Change share permission and the Create files / Write data folder
permission on file shares where report subscriptions will be saved
NOTE: Subscriptions created in the Netwrix Auditor client are uploaded to
file servers under the Default Data Processing Account.
Follow the procedures below to configure some basic Data Processing Account rights and permissions:
l
154/182
Assign Change and Create files/Write Data Permissions to Upload Subscriptions to File Server
Create Role on NetApp Clustered Data ONTAP 8 and Enable AD User Access
Assign Audit Logs, Mail Recipients and View-Only Configuration Admin Roles to Account
155/182
3. Double-click the Log on as a batch job policy, and click Add User or Group. Specify the account
that you want to define this policy for.
156/182
4. Click Search next to Login Name and specify the user that you want to assign the sysadmin role to.
5. Specify the Server roles tab and assign the sysadmin role to the new login.
1. On the computer where audited SQL Server instance is installed, navigate to Start All Programs
Microsoft SQL Server SQL Server Management Studio.
2. Connect to the server.
3. In the left pane, expand the Security node. Right-click the Logins node and select New Login from
the pop-up menu.
157/182
4. Click Search next to Login Name and specify the user that you want to assign the sysadmin role to.
5. Specify the Server roles tab and assign the sysadmin role to the new login.
158/182
where deleted_object_dn is the distinguished name of the deleted directory object and user_
or_ group is the user or group for whom the permission applies, and Permissions is the
permission to grant.
For example, dsacls "CN=Deleted Objects,DC=Corp,DC=local" /G Corp\jsmith:LCRP
In this example, the user CORP\jsmith has been granted List Contents and Read Property
permissions for the Deleted Objects container in the corp.local domain. These permissions let this
user view the contents of the Deleted Objects container, but do not let this user make any changes
to objects in this container. These permissions are equivalent to the default permissions that are
granted to the Domain Admins group.
1. Log on to any domain controller in the target domain with a user account that is a member of the
Domain Admins group.
2. Navigate to Start Run and type "cmd".
3. Input the following command: dsacls <deleted_object_dn> /takeownership
where deleted_object_dn is the distinguished name of the deleted directory object.
For example: dsacls "CN=Deleted Objects,DC=Corp,DC=local" /takeownership
4. To grant permission to view objects in the Deleted Objects container to a user or a group, type the
following command: dsacls <deleted_object_dn> /G <user_or_group>:<Permissions>
where deleted_object_dn is the distinguished name of the deleted directory object and user_
or_ group is the user or group for whom the permission applies, and Permissions is the
permission to grant.
For example, dsacls "CN=Deleted Objects,DC=Corp,DC=local" /G Corp\jsmith:LCRP
In this example, the user CORP\jsmith has been granted List Contents and Read Property
permissions for the Deleted Objects container in the corp.local domain. These permissions let this
user view the contents of the Deleted Objects container, but do not let this user make any changes
to objects in this container. These permissions are equivalent to the default permissions that are
granted to the Domain Admins group.
159/182
menu.
3. Click Add and enter the name of the user that you want to grant permissions to.
4. Check Allow next to the Read permission.
NOTE: If for some reason you do not want this account to belong to the Organization
Management group, you can add it to the Records Management group in the same way.
The Records Management group is less powerful, and accounts belonging to it have fewer
rights and permissions.
160/182
1. Navigate to Start Active Directory Users and Computers on any domain controller in the root
domain of the forest where Microsoft Exchange 2010 or 2013 is installed.
2. In the left pane, navigate to <domain_name> Microsoft Exchange Security Groups.
3. On the right, locate the Organization Management group and double-click it.
4. In the Organization Management Properties dialog that opens, select the Members tab and click
Add.
NOTE: If for some reason you do not want this account to belong to the Organization
Management group, you can add it to the Records Management group in the same way.
The Records Management group is less powerful, and accounts belonging to it have fewer
rights and permissions.
161/182
162/182
1. Navigate to a folder where report subscriptions will be stored, right-click it and select Properties.
2. In the <Share_Name> Properties dialog, select the Sharing tab and click Advanced Sharing.
3. In the Advanced Sharing dialog, click Permissions.
4. In the Permissions for <Share_Name> dialog, select a principal or add a new, then check the Allow
flag next to Change.
5. Apply settings and return to the <Share_Name> Properties dialog.
6. In the <Share_Name> Properties dialog, select the Security tab and click Advanced.
7. In the Advanced Security Settings for <Share_Name> dialog, navigate to the Permissions tab,
select a principal and click Edit, or click Add to add a new one.
8. Apply the following settings to your Permission Entry.
l
NOTE: Report subscriptions are saved to file shares\Netwrix Auditor host under the Default Data
Processing Account, but users who are going to access them must be granted read access to these
shares. It is recommended to create a dedicated folder and grant access to the entire Netwrix
Auditor Client Users group.
version
readonly
163/182
volume
readonly
vserver audit
readonly
all
readonly
164/182
Option
Description
Name
Description
Write scope
Roles
Members
Audit Logs
Mail Recipients
View-Only Configuration
NOTE: If you already configured specific role scopes for role groups (for example, multiple
management role scopes or exclusive scopes) using Shell, you cannot assign new roles to
these role groups via Exchange admin center. For detailed instructions on how to configure
roles using Shell, read the following Microsoft article: Manage role groups.
For your convenience, Netwrix provides a special shell script for configuring an audited EMCIsilon cluster
and granting necessary privileges to the account that is used to collect audit data. Depending on your
cluster operation mode, review the following sections:
l
To configure EMCIsilon cluster in Normal and Enterprise mode via shell script
If, for some reasons, you want to configure Data Processing Account for EMC Isilon manually, you need to
perform all steps for manual audit configuration, otherwise the product will not function properly. See the
following sections for more information:
l
165/182
Applicable to Netwrix Auditor 7.0, 7.1, and 8.0 (upgrade within the same version).
No special upgrade procedures are requiredsimply install Netwrix Auditor8.0. During installation your
Netwrix Auditor configuration and data will be preserved.
l
166/182
Upgrade scenario
Applicable to Netwrix Auditor 7.0 or 7.1 previously upgraded from 6.5 or below.
NOTE: Upgrade from Netwrix Auditor 6.5 and below to 7.0 is a mandatory procedure, otherwise the
product will not work. For detailed instructions on how to migrate to Netwrix Auditor 7.0, see
Netwrix Auditor Installation and Configuration Guide 7.0 Upgrade from Previous Versions.
Since you have already performed migration while upgrading to 7.0, refer to a simple upgrade
procedure (upgrade through installation). Also, it is necessary to transfer your old audit data (6.5 and
below) to the Long-Term Archive-compatible format using the Netwrix AuditArchive Migration Tool.
l
167/182
OR
l
5. Enter your license details when asked or you can do it later in Netwrix Auditor Administrator
Console under the License node.
6. In the dialog that opens, click Apply.
As Non-Owner Mailbox Access Auditing tool upgrades data collection will continue with the latest changes,
Change Summaries will come on the old schedule.
168/182
NOTE: Depending on the amount of your Netwrix Auditor 6.5 audit data, migration may take a while
to complete. You can minimize the AuditArchive Migration Tool screen and keep working
with Netwrix Auditor.
Once migration completes, you will see a message with migration status successful or with
warnings/errors.
169/182
Auditing\adcr.exe
where <domain name> is the name of the monitored domain in the FQDN format.
NOTE: if any argument contains spaces, use double quotes.
Example:
"C:\Program Files\Netwrix\Active Directory Auditing\adcr.exe"
/removecompressionservice domain=domain.local
3. To delete Compression Services from a specific domain controller, execute the following command:
Netwrix_ Auditor_ installation_ folder \Active Directory
/removecompressionservice d=<domain controller name>
Auditing\adcr.exe
170/182
171/182
Remove the Netwrix Auditor User Activity Core Service manually on each audited computer:
1. Navigate to Start Control Panel Programs and Features.
2. Select Netwrix Auditor User Activity Core Service and click Uninstall.
172/182
8. Appendix
This section contains instructions on how to install the third-party components that are not included in the
Netwrix Auditor installation package, but are required for the product to function properly.
Refer to the following sections for step-by-step instructions on how to:
l
173/182
2. Navigate to Start Control Panel Programs and Features Turn Windows features on or
off.
3. Navigate to Remote Server Administration Tools Feature Administration Tools and select
Group Policy Management Tools.
4. Click Install.
To install ADSI Edit on Windows Server 2008 and Windows Server 2008 R2
1. Navigate to Start Control Panel Programs Programs and Features Turn Windows
features on or off.
2. In the Server Manager dialog, select Features in the left pane, click Add Features.
3. Navigate to Remote Server Administration Tools Role Administration Tools and select AD DS
and AD LDS Tools .
4. Click Next to proceed to the confirmation page.
5. Click Install to enable it.
174/182
175/182
176/182
values, click Change Database and complete the Report Server Database Configuration wizard.
5. In the Reporting Services Configuration Manager left pane, select Report Manager URL. Make
sure Virtual Directory is set correctly, and that the URL is valid.
TCP 135
TCP 9004
UDP 514
NOTE: You do not need to open any additional ports on computers where Netwrix Auditor clients are
installed.
If you are running Windows Firewall on the computer where Netwrix Auditor Administrator Console is
going to be installed, these ports will be opened automatically for inbound connections after Netwrix
Auditor installation. If you use a third-party firewall, you must create rules for inbound connections
manually.
NOTE: Before installing Netwrix Auditor, make sure that the Windows Firewall service is started.
On the Protocol and Ports step, select TCP. In the Specific local ports field specify "135".
177/182
On the Profile step, make sure that the rule applies to all profiles (Domain, Private, Public).
On the Name step, specify the rule's name, for example Netwrix Auditor TCP port 135
Access.
6. Repeat these steps and create inbound rules for the UDP 514 and TCP 9004 ports.
178/182
Exchange 50
Index
Active Directory
Office 365 53
Audit settings
Advanced audit policy 34
Auto archiving 46
Local audit policies 33
Objec-level auditing for Configuration
and Schema partitions 40
Objec-level auditing for Domain
partition 37
SharePoint 112
User Activity 135
Windows file servers 54
Windows Server 114
Core Service 19
Manually install for SharePoint 19
Manually install for User Activity 19
D
Data Processing Account 146
Audit Logs role 161
Deleted Objects Container 158
EMC Isilon role and privileges 165
Audit, configure 24
AuditArchive
179/182
Group Policy
Audit settings 127
EMC Celerra
Audit settings
Audit object access policy 73
I
IIS
Configure audit 127
Inactive Users in Active Directory
Configure audit 86
Compliance mode 88
Non-compliance mode 86
Rights and permissions 146
Install
ADSI Edit 174
Core Service for SharePoint 19
Environment 10
Event Log
Deployment options 13
Audit settings
GPMC 173
Ports 177
IIS 127
Silent mode 23
Exchange
Audit settings 50
AAL 50
Logon Activity
Configure Audit 53
180/182
System requirements 10
NetApp Filer
Uninstall
Services 170
Event categories 92
Qtree security 92
Rights and permissions 150
O
Upgrade
Within the same product version 167
User Activity
Account rights and permissions 154
Audit settings
Overview 7
P
Password Expiration in Active Directory
Rights and permissions 154
R
Roles 141
Administator 141
IE ESC 139
V
VMware
Rights and permissions 152
User 142
S
SharePoint
Audit settings 112
SQL Server
Rights and permissions 151
SSRS service account
Content Manager role 145
Supported SQL Server versions 14
181/182
Windows Server
Audit settings
Advanced policies settings 119
Event log size and retention 122
Firewall rules 124
Local audit policies 118
Remote registry service 115
Windows registry 116
Rights and permissions 152
182/182