DatAdvantage 6.3 User Guide
DatAdvantage 6.3 User Guide
3
User Guide
Publishing Information
Software version 6.3.160
Document version 9
Publication date May 22, 2017
Chapter 4: Getting Started..................................................................................................................................... 38
Starting DatAdvantage........................................................................................................................................ 38
DatAdvantage's Graphical User Interface..................................................................................................... 38
DatAdvantage Views....................................................................................................................................... 41
Menus and Toolbar.........................................................................................................................................42
DatAdvantage Status Bar.............................................................................................................................. 44
Displaying the DatAdvantage Legend.......................................................................................................44
Keyboard Shortcuts......................................................................................................................................... 47
Closing DatAdvantage........................................................................................................................................ 52
Chapter 5: Common Activities.............................................................................................................................. 53
Setting User Interface Display Options..........................................................................................................53
Switching Views.................................................................................................................................................... 53
Selecting Resources............................................................................................................................................ 54
Showing and Hiding Window Panes.............................................................................................................. 56
Using the Current Active Entity List................................................................................................................56
Using the Directory Services Search Dialog Box........................................................................................57
Using the Directory Picker Dialog Box.......................................................................................................... 58
Navigating Directories and Files......................................................................................................................59
Searching for Directories and Files............................................................................................................59
Understanding Logical and Physical Views.............................................................................................59
Focusing on Directories and Files by View State..................................................................................62
Viewing the Tree According to Permission Types................................................................................ 64
Grouping Exchange Entities......................................................................................................................... 64
Showing and Hiding Management Indicators......................................................................................... 66
Showing and Hiding Deduplication Indicators........................................................................................66
Viewing Columns in the Directories Pane............................................................................................... 66
Filtering Directories and Files...................................................................................................................... 67
Clearing Filters................................................................................................................................................. 68
Navigating User and Group Lists.................................................................................................................... 68
Reloading User or Group Information....................................................................................................... 69
Arranging Users and Groups....................................................................................................................... 69
Filtering User and Group Lists.....................................................................................................................70
Switching between Parent and Child Views.............................................................................................71
Viewing Users and Groups According to Permission Types...............................................................73
Selecting Display Name Settings for Users or Groups......................................................................... 73
Showing or Hiding Managed Group Indicators.......................................................................................74
Showing or Hiding Inactivity Indicators.....................................................................................................75
Showing or Hiding Excluded from IDU Analytics Indicators................................................................75
Editing the Displayed Columns................................................................................................................... 76
Selecting Organizational Units..................................................................................................................... 77
Moving Users and Groups to the Top of the List.................................................................................. 79
Searching for Users or Groups....................................................................................................................79
Viewing Azure Active Directory Objects in the Users & Groups Pane.............................................79
Managing Ownership and Custodianship...................................................................................................... 81
About Uploading Owners...............................................................................................................................81
Assigning Owners, Custodians and Entities Throughout the System...............................................84
With Varonis DatAdvantage, organizations can see, understand and manage who is using data, to
control data access and enforce compliance with data usage policies to meet business needs.
Varonis DatAdvantage addresses the growing need for regulating data usage within organizations,
enabling full visibility and accountability of data usage across legal, financial, data security,
intellectual property and data privacy requirements.
Terminology
The following terms are used with regard to DatAdvantage:
Term Definition
ACE Access control entry. A list or table containing entries that specify
individual user or group rights to specific system objects, such as
a program, a process, or a file.
Base folder The root managed folder. A storage folder that is managed by
one or more data owners. Can only be defined by administrators.
Contains managed directories.
Term Definition
Behavioral profile A collection of the standard metadata that Varonis gathers for all
users and their activities in the computing environment. When this
metadata is accumulated over the course of several months, user
behavior analysis (UBA) can identify atypical user behavior, which
may indicate malicious intent.
Distinguished An object that has effectively different permissions than its parent
unique directory permissions. Both unique and distinguished unique objects are
or file marked with the standard unique icons.
Domain local A domain local group is a security or distribution group that can
group contain universal groups, global groups, other domain local
groups from its own domain, and accounts from any domain in
the forest. You can give domain local security groups rights and
permissions on resources that reside only in the same domain in
which the domain local group is located.
End-user account All accounts that are not service, computer or group accounts.
Can be: Admin, executive or user accounts.
Term Definition
Existing User/ Describes the users and groups that currently exist in the
Group Active Directory environment. This information comes from
existing entities in Active Directory, and represents actual group
membership and nested groups.
Global group A global group is a group that can be used in its own domain,
in member servers and in workstations of the domain, and in
trusting domains. In all those locations, you can give a global
group rights and permissions and the global group can become
a member of local groups. However, a global group can contain
user accounts that are only from its own domain.
Owner A user who can view and manage all actions regarding the
application and the entities assigned to him or her.
POSIX ACLs ACLs that comply with the POSIX specifications for user and
software interfaces to an operating system.
Probe A server that monitors file servers for file events, and records the
data in a SQL database. The Probe also scans the file structure of
the target file server. One probe is capable of monitoring multiple
servers for events.
Protected A protected directory or file does not inherit any permissions from
directory or file its parent directory. The entity's icon is decorated with a lock.
Term Definition
User All accounts that are not computer or group accounts. Can be:
Admin, executive, service or end-user accounts.
A file system object may have an ACL that is the same as that
of its parent, even though there is no conventional inheritance
relationship between the objects and the parent is marked as
unique. DatAdvantage marks such an object as unique-equal, to
indicate the identical ACLs. The other unique folders, which are
not unique-equal, are marked as distinguished unique.
Term Definition
Target Audience
This user guide is intended for the following users:
• System Administrators managing the organization's Active Directory and file servers
• Help Desk operators managing users and permissions
• IT management
• Compliance and finance users - Users who need to apply access policies as well as obtain
forensic information on past activity
• Security analysts
Related Documentation
• Metadata Framework Filters
• Metadata Framework Installation Prerequisites and Requirements
• Metadata Framework Installation Guide
• Metadata Framework Release Notes
• Metadata Framework Reports
By collecting actual data usage information, the File Server Probe provides coverage of what data
is currently available to users across an unlimited number of users and data, as well as what data
is actually being accessed and used, for full and accurate usage visibility.
The File Server Probe is completely transparent to system operations. All data collection
processes are continuously monitored, and terminated immediately if performance degradation is
detected, ensuring completely non-intrusive probing.
EMC Celerra NAS Collects file server event information through Windows
auditing.
EMC Celerra CEPA Collects file server event information through the event
enabler framework.
EMC Isilon Collects file server event information through the event
enabler framework.
MS File Server Collects file server event information through MS- IFS (file
server filter).
Sun Solaris Collects file server event information through the Varonis
driver.
Along with other methods designed to streamline data governance, the Probe's event collection
mechanism handles events as follows:
• Events gathered for the same entity made by the same user at the same time are filtered, so
that only one event is recorded in the system.
• Events are aggregated on a daily basis, so that the Event Count displays the number of times
the same event occurred (with the first and last times at which it occurred).
The Directory Service Probe is completely transparent to system operations. All event collection
processes are continuously monitored, and terminated immediately if performance degradation is
detected, ensuring completely non-intrusive probing.
Note: Due to standard Microsoft behavior, Modify events may be recorded for all the fields
in a modified object, not only those that were changed. In addition, when a directory service
object is created, many Create and Modify events are recorded on the object's fields.
The Metadata Framework supports only auditing of directory service events. The DCF does not
support probing directory services.
The Directory Service Probe collects event information through a combination of the Microsoft
directory service audit feature combined with the DC's security log.
IDU Server
The IDU Server is a database that provides Active Directory data and recommendations from IDU
Analytics. It also contains information used by the DatAdvantage user interface (UI), including data
about Probes and file servers, and roles for users accessing DatAdvantage.
DatAdvantage data collection receives data from the monitored sources (such as EMC CEPA) as
they send them, dependent on the mechanism associated with the data source. This mechanism
is outside the control of DatAdvantage (e.g., EMC CEPA typically sends events some seconds after
they occur, or when its buffer is full).
While these events are stored in tables on the Varonis Probes as they are received, they are
not immediately visible in the user interface. They are made available after several database
processing and transfer jobs are run (scheduled to run nightly by default). These jobs can be
triggered manually, if necessary.
In general, DatAdvantage collects and normalizes all events. Within a one-day period, all events of
a discrete type (Open, Create, Modify, etc.), generated by a discrete user, on a discrete object (file,
folder, email message, etc.) appear in the user interface. Duplicate events - those events occurring
on the same day and whose type, user, and object are identical - are displayed as increments
to a counter, "Event Count." All events are aggregated on a daily basis, so that the Event Count
displays the number of times the same event occurred (with the first and last times at which it
occurred).
Note: Temporary events are those associated with objects that are created and deleted
within a "count-time frame" (default is 5 minutes).
• Duplicate Open, Modify and Set Security (i.e., change permissions, or chmod) events occurring
within the same minute are omitted, so that only one event is recorded in the system. The one-
minute time frame is determined based on real time between seconds 0-59.
• A buffer of 10 events (the default) is maintained and checked against various event filtering
patterns. If no events in the buffer match an event filtering pattern, the buffer is emptied and
the events are sent to the Probe without being filtered.
Bidirectional Clustering
DatAdvantage performs bidirectional clustering on both data and users. It thereby creates
multilevel classifications to deliver a full understanding of data usage, automatically eliciting what
data belongs to whom and what data is actually needed to meet specific business objectives.
Using a robust set of profiling criteria, DatAdvantage continuously maps data-user relationships,
tracking changes in behavior over time so that administrators can dynamically match user
classification and access control with data usage compliance needs. DatAdvantage provides a set
of recommendations based on very accurate behavioral analysis, allowing access control to be
aligned with the business needs.
IDU Analytics
DatAdvantage IDU Analytics intelligently aggregates and clusters data events and directory
structure information to accurately profile and classify data usage. DatAdvantage automatically
maps data to users, and vice versa, making sense of data usage patterns to provide an
understanding of data owners and who should be accessing data while pinpointing potential data
usage risks.
DatAdvantage Management
DatAdvantage Management is a user interface (UI) for managing all aspects of data usage across
the enterprise, including risk assessment, permission management, auditing and reporting.
Risk Assessment
DatAdvantage maps actual data usage with users to automatically analyze and evaluate data risks,
highlighting potential mismatches between sensitive data and permissions and recommending
classification changes, based on true usage behavior. With DatAdvantage, administrators can
accurately profile data and users, creating accurate classifications to ensure access control and
usage compliance.
Permission Management
DatAdvantage enables centralized updating of permissions, streamlining access control
management and ensuring enforcement across an unlimited number of nested users, data
sensitivity levels and business processes.
The Windows operating system has evolved quite a bit over the past several versions. Unlike
early iterations, it now provides a number of advanced features that, in providing a rich user
experience, may occasionally cause DatAdvantage to return false positives - that is, DatAdvantage
may indicate a particular user has accessed a file even though the user believes he has not done
so.
Some examples of these advanced features, primarily available in Windows Vista and higher,
include:
• Content search
• Thumbnail views
• Preview panes
False positives occur because Windows Explorer must actually open a file's data stream and peek
inside to enable the advanced OS features mentioned above. Whether the user purposely opens
a file or Windows Explorer does it for him during a content search, the file is, in fact, accessed and
the event is recorded as such by DatAdvantage.
• Enterprise Manager - Has full control over the DatAdvantage environment, including all required operations.
• Power User - Can edit and manipulate changes on the admin set, and after reviewing them, commit them to the actual environment.
• System Administrator - Maintain DatAdvantage through its configuration window. Cannot edit or commit changes on the actual data.
• User - The most basic role within DatAdvantage, a regular user can only view data.
• While all roles can view entities in DatAdvantage, the following operations can only be performed by certain roles:
• Configuration
• Edit/Commit
In short:
Enterprise Manager + + + + +
Power User + - + + +
System Administrator + + - +
User + - - +
It is also possible for users to be members of several additional user roles at once, which provides fine-grained control over user access to various areas of
DatAdvantage. The following table lists the possible activities for each of the additional user roles:
User General Capabilities With the Configuration With the Commit/Edit User Comments
User
Alerts View user View and analyze alerts Same Same No Jump To options are
available
User General Capabilities With the Configuration With the Commit/Edit User Comments
User
Classification Analysis for View the classification Same Same Only the Enterprise
Unix Files analysis of all sensitive files Manager can assign this
on a Unix file server from role to users.
the Work Area (in the File
Results Analysis window).
Important: This
role allows the user
to access the files
regardless of the
user's permissions.
User General Capabilities With the Configuration With the Commit/Edit User Comments
User
User General Capabilities With the Configuration With the Commit/Edit User Comments
User
User General Capabilities With the Configuration With the Commit/Edit User Comments
User
User General Capabilities With the Configuration With the Commit/Edit User Comments
User
User General Capabilities With the Configuration With the Commit/Edit User Comments
User
Reports View user • Create reports Same Same No Jump To options are
• Access the quick view available
• Subscribe to reports
• Manage subscriptions
• Set filters on the Filter
Configuration tab
• Set the schedule on the
Scheduler tab
• Configure Active
Directory properties
on the Active Directory
Properties tab
Review Area user • View the Review Area • View the Review Area • View the Review Area • Jump To options
• View permission status • View permission status • View permission status are available only to
options options options screens to which the
• View the Edit pane • View the Edit pane • View the Edit pane user has permission
• View editing history • View editing history • View editing history • Jump to Work Area is
only available if the user
• Manage users and • Manage users and
has the Work Area user
groups groups
role
• Manage directories and • Manage directories and
• Jump to Review Area is
files files
only available if the user
has the Review Area
user role
User General Capabilities With the Configuration With the Commit/Edit User Comments
User
Statistics View user Generate statistics for: Generate statistics for: Generate statistics for: • Jump To options
• Resources • Resources • Resources are available only to
• Directories • Directories • Directories screens to which the
• Users • Users • Users user has permission
• Groups • Groups • Groups • Jump to Work Area is
only available if the user
Manage ownership Manage ownership has the Work Area user
role
• Jump to Statistics is
only available if the user
has the Statistics view-
based user role
Work Area user • View permissions and • Manage users and • Manage users and • Jump To options
recommendations groups groups are available only to
• Manage directories and • Manage directories and screens to which the
files files user has permission
• Jump to Work Area is
only available if the user
has the Work Area view-
based user role
Users with multiple roles are granted the highest permissions possible for that combination of roles. This may result in redundancy. For example, the Enterprise
Manager role includes all the permissions available to all other roles; it would therefore be redundant to assign other roles to a user who is an Enterprise
Manager.
• A user's role is validated each time the user moves to another screen in DatAdvantage, so that only the areas to which that user has permission are displayed.
• The DatAdvantage authorization model limits the data to which a user has access. For example, a user might be limited to specific resources, OUs, directories,
and so forth.
• All roles are controlled by the security options that are set through the Management Console during configuration. These options function as follows:
• Enable global flags and tags in DatAdvantage - Select to determine whether global flags and tags can be used in DatAdvantage.
• Enable assigning global flags to a rule - If the Enable global flags and tags in DatAdvantage is selected, this option becomes available for selection.
Select to enable assigning global flags to a file based on DCF rule criteria. The global flags can be assigned to files only.
• Apply object limitation for users that own both directory objects and file system objects - Select to restrict users from owning both directory objects and file
system objects.
• Enable object limitation for owners and custodians - Select to limit owners and custodians to view only the object hierarchy each one owns.
• Do not provide activity information to group owners or domain custodians - Select this option to prevent group owners and domain custodians from
viewing activity information regarding group members. Regarding reports, this option affects only results displayed in the user interface and data-driven
subscriptions. It does not affect regular subscriptions. These must be deleted manually to prevent owners from viewing them.
• Data-driven subscriptions are not sent to group owners or custodians
• Activity-based reports (report categories 1 and 2) are not available to group owners or custodians
• Group owners who are also data owners have access to all relevant information as usual
• Limit DatAdvantage security configuration to Enterprise Managers only - Select this option to limit DatAdvantage security configuration to Enterprise
Manager and exclude users with the Configuration role.
Abstract Entities
Abstract entities are users and groups whose security identifiers (SIDs) are not related to a
particular domain (similar to Microsoft's well-known SIDs and implicit groups).
IDU Analytics does not take abstract entities into consideration. No recommendations are
generated for their members or permissions.
• Other
• Default
• This Organization Certificate
Except for a user defined as a custodian, any user in the Active Directory from any domain may be
an owner.
The following entities can be managed, regardless of their presentation: (that is, as tree nodes, pie
chart slices, grid rows, and so on):
• Group
• Directory
• Mailbox - On Exchange or Exchange Online Servers, owners can only be assigned at the
mailbox level within the mailbox store. For example, an owner cannot be assigned to a specific
calendar.
When an owner is defined for a file system entity, the entity becomes the base folder. A base
folder cannot have a parent folder or subdirectories that are themselves base or managed folders.
Custodians are mainly responsible for the IT aspects of resource and domain management. They
may not act concurrently as owners over the objects residing in their assigned entities. Therefore,
access to the DatAdvantage UI by custodians and owners may be limited to their managed objects
only, allowing full segregation of data for security purposes.
Groups can be defined as resource custodians to grant all members in the group custodian
privileges on the file server. If a member in the group is a folder owner on the resource, the
member can also be defined as a custodian. In this case, the member is limited to custodian
privileges only on the file server.
It is important to note that a custodian cannot be set on a resource or domain in which he already
owns a folder or group, and vice versa - a custodian cannot become an owner on a folder residing
on one of the resources under his custodianship.
A group - and not just a user - can also have ownership of both domains and file servers.
Assigning ownership to a group reduces the logistics of managing ownership changes.
Defining a group to ownership grants all users directly in the group custodian privileges on the
file server. The users directly in the group can see the file servers/domain in the Work area and
Reports according to resource custodian limitations.
Users that are folder owners to a specific resource can also be members of the custodian group
– they will be treated as resource custodians and not folder owners in regards to ownership
limitations.
• In order to access the UI, a user must be defined in an application role. This implies that
even if this user is defined as an owner or custodian, he will not be able to operate the UI if
he is not defined in an allowed role. However, owners who have no application role are still
synchronized to DataPrivilege and they can receive data-driven reports.
• A user that is not listed as owner or custodian has no visibility limitations in DatAdvantage.
These users see all objects, regardless of their role. For example, an enterprise manager who
is an owner sees less than a simple user who is not an owner.
• However, other non-managed objects may be visible in some situations, in view-only mode.
For example, an owner can see nested groups under one of his managed groups.
• If the owner manages folders, he can see all users and groups related to his folders. If the
owner manages groups, he can see all the folders related to his groups.
Resource custodian • Full visibility of all nested Full visibility of all objects.
folders
Double-click to view
• Full control (editing,
permissions on owned
commit, double-click,
resources.
jump-to) on all nested
folders
Folder owner • Full visibility of all nested Full visibility of all objects.
folders
Double-click to view
• Full control (editing,
permissions on owned
commit, double-click,
folders.
jump-to) on all nested
folders
Domain custodian Full visibility of all objects • Full visibility of all nested
groups and users
• Full control (editing,
commit, double-click,
jump-to) on all nested
objects
Group owner Full visibility of all objects • Full visibility of all nested
groups and users
• Full control (editing,
commit, double-click,
jump-to) only on the
owned group.
• Double-click unowned
users or groups to view
permissions on owned
folders.
• Pickers are not limited by ownership. This means an owner can add members and
permissions to his managed objects from any of the available views.
• Statistics View
• Statistics are not populated automatically for owners and custodians. In the Statistics view,
graphs are only loaded if the user double-clicks one of his owned objects.
• Owners cannot right-click in the statistics graphs. This means owners cannot jump to other
views or manage ownership options from within the displayed graphs, but it does allow drill-
down within the graph itself (for sub-folders, or more granular pie-chart slices).
• Log View
• The log automatically implements the data-driven mechanism, which limits the viewable
objects according to the users' management status.
• The data-driven mechanism limits log output even if the user sets filters that encompass a
larger area than he is allowed to view.
Multiple Owners
Some users are set as owners of more than one type of object. For example:
For these users, ownership limitations are treated as Or conditions. This means that in any of the
cases above, the user has full visibility for all the objects in the system, but he is limited in the
actions permitted to him.
Folder owner and group • Full visibility for all folders • Full visibility for all
owner on all resources objects
• Control (editing, commit, • Control (editing, commit,
double-click, jump-to) double-click, jump-to)
only on owned folder and only on owned group
all nested folders
Resource custodian and • Full visibility for all folders • Full visibility to all objects
group owner on all resources • Control (editing, commit,
• Control (editing, commit, double-click, jump-to)
double-click, jump-to) only on owned group
only on owned resource
and all nested folders
Resource custodian and • Full visibility on all folders • Full visibility on all objects
domain custodian on all resources • Control (editing, commit,
• Control (editing, commit, double-click, jump-to)
double-click, jump-to) only on groups and users
only on owned resource from the owned domain
and all nested folders
Folder owner and domain • Full visibility on all folders • Full visibility to all objects
custodian on all resources • Control (editing, commit,
• Control (editing, commit, double-click, jump-to)
double-click, jump-to) only on groups and users
only on owned folder and from the owned domain
all nested folders
Ownership Inheritance
The following table summarizes inheritance with regard to ownership and custodianship:
Inheritance Description
Inheritance Description
The following major directory service account management functions are available:
• User and account management - This includes the following administrative tasks:
• Creating an entity
• Deleting an entity
• Resetting an entity password
• Unlocking an entity
• Enabling and disabling an entity
• Moving an entity
• Copying an entity
• Editing an entity
• Resetting user passwords
• Unlocking users
• Enabling or disabling users
• User and group filtering - This includes filtering accounts that require attention, such as locked
users, expired passwords, etc.
• Capturing events - Capture user administration events such as locking and unlocking users;
resetting passwords; and enabling or disabling users.
• Viewing and sorting directory service objects and properties - DatAdvantage provides
convenient viewing and sorting of Active Directory properties within user and group panes.
Note: Account management activities are not supported for SharePoint Online, Exchange
Online and OneDrive.
For non-CIFS resources (such as SharePoint, Unix and Exchange), the folder structure is displayed
as usual in the logical view. This means that even if the view state is switched to Logical, the real
folder tree is presented, just as it is in the physical view.
For mixed-mode resources (which include both CIFS and non-CIFS folders), the tree structure
presents all shares as well as the non-CIFS mount points at the first level.
• In the Directories pane, inaccessible objects are indicated by a yellow folder icon and the text
of accessible objects is displayed in bold gray.
• In the Directories pane, accessible objects are indicated by a yellow folder icon inside a green
square.
• In the Users and Groups Pane, the icons of disabled users and computer are lightened to
distinguish them from enabled users and groups.
For instructions on activating this feature, see Setting User Interface Display Options.
This section describes recommended workflows. For complete instructions on carrying out the
activities described in the workflows, see the relevant sections.
By applying the described workflows on a daily basis for 30-45 minutes, you can eliminate risk and
simplify the domain structure, while maintaining user productivity.
Keep in mind that DatAdvantage does not provide recommendations for the Everyone and
Domain Users groups. There are also several groups, such as Domain Admin, whose users
normally do not use all the permissions provided by the group; as a result, recommendations will
be made to remove them from that group.
It is also important to remember that DatAdvantage IDU Analytics recommendations are based
on access. If a directory or file was not accessed at all, the analysis will recommend that all
permissions be removed from it.
Prior to reviewing specific groups, it is highly recommended to review the predefined Windows
Everyone and Domain Users groups. These groups are often granted extensive permissions; since
every domain user belongs to these groups by default, you may find that certain areas of the file
server are accessible to all users, with no controls. If you do find that either of these groups is
granted permissions, you should probably start the change process by modifying the permissions
to a more specific group (except for areas that are meant to be publicly accessible).
1. In the Existing Users pane (hidden by default), double-click the relevant group to view the
current permissions for the group.
2. In the Recommended Users pane, double-click the group to view recommendations for it
on the selected resource. If you are monitoring several resources, repeat the process for the
other resources after you have completed it for the current resource. The explanation next to
the directory or file indicates the type of change - removing the group from the entity's ACL,
removing a user from the group, the group from which the permissions were inherited, and so
on.
3. Sort the group list by status to view specific users with recommendations.
4. Double-click the groups or users to view the recommended changes across the file server.
5. Use the flags to categorize the users and groups into the following: Reviewed, Changed,
Requires Further Review, and Do Not Change.
1. Identify all the directories and files the group members can access in addition to the ones you
previously reviewed.
2. Use these directories and files for further review.
Note: You can also use the IDU Analytics and Editing reports to review recommended
changes.
In addition to the recommended changes, you can provide manual input by editing group
membership and permissions on directories and files.
In order to apply the recommendations and manual edits to the production environment, you must
perform the commit process. Until you do so, the recommendation and manual edits remain in the
virtual environment.
After completing the review, there are several ways to validate the changes you have made in
DatAdvantage before they are applied to your production environment.
Begin by reviewing the errors listed in the Review Area to identify changes that may cause access
denials. This review validates the changes based on past usage patterns. Keep in mind that errors
are calculated in the background in real time, so the administrator can continue working.
Note: It still might take some time to complete the calculations (up to few minutes).
Therefore, the effect of a change may not be evident for several minutes.
For changes that may impact sensitive groups, directories or files, you can delay applying the
changes to the production environment for 1-2 weeks (this is especially true during the first few
months after deployment, when IDU Analytics is still adapting to the users' behavior patterns). This
enables DatAdvantage to collect additional events and make more precise calculations of errors.
Remember - a user may not access a particular directory or file for a long time; the user may be
ill or on vacation, or the data may be needed on only an occasional basis (such as payroll data
or quarterly financial data). This results in a recommendation to remove the user; however, the
recommendation may change when more data is collected.
In rare cases, additional validation can be obtained by discussing the changes with the users
themselves or with the group managers. Explain the changes you are about to make and the
reasoning behind them, and verify that there is no business reason to contradict the behavior
pattern established by DatAdvantage.
Note: When you apply the changes, be sure you are aware of reporting relationships, and
be careful of making changes to group managers and executives. A manager may require
permissions to data he or she does not access on a regular basis (and it was therefore
recommended to deny the manager access to the data), but the manager's reports do access
it regularly.
3. If you identify days that do not fit the pattern, focus on these days. Use the file server's
Directory and User Activity charts to see if a single user is responsible for the activity, and
whether it is focused on a specific area of the file server.
4. Even if no unusual activity is detected in the Activity History chart, review the other charts to
determine whether a user, directory or file is generating a high level of activity.
5. After you have determined the source, use the User and Directory Statistics charts to drill
down and better understand the nature of the abnormal behavior. For example, check the
user's activity to see whether there are usage patterns that may explain the behavior, check
the user's activity relative to other group members, and so on).
6. If necessary, use the logs to drill down further and review the actual events, to determine the
exact nature of the activity. For example, a user creating a large number of files is probably
backing up data to the file server, whereas a user opening a large number of files across
many directories may be gathering information for some reason.
With Varonis DatAdvantage, the organization can easily view share permissions as such and edit
them as NTFS permissions. DatAdvantage has a powerful engine that sandboxes permissions
changes before implementing them to the real environment. This engine can be used for
identifying abnormalities during the transition from share permissions to NTFS permissions.
Reviewing Activities
DatAdvantage makes it easy to discover usage patterns across the enterprise, without resorting
to the cumbersome work of digging through activity logs. Instead, use the DatAdvantage Statistics
view to identify trends in usage and access. If you require more information at that point, the
Statistics view provides simple drill-down access to the precise location you need in the logs.
However, there is no information about what actually happened. There is no way to tell just by
examining the event itself whether permissions were added or removed, or the file was opened, or
something else happened.
DatAdvantage uses the FileWalk job to examine the file system at predefined intervals and identify
events that occurred on it. Each time the FileWalk job runs, it captures the file system's permission
structure and compares the results to the previous capture. The differences between the two
captures are stored as the history of differences and can be viewed in the Logs view.
Problem
The events themselves and the history of differences provide several pieces of the puzzle, but
neither provides the entire picture. How, then, can you understand exactly what happened?
Solution
In either the Log View or the Report View (report 1a), you can view both audit events and the
history of differences. Use the two sets of information together to establish a full understanding of
the event.
Example
In the figure above, notice rows 2 and 3, which are marked in red.
Row 2 describes an event. You can see the change was made at 5:23 by a user named
DPplatinum-admin. However, since the event was pulled from the operating system, it does not
include any sort of description.
On the other hand, row 3 is drawn from the history of differences. Notice the following:
• The Time column indicates the first time the permissions in question have appeared (or the last
time, if the event is the removal of permissions).
• We do not know exactly who made the change - the Operation By column merely says
FileWalk.
• There is a full description of the change - Read permissions have been added to the directory.
The problem would be completely solved if the two sets of information could be correlated.
Unfortunately, it is impossible to do so. While correlation is not difficult for a single change,
consider what might happen if two users made changes to the same folder. It is not possible to
associate one of the changes with one particular user. If there are three or more users making
changes that override other changes, the problem increases substantially. Moreover, if a change
was made and then rolled back between two runs of the FileWalk job, the history of differences
would not recognize a change at all.
Starting DatAdvantage
To start DatAdvantage:
• From the default Windows Start menu, select Programs > Varonis > DatAdvantage;
-OR-
DatAdvantage Views
DatAdvantage includes several views that enable you to examine and modify the information it
collects:
• The Work Area is DatAdvantage's main working environment. It provides full visibility of
Active Directory, the directory structure and permissions in the organization. This view reflects
the organizational changes recommended by DatAdvantage IDU Analytics, and enables
administrators to edit users, groups and permissions through smart, user-friendly editors.
The Work Area is divided into the following panes:
• Directories - Displayed in the center pane. Use the Directories pane to view the rights
to directories and files in either an actual or recommended user or group environment.
There are some differences in the information displayed in this pane for Unix and Windows
installations.
• Recommended Users & Groups - Represented by the pane on the right side of the window.
The Recommended Users & Groups list displays DatAdvantage's recommendations
for group membership and directory or file access rights. There are differences in the
options available in this pane for Unix and Windows installations. For Unix, three different
permissions are presented - those of the owner, those of its group, and those of all the rest.
• Existing Users & Groups - Represented by a pane on the left side of the window (the pane
is hidden by default). This pane reflects the actual entities in the environment. There are
differences in the options available in this pane for Unix and Windows installations.
Together, these panes provide an integrated view of current user and group rights to files and
directories. In addition, they display DatAdvantage suggestions and manual changes made by
the administrator for file rights and group membership.
• The Review Area enables administrators to analyze the virtual environment created by
DatAdvantage IDU Analytics, along with the administrator's changes, prior to committing these
changes to the real environment.
• The Statistics view provides detailed visualizations and activity graphs for user-defined
timeframes, file servers, directories, users and user groups.
• The Logs view enables you to browse and search the event logs from all the monitored
resources for a specific day, down to the level of a single event, to provide full coverage of the
system.
• The Reports view enables you to define reports to be sent periodically by email. You can also
view reports online, and store snapshots of important reports.
• The Alerts view notifies you if a user's behavior is unusual. When DatAdvantage analyzes
usage patterns for the past 30 days, it generates alerts for users whose patterns do not suit the
norm.
• Print - The Print button enables you to print data from the Statistics and Alerts views.
• Print Preview - The Print Preview button enables you to view the Statistics or Alerts page you
are going to print.
Upload Follow Up Enables uploading a CSV file containing all the data required to
Indicators define flags and tags in a bulk operation.
Management Console Enables launching the Management Console directly from the
DatAdvantage UI.
Archive Enables you to archive events and statistics (This option is not
available if DatAnswers is installed without a valid DatAdvantage
license.)
Automation Engine Enables using the Automation Engine utilities, a suite of tools
that provide the means to remediate security issues in the
organization's file system:
• Broken Inheritance Repair Utility
• Global Access Groups Utility
Data Transport Engine Enables you to define rules to transport data securely from one
location to another. (This option is not available if DatAnswers is
installed without a valid DatAdvantage license.)
Options Enables you to define various display options. (This option is not
available if DatAnswers is installed without a valid DatAdvantage
license.)
Reset Stored Credentials Enables you to delete the credentials stored for this session
during commit or DCF analysis. (This option is not available if
DatAnswers is installed without a valid DatAdvantage license.)
When you select a resource, reload a list, or perform any other operation (such as viewing
statistics or logs), the left side of the status bar displays the progress of the operation. When the
operation is complete, the displayed status is Finished.
If software messages (such as warnings or errors) have been generated, the status bar displays
the number of messages that are available for viewing. Click New Msg once to read the messages.
• Status - Lists the icons and decorators that describe the status of entities in the system.
• Accounts - Lists the icons and decorators that describe various types of accounts. This
includes decorators for accounts that were not active in the system at all during the
analysis period.
• Follow Up - Lists the default flags and tags that are configured in the system.
• Directory Services - Lists the icons and decorators that describe directory service objects.
• Exchange - Lists icons used by Microsoft Exchange and Microsoft Exchange Online.
Keyboard Shortcuts
The following sections describe the keyboard shortcuts that are available in the DatAdvantage
user interface.
File Menu
Tabs Menu
Tools Menu
Help Menu
Open and focus on or close the Users and Ctrl+1 (toggles between the Users and
Groups pane Groups pane and the Directories pane)
Open and focus on or close the Ctrl+1 (toggles between the Users and
Directories pane Groups pane and the Directories pane)
Open and focus on or close the Reports Ctrl+1 (toggles between the My
List pane Subscriptions pane and the Reports List
pane)
Closing DatAdvantage
To close DatAdvantage:
1. Save your work.
2. Select File > Exit. DatAdvantage is closed.
Several elements are shared by most of the DatAdvantage views. The following subsections
describe these elements and provide general instructions for their use. For more specific
instructions for using these elements, see the relevant section in this guide.
Switching Views
There are several ways to switch views in DatAdvantage:
• From the Tabs menu, select the required view.
• On the tool bar, click the relevant view selection tab to move to the required view.
• When you are working with an entity whose information appears in more than one view
(such as a user or directory), select the Jump To option from the shortcut menu (accessed by
right-clicking the relevant entity). This method enables you to switch to another view while
maintaining the context of the entity with which you were working.
• In the Statistics view, you can access the same shortcut menu by right-clicking a pie slice or a
bar in the relevant graph. If you jump to the Logs view, the log is automatically loaded with the
relevant filters, so that it reflects the events that comprise the selected graph portion.
Selecting Resources
Selecting the resource (that is, the file server or directory service), is the first step in managing the
user and directory environment in the rest of the Work Area. The Directories pane and permissions
for users and groups are based on the selection of the resource. The default resource is the first
one added to the system during installation of DatAdvantage.
All the network resources monitored by DatAdvantage are displayed in the Resources drop-down
list in the Directories pane. Resources located on all supported platforms can be displayed.
Exchange uses the concept of logical storage, called the storage group. A storage group may
comprise many Exchange Servers within a single domain. In the Directories pane, storage groups
are represented as resources.
Directory services are represented as containers in which domains reside. They are represented
as a flat list, regardless of the trust relationships between them.
In the Work Area and the Statistics view, you may select more than one resource.
• Work Area - Information about all selected resources is displayed in the Directories pane.
• Statistics view - Aggregated statistics are displayed for all selected resources.
To select a resource:
1. From the Resources drop-down list, select the required resource, or select All Resources. If
you selected All, all the resources defined in your environment are listed in the Resources
table.
2. Filter and sort the table as follows to quickly locate the relevant file server:
• In the Look For field, type the first few characters of the file server's name.
• In the results table, set filters in the first row under the table header as required.
• Click the header of any table column to sort the results by that column.
3. After you have located the required file server, select its checkbox.
4. To remove a resource, clear its checkbox.
Use the Current Active Entity list according to the following guidelines:
• Each time you select an entity in one of the main panes (Resources, Directories or Users &
Groups), it is added to the Current Active Entity list.
• You can also select an entity from the list itself to make it the current active entity.
• Click the Move Forward and Move Back buttons to navigate the list as required.
• The list can contain up to 50 entities at a time.
• Entities in the list have the following naming convention:
<Entity icon> <View name>:<Entity name>
• If you select an entity that is located in a different view, the view is switched, and view
preferences (such as timeframe and filters) are refreshed accordingly.
2. From the OUs drop-down list, select the organizational unit in which the required user is
located. The OU's users are displayed.
3. Select the following options as relevant:
• Include computer accounts - Select to include computer accounts in the search results
• History - Select to include
4. Enter the search criteria:
• Search field - Enter the name (or the first few letters) of the entity you want to find.
• In field - From the drop-down list, select an Active Directory property by which to further
filter the search.
• Search field - Type the first few letters of the relevant entity's name.
5. Click Search.
The entities whose properties match the search criteria are displayed in the center pane of
the dialog box.
6. From the center pane, select the relevant entity.
7. Click Add.
The entity is moved to the bottom pane of the dialog box.
8. Repeat to add other users to the group.
9. Click OK.
The dialog box is closed, and the users are added to the group. The users are marked with
green plus signs ( ) and the group is marked with a yellow pencil ( ).
1. Open the dialog box from the relevant view, pane or entity.
2. Use the Resources drop-down list and the Look For field to search for the required directory.
3. Click Search.
The entities whose properties match the search criteria are displayed in the center pane of
the dialog box.
4. From the center pane, select the relevant entity.
5. Click Add.
The entity is moved to the bottom pane of the dialog box.
6. Repeat steps 4 and 5 to select additional entities.
7. Click OK.
Example 1
The following illustrates the allocation of permissions on a given folder:
• Share Permissions
• Everyone - Read
• Engineering - Full Control
• NTFS Permissions
• QA - Modify
• IT - Full Control
Consider the group nesting: Engineering is the parent of QA. The following views are displayed in
the Users & Groups panes:
• Share Permissions
• Everyone - Read
• Engineering - Full Control
• File System Permissions
• QA - Modify
• IT - Full control
• Effective Permissions
• QA - Modify
• IT - Read
Example 2
The following illustrates the allocation of permissions on a given folder:
• Share Permissions
• QA - Read
• Engineering - Full Control
• IT - Read
• NTFS Permissions
• Everyone - Modify
The following views are displayed in the Users & Groups panes:
• Share Permissions
• QA - Read
• IT - Read
• Engineering - Full Control
• File System Permissions
• Everyone - Modify
• Effective Permissions
• QA - Read
• IT - Read
• Engineering - Modify
For non-CIFS resources (such as SharePoint, Unix and Exchange), the folder structure is displayed
as usual in the logical view. This means that even if the view state is switched to Logical, the real
folder tree is presented, just as it is in the physical view.
For mixed-mode resources (which include both CIFS and non-CIFS folders), the tree structure
presents all shares as well as the non-CIFS mount points at the first level.
• Pruned Tree - Presents the search results in a partial tree structure. Leaves that do not
match the search criteria are disabled.
• Arrow Tree - Presents the search results in a full tree structure. Arrows are used to indicate
the relevant results.
1. In the relevant Users and Groups pane, double-click the entity whose permissions you want to
review.
2. In the Directories pane, click the View button.
The View menu is displayed.
3. Select Permissions, and then select the relevant option from the submenu:
• File system permissions - Displays the file system permissions for the permitted folders.
This option is available in both the physical and the logical views.
• Share permissions - Displays the share permissions for the permitted folders. This option is
only available in the logical view.
• Effective permissions - Displays the effective file system permissions for the permitted
folders, as masked by the share permissions. This option is only available in the logical
view.
1. In the relevant Users and Groups list, locate the entity whose mailbox you want to work with.
2. Double-click the entity to display the mailboxes to which it is related in the Directories pane.
3. In the Directories pane, click the View button.
The View menu is displayed.
4. Select Exchange Grouping > Dynamic Grouping. The mailboxes are automatically arranged
in the Directories pane in the following groups:
• Changed - The mailboxes for which the selected entity's permissions have changed
• Not Permitted - The mailboxes the selected entity cannot access
• Permitted - The mailboxes for which the selected entity has access rights
5. If necessary, select Permissions > Exchange Grouping > Alphabetic Grouping to add an
additional layer of alphabetic grouping to the dynamic grouping.
To show or hide icons ( ) indicating folders that are managed in the Metadata Framework:
The selected columns are displayed. The Directories pane provides the following additional
information about directories:
• Physical Size (After Deduplication) - The directory's physical size, in bytes, after
deduplication is enabled on the volume (not relevant for directory service probing)
• Contained Files/Objects - The number of files in the directory or the OU
• Modified - The last date on which the directory was modified, or the last time at which the
OU object was modified
• Accessed - The last time the directory was accessed (not relevant for directory service
probing)
• Server - The server on which the directory or OU resides
• Owner - The person responsible for the directory or OU object
• Flags (All) - Directories that have any sort of flag (global or personal) attached to them
• Flags (Global) - Directories that have global flags attached to them
• Flags (Personal) - Directories that have personal flags attached to them
• Tags - Directories that have tags attached to them
• Notes - Directories that have notes attached to them
Note: Only rules that were run on files on which hits were detected are displayed in
the submenu.
• Flags - From the submenu, select the flag by which to filter directories and files (this option
is only displayed if flags are defined).
• Tags - From the submenu, select the tag by which to filter directories and files (this option
is only displayed if tags are defined).
• Notes - From the submenu, select the note by which to filter directories and files (this
option is only displayed if notes are defined).
• Edited Directories - Select to display only directories and files that have been edited in
DatAdvantage.
• Error Directories - Select to display only directories and files that have errors in
DatAdvantage.
• Attributes - From the submenu, select the permission attribute by which to filter directories
and files. Options are:
• Protected
• Unique
• Inherited
• Ownership - From the submenu, select the management attribute by which to filter
directories and files. Options are:
• Managed
• Unmanaged
• Data Transport Engine - Select to display only the directories used in data transport rules.
Clearing Filters
To clear filters and flags in the Directories pane:
For convenience, procedures that can be carried out on both lists are only explained once.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. In the list (existing or recommended), click the Reload button. The list is reloaded with the
most updated information.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Click the Arrange By button for the list you want to sort (either the actual list of users and
groups, or the recommended list). A drop-down list is displayed.
3. From the drop-down list, select the required sort option:
• Name - Select to arrange the list by the displayed user or group name. This option is
available for both lists.
• Type - Select to arrange the list into users or groups as required. This option is available
for both lists.
• Status - Select to arrange the list according to the status of users and groups; that is, those
that have been added, removed, or undergone other changes. This option is only available
for the recommended list of users and groups.
• Email Address - Select to arrange the list by email address (if Exchange or Exchange
Online is installed).
• Has Errors - Select to arrange the list by entities that have errors. This option is only
available for the recommended list of users and groups.
• User Edited - Select to sort the list according to users and groups that have been manually
edited. This option is only available for the recommended list of users and groups.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Click the Filters button.
3. From the submenu, select the required filter options. You may select as many as necessary;
however, the selection of conflicting filters does not return results.
• Entities - From the submenu, select the type of entity by which to filter the list. Options are:
• Distribution Groups
• Security Groups
• Users
• Computers
• Account Management - From the submenu, select an option to filter the list by
management activity. Options are:
• Enabled users with expired passwords
• Accounts that are enabled but stale
• Locked-out users
• Accounts that are disabled and stale
• Enabled users with password about to expire
• Enabled users with account about to expire
• Users with password that never expires
• Accounts with expiration date
• Stale accounts
• Users with expired passwords
• Flags - From the submenu, select the flag by which to filter users and groups (this option is
only displayed if flags are defined).
• Top-Level Flags Only - Select to filter the list by top-level flags.
• Tags - From the submenu, select the tag by which to filter users and groups (this option is
only displayed if tags are defined).
• Top-Level Tags Only - Select to filter the list by top-level tags.
• Notes - From the submenu, select the note by which to filter users and groups (this option
is only displayed if notes are defined).
• Changed Objects - From the submenu, select the type of change by which to filter the list.
Options are:
• IDU Analysis - Filter by changes recommended by IDU Analytics.
• Edited - Filter by manual changes.
• Disabled - From the submenu, select an option to filter the list by enabled or disabled
objects. Options are:
• Enabled
• Disabled
• Inactive - From the submenu, select an option to filter the list by active or inactive objects.
Options are:
• Active
• Inactive
• Children - From the submenu, select an option to filter the list by objects having children or
not. Options are:
• No children
• Has children
• Ownership - From the submenu, select an ownership option by which to filter the list.
Options are:
• Unmanaged
• Managed
• IDU Analytics Exclusion - From the submenu, select an option to filter the list by objects
that are included or excluded from processing by IDU Analytics. Options are:
• Included
• Excluded
• Only Changed Users and Groups - Select to display only users and groups whose
permissions have been changed.
• Clear Filters
When the list of users and groups is arranged by children, users appear at the main nodes. Each
user's groups are displayed at the sub-nodes.
You can easily switch between parent and child views in both the Existing Users and Groups and
the Recommended Users and Groups lists.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. In the Users and Groups pane, click the View button.
The View menu is displayed.
3. Do one of the following:
• If the entity list is arranged by parents, click the Children button to arrange the list by
children
• If the entity list is arranged by children, click the Parents button to arrange the list by
parents.
1. Set the Directories pane to the relevant view, either Physical or Logical.
2. In the relevant Users and Groups pane, double-click the entity whose permissions you want to
review.
3. In the Users and Groups pane, click the View button.
The View menu is displayed.
4. Select Permissions, and then select the relevant option from the submenu:
• File system permissions - Displays the file system permissions for the permitted folders.
This option is available in both the physical and the logical views.
• Share permissions - Displays the share permissions for the permitted folders. This option is
only available in the logical view.
• Effective permissions - Displays the effective file system permissions for the permitted
folders, as masked by the share permissions. This option is only available in the logical
view.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Click View > Display Name.
4. To set a customized convention, select Custom. The Display Name Configuration dialog box
is displayed.
5. In the Your Format field, type the required naming convention. Be sure to use one of the
following patterns:
• User Name
• Display Name
• Domain
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Click View > Indicators > Managed Groups. The Managed Groups indicators are toggled on
or off, as relevant.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Click View > Indicators > Inactive. The Inactivity indicators are toggled on or off, as relevant.
You can easily show or hide the Excluded from IDU Analytics indicator:
To toggle the Excluded from IDU Analytics indicator:
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Click View > Indicators > Excluded from IDU Analytics. The Excluded from IDU Analytics
indicators are toggled on or off, as relevant.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Click Edit Columns.
The Edit Columns dialog box is displayed.
3. Select the required properties from the Available Columns pane on the left, and click the right
arrow to move them into the Selected Columns list.
4. Use the Up and Down buttons to arrange the order in which the columns are displayed.
5. Click OK.
The selected columns are added to the Users and Groups pane you are working with.
Note: You can set different columns for each of the Users and Groups panes.
6. In the Users and Groups pane, drag the column dividers to the preferred width.
• The columns are saved as you personalized them, including their selection, order and
width.
• The Users and Groups list can be sorted by these columns, through the Arrange by
button.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Click the Org. units field.
3. Select the relevant option to filter the list of organizational units by domain or local host:
• All domains and local hosts - All domains and local hosts are automatically selected.
• Select specific domain or OU - Double-click the relevant domain or OU, or choose it and
click Select.
• Select specific local host - Double-click the relevant local host, or choose it and click
Select.
The list is filtered so that only users and groups defined for the selected organizational unit
are displayed.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Select the required user.
3. Right-click, and from the context menu, select Bring to Top. The user or group is moved to the
top of the list.
Viewing Azure Active Directory Objects in the Users & Groups Pane
You can view Azure Active Directory users and groups in the Existing Users and Groups and
Recommended Users and Groups panes. You can also view Azure Active Directory users and
groups that were synchronized to on-premises Active Directory.
The list of users retrieved from Azure Active Directory are matched with the list of domain forest
users. In terms of permissions visibility, synchronized users are represented as domain users in the
DatAdvantage UI.
Note: If the Azure Active Directory Sync configuration was configured to disable Active
Directory synchronization, the Active Directory and Azure Active Directory objects are
displayed as two separate entities in the DatAdvantage UI.
To view Azure Active Directory objects in the Users & Groups pane:
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Click the Org. units field.
3. To view users and groups defined for all domains and local hosts (including cloud users and
groups from the Azure domain), select All domains and local hosts.
A list of users and groups defined for all domains and local hosts are displayed. Synchronized
objects are represented as domain objects in the Users & Groups pane. Cloud users and
groups that were created in Azure Active Directory are marked with the cloud icon.
Note: When selecting a cloud user or group, its permissions on the online file servers
are displayed. Alternatively, when selecting a synchronized object, its permissions on
both on-premises and online file servers are displayed.
b. Click Select.
Azure Active Directory users and groups are displayed and marked with the cloud icon.
Synchronized objects are marked as Synced.
Note: You cannot view the permissions of synchronized objects if you have selected to
display only users or groups from the Azure domain in the Users & Groups pane. In this
case, to view the object's permissions, you must first locate the domain user or group.
For more information, see Locating Domain Users and Groups.
• Ownership dialog box - To manage all the objects belonging to a particular owner.
• Drag-and-drop - To add a particular owner to an entity, or vice versa. Custodians cannot be
added by drag-and-drop.
Note: If DataPrivilege is installed and synchronized with DatAdvantage, ensure your list
does not place a managed folder above or below an existing managed folder. Line items
contradicting this rule will be ignored.
<OwnerName>|<ResourceName>|<folder/group>|<type>|<ActionType>|
<OriginalOwner>
Where:
The ActionType field is optional. The ActionType field is only required if the Del or Replace
options are selected.
• OriginalOwner is the name of the original owner in the format of Domain\SAM account
name, where Domain is written in FQDN format and SAM account name is the user logon
name (pre-Windows 2000). If the Replace ActionType is selected, the original owner
replaces the current owner. The OriginalOwner field is only required if the Replace
ActionType is selected.
Varonis.com\david|NetApp1|/vol/vol0/Engineering|Dir
Varonis.com\Richarde|Varonis.com||Dom|Add
Varonis.com\janetr|Portal.varonis.com|Portal.varonis.com
\PM|Gr
To replace David (the current owner) with Mary (the new owner) as the owner of
all folders owned by David:
Varonis.com\mary|*|*|Dir|Replace|Varonis\david
To replace David (the current owner) with Mary (the new owner) as the owner of
the Engineering folder:
Varonis.com\mary|NetApp1|/vol/vol0/Engineering|Dir|
Replace|Varonis\david
Varonis.com\david|WinFS1|D:\Share/Engineering|Dir|Del
2. Click Upload.
3. Browse to upload your previously prepared CSV file.
4. Click OK.
In addition, you can assign groups as resource custodians to grant all users in the group custodian
privileges on the file server. You can assign security or distribution groups as custodians. If a user
is a folder owner on the resource, the user can also be defined as a custodian. In this case, the
user is limited to custodian privileges only on the file server.
3. In the Choose Owners area, click Select. The Directory Services Search dialog box is
displayed.
4. Select the users you want to set as owners or domain custodians or groups that you want to
set as custodians or select the groups you want to set as resource custodians.
5. In the Choose Managed Entities area, select the type of entity to which you want to add the
owners from the Entity Type drop-down list.
• To add an owner, select Group or Directory as relevant. Selecting Azure Active Directory
groups is not supported.
• To add a custodian, select Domain or File Server as relevant.
Note: You can add groups to file servers and domains only.
6. Select the actual entity from the drop-down list to the right of the selected entity type.
7. Click Add. Your choices are added to the Selected Managed Entities area.
8. Click OK.
The owners or custodians and their assigned entities are displayed in the Manage Ownership
dialog box.
3. To add entities to the owner, click Add. The Entity Picker dialog box is displayed.
4. From the Entity Type drop-down list, select the type of entity to which you want to add the
owner.
5. Click Select to select groups, directories, File Servers, or domains. The dialog box that is
displayed depends on the entity type you chose.
6. Select the required entities.
7. Click OK.
The owners and their assigned entities are displayed in the Manage Ownership dialog box.
Note: The Add Managed Resources option is not be available when right-clicking
abstract, global or virtual groups.
3. To add resources, click Add. The Pick Entities to Manage dialog box is displayed.
4. From the Entity Type drop-down list, select the type of entity to which you want to add the
owner. Selections are Domain and File Server.
5. Click Add to add the entities.
The entities are added to the Entity Picker dialog box.
6. Click OK.
The entities are displayed in the Manage Ownership dialog box.
3. To add entities to the owner, click Add. The Directory Services Search dialog box is
displayed.
7. Click OK.
The owners and their assigned entities are displayed in the Set Ownership dialog box.
3. Click Add.
The Directory Services Search dialog box is displayed.
4. Select owners for the entity as required.
5. Click OK.
The entity's owners are displayed in the Manage Ownership dialog box.
2. At the top of the Manage Ownership dialog box, select the type of entity by which you want
to filter.
3. If you are filtering by location, select the file server you want to work with from the second
drop-down list.
4. In the text field, enter the string by which you want to filter the list. The Managed Entities list is
filtered.
Notes:
• If the new owner is a group while the original owner does not own a file server or domain, an
error occurs - groups can only be defined as file server or domain custodians.
• If the original owner is a custodian and also a directory/group owner, and the new owner is
a group, the replacement must be applied only on the relevant file servers/domains (without
applying the directory/group ownership).
3. Use the relevant Browse buttons to select both the original and new owners (if you selected
an entity in the Ownership table, the original owner is already populated).
4. Select the required operation. Options are:
• Replace original owner with new owner - Select to replicate all the original owner's
definitions to the new owner, leaving the original owner with no owned entities
• Clone ownership from original owner to new owner - Select to copy all the original owner's
definitions to the new owner, leaving the original owner's definitions intact
5. Click OK.
2. Click Save As and save the file to the required location (this only saves the current search, not
all defined owners). The file takes the following format:
• The pipe sign ( | ) is used as a separator.
• OwnerName is in the format of Domain\SAM account name, where Domain is written in
FQDN format and SAM account name is the user logon name (pre-Windows 2000).
• ResourceName is either the file server name or the domain name, written exactly as they
are configured in DatAdvantage (either FQDN or NetBIOS). Wild cards are supported.
• Folder/group is the physical path of the folder to manage, or the group name in the
format of Domain\SAM account name, where Domain is written in FQDN format and
SAM account name is the user logon name (pre-Windows 2000). For custodianship, this is
left empty. Wild cards are supported.
• Type - One of the following options:
• Dom – Domain
• R - Resource
• Gr – Group
• Dir- Folder
The ActionType field is optional. The ActionType field is only required if the Del or
Replace options are selected.
• OriginalOwner is the name of the original owner in the format of Domain\SAM
account name, where Domain is written in FQDN format and SAM account name is
the user logon name (pre-Windows 2000). If the Replace ActionType is selected, the
original owner replaces the current owner. The OriginalOwner field is only required if
the Replace ActionType is selected.
DatAdvantage enables you to manage changes and commit processes through the Change
Management and Commit window. You may commit changes and follow up on processes that are
committed or scheduled for commit. In addition, the Change Management and Commit window
enables you to perform the following:
• View pending or invalid changes
• Search for specific changes and commit processes
• View the prerequisites of changes prior to committing, scheduling or discarding
• Commit a single change or a bulk of changes
• Discard selected changes
• Run a commit process immediately or at a scheduled time
• View, edit, abort, cancel or roll back required processes
• View the progress and status of commit processes
• Export changes and processes to CSV
• Edit the displayed columns
Before committing changes, it is recommended to review their effects on the virtual environment.
To do so, ensure the system is synchronized (see Synchronizing Recommendations).
An email notification is sent when a commit process successfully completes or changes are rolled
back.
Note:
• You must have the Commit/Edit role to perform operations in the Change Management
and Commit window. Users with the Edit role can only view changes and commit
processes and discard changes.
• Commit processes are executed asynchronously.
• Changes on Exchange Online directories and files cannot be committed.
Users
The following changes to users can be committed:
Permissions
The following changes to permissions can be committed:
Ownership
The following changes to ownership can be committed:
• Change owner
• Change group owner
• Change owner or group owner to one from an affiliated Unix domain
ACLs
The following changes to ACLs can be made:
Group Membership
The following changes to group membership can be committed:
• Create new group
• Delete group
• Add member
• Remove member
Permissions
The following changes to permissions can be committed:
• Add permissions
• Remove permissions
• Change permissions
• Add and remove protection
To perform Add Membership or Remove Membership operations for local SharePoint groups, the
commit user must be a member of the site collection's Administrators group.
For SharePoint Online and OneDrive, you can remove guest link permissions for Anonymous
Logon built-in groups.
• In the Logs view, right-click the relevant entity and select Jump to Change Mgmt. and Commit.
The Processes tab in the Change Management and Commit window is displayed, showing all
scheduled and committed changes on the entity or directory.
Note: This option is only available for history of differences events. In addition, the user
must have Edit/Commit or Edit roles.
• Upon creation or deletion of a group, select the Commit these changes option on the last page
of the wizard. The Change Management and Commit window automatically opens and the
Start Commit Process dialog box is displayed.
The Pending Changes tab enables you to perform the following operations:
• Search for specific pending and invalid changes
• View a change's prerequisites prior to committing, scheduling or discarding
• Commit a single change or a bulk of changes
• Schedule the commit process
• Discard selected changes
Use the Pending Changes tab to view specific pending or invalid changes. You cannot commit
invalid changes. Changes can be invalid either due to inconsistent permissions or because the
object no longer exists (such as a group or directory that has been deleted).
2. In the Search pane of the Pending Changes tab, enter any of the following information:
• From the File server drop-down list, select one of the following options:
• File server - Click the Browse button to locate the the file server to be added.
• Access path - Click the Browse button to locate the full path on which the changes
were made. Select the Include child objects option to include an entity's child objects
(subdirectories).
• From the Domain name/OU drop-down list, select one of the following options:
• Domain name/OU - Browse to locate the OU or relevant domain of the user, group or
trustee.
• User/group - Browse to locate the relevant user, group or trustee.
• Status - From the drop-down list, select one or both of the following options:
• Pending - Select to filter the results according to changes with a pending status.
• Invalid - Select to filter the results according to changes with an invalid status.
• Created by - Browse to locate the user who made the change.
• Create time - Set the date and time at which the change was made. Select the All Dates
option to apply all dates.
3. To use advanced filters, click Advanced Filters and set the filters as required.
4. Click Search.
Changes that meet the specified search criteria are displayed in the grid.
You can view the prerequisites on which a change is dependent prior to committing, scheduling or
discarding the change.
discard a prerequisite on which a change is dependent, the change and all of its dependent
changes are discarded.
The Pending Changes tab displays all pending and invalid changes.
2. In the grid, locate the Pre-requisite Changes column. The Pre-requisites column displays
Commit and Discard links for viewing prerequisites.
3. To view the prerequisite(s) for a change, select the relevant link in the Pre-requisite Changes
column.
The Commit or Discard dialog box is displayed, listing the prerequisite(s) on which the
selected change is dependent.
The Commit dialog box provides a list of all changes that must be committed or scheduled in
order to commit the selected change.
The Discard dialog box provides a list of changes that will be discarded if the selected
change is discarded.
Committing Changes
You can select one or more pending changes to be committed in a commit process. The
changes included in the commit process can be committed immediately or scheduled for commit
at a defined time. Invalid changes, such as changes on entities that have been deleted, are
automatically excluded from the commit process.
If you choose to commit a change that is dependent on a prerequisite, the change and all
its prerequisites must be committed. These prerequisite changes are automatically added
when committing the change. You may choose to clear a selected change to exclude it and its
prerequisites from the commit process.
An email notification is sent when a commit process successfully completes or fails to complete.
Note: Editing in the Work Area is disabled until the selected changes are committed to the
database.
The Pending Changes tab displays all pending and invalid changes.
2. In the Pending Changes tab, select the relevant change(s) in the grid and click Commit.
If you have selected one or more pending changes without prerequisites, the Start Commit
Process dialog box opens, prompting you to enter user credentials.
If you have selected pending changes with prerequisites, the Commit dialog box opens,
displaying the Pending + Pre-requisites tab.
Note: In both cases, if you have selected invalid changes, they are displayed in the
Excluded tab. All invalid changes will be excluded from the commit process.
Note: If you have selected changes without prerequisites, continue with step 4.
a. In the Pending + Pre-requisites tab of the Commit dialog box, clear a selected change to
exclude the change and its prerequisites from this process.
Note: Prerequisites common to one or more changes are displayed under each
change.
Important: The user must have the appropriate credentials required to commit
the changes.
• User name - Type the relevant user name or browse to locate the required user.
• Password - Type the relevant password.
• Remember Password - Select to save the credentials for this commit process. This
option saves the credentials for each commit operator.
• Enter credentials per resource - For each resource, click the Enter credentials link and
enter the relevant user name and password.
b. Comment - Type a free-text comment in the field as necessary.
c. Send process report to - Select to send the process report to a recipient and then type
the recipient's email address in the field. You can enter the email of only one recipient or
distribution list.
5. Click Start.
A confirmation message is displayed, enabling you to switch to the Processes tab to view the
progress.
2. In the Pending Changes tab, select the relevant change(s) in the grid and click Schedule.
If you have selected one or more pending changes without prerequisites, the Start Schedule
Process dialog box opens, prompting you to schedule the commit process and enter user
credentials.
If you have selected pending changes with prerequisites, the Schedule dialog box opens,
displaying the Pending + Pre-requisites tab.
Note: In both cases, if you have selected invalid changes, they are displayed in the
Excluded tab. All invalid changes will be excluded from the commit process.
Note: If you have selected changes without prerequisites, continue with step 4.
a. In the Pending + Pre-requisites tab of the Schedule dialog box, clear a selected change
to exclude the change and its prerequisites from this process.
Note: Prerequisites common to one or more changes are displayed under each
change.
Important: The user must have the appropriate credentials required to commit
the changes.
• User name - Type the relevant user name or browse to locate the required user.
• Password - Type the relevant password.
• Remember Password - Select to save the credentials for this commit process. This
option saves the credentials for each commit operator.
• Enter credentials per resource - For each resource, click the Enter credentials link and
enter the relevant user name and password.
b. Comment - Type a free-text comment in the field as necessary.
c. Send process report to - Select to send the process report to a recipient and then type
the recipient's email address in the field. You can enter the email of only one recipient or
distribution list.
6. Click Start.
A confirmation message is displayed, enabling you to switch to the Processes tab to view the
progress.
Discarding Changes
You can discard pending or invalid changes that are not required.
If you choose to discard a prerequisite on which a change is dependent, the change and all of its
dependent changes are discarded.
The Pending Changes tab displays all pending and invalid changes.
2. In the Pending Changes tab, select the relevant change(s) in the grid and click Discard.
If you have selected one or more pending changes on which no other change is dependent,
the Discard dialog box opens, displaying the changes to be discarded.
If you have selected pending changes on which other changes are dependent, the Discard
dialog box displays the Pending + Pre-requisites tab.
3. To exclude a change and its dependent changes from being discarded, in the Pending + Pre-
requisites tab, clear a selected change. Prerequisites common to one or more changes are
displayed under each change.
Note: If you have selected changes on which no other change is dependent, continue
with step 4.
4. Click Start.
The selected changes are discarded.
Additionally, the Processes tab enables you to perform the following operations:
• Search for specific scheduled or completed processes
• Edit a scheduled process
• Cancel a scheduled process
• Stop the commit process
• Roll back a commit process
You can expand or collapse rows in the grid as necessary. Expanding a row enables you to view
the changes included in the process. Certain changes may not be displayed due to filtering or
ownership limitations.
Use the Processes tab to view processes that are committed or scheduled for commit. Each
commit process is assigned a unique ID, which can be used when searching for a specific process.
4. To use advanced filters, click Advanced Filters and set the filters as required.
5. Click Search.
Processes that meet the specified search criteria are displayed in the grid.
3. In the grid, select one or more pending processes that are scheduled for commit.
Tip: You can apply the Process status filter to view pending processes that are
scheduled for commit.
Important: The user must have the appropriate credentials required to commit
the changes.
• User name - Type the relevant user name or browse to locate the required user.
• Password - Type the relevant password.
• Remember Password - Select to save the credentials for this commit process. This
option saves the credentials for each commit operator.
• Enter credentials per resource - For each resource, click the Enter credentials link and
enter the relevant user name and password.
b. Comment - Type a free-text comment in the field as necessary.
c. Send process report to - Select to send the process report to a recipient and then type
the recipient's email address in the field. You can enter the email of only one recipient or
distribution list.
d. Commit changes on folders with broken inheritance - Select to commit changes on
folders with broken inheritance.
Users without edit/commit permissions, or for users where this option was not configured
(via the Management Console), will not see this screen.
Note:
7. Click Start.
The selected process(es) are rescheduled according to the defined time.
Note: You cannot cancel a process that is currently running, or one that has been terminated
or committed. In order to cancel a running process, you must first terminate it. See Stopping
the Commit Process for instructions.
1. Access the Change Management and Commit window and select the Processes tab.
2. In the grid, select the scheduled process(es) to be cancelled.
Tip: You can apply the Process status filter to view scheduled processes only.
Note: For instructions on cancelling scheduled commit operations that are still pending, see
Cancelling a Scheduled Process.
1. Access the Change Management and Commit window and select the Processes tab.
2. Select the required process and click Terminate.
A confirmation message is displayed.
Note: This option is available only if a mail recipient was not selected during commit.
If a mail recipient was previously selected, the report will automatically be sent to that
recipient.
4. Click OK. A confirmation message is displayed. The process is marked as Aborted in the
Processes tab.
If you have selected to roll back committed changes, a rollback process is initiated for
successfully committed changes and a report is sent to the recipient by email.
Rejecting Changes
You can reject or roll back changes that have already been committed. The rollback process can
only be performed for terminated or completed processes that have not yet been rolled back. For
a list of DatAdvantage operations that can be rolled back, see Supported Rollback Operations.
Important: The rollback reverses changes and may not restore permissions to their original
state.
To reject changes:
1. Access the Change Management and Commit window and select the Processes tab.
2. Select the required process and click Rollback.
The Rollback dialog box is displayed.
Note: If a mail recipient was already selected during commit, this field is populated
with the recipient's email address.
4. Click Start.
A confirmation message displays the rollback process ID.
5. Click OK.
The selected change(s) are rejected and a report is sent to the recipient by email.
Note:
• The rollback process can only be performed for terminated or completed commit
processes that have not yet been rolled back.
• The rollback reverses changes and may not restore permissions to their original state.
Note: This action exports all changes and processes that were filtered for display (and not
the items that were selected in the grid).
1. Open the Change Management and Commit window and select the relevant tab.
1. Open the Change Management and Commit window and select the relevant tab.
3. Select the required columns from the Available Columns pane on the left, and click the right
arrow to move them into the Selected Columns list.
Note: For a complete list of columns that can be included in the Pending Changes and
Processes tabs, see Change Management and Commit Columns.
4. Use the Up and Down buttons to arrange the order in which the columns are displayed.
5. To restore the default set of columns, click Reset.
6. Click OK.
The selected columns are added to the grid.
You can customize which columns are included in the Pending Changes and Processes tabs (for
more information, see Editing the Displayed Columns).
You can also change the order in which the columns are displayed, sort columns, and group
columns as required. For more information, see Working with Lists and Tables.
The following table describes all columns that can be included in the Pending Changes tab:
Created By The display and domain name of the user who made the
change, or IDU Analytics.
Created By (SAM Account The domain and SAM account name of the user who
Name) made the change, or IDU Analytics.
Create Time The date and time at which the change was made. The
time format is displayed in accordance with the IDU
Server's local settings.
File Server The name of the file server on which the change was
made.
Last Process ID The unique identifier of the last process which included
the change. This is relevant only for invalid changes or
changes that could not be committed.
Member/Trustee (SAM The domain and SAM account name (in the format
Account Name) Domain\SAM Account Name) of the member or trustee
(for membership or permission changes).
Object The name of the object on which the change was made.
The type of object displayed in this column can be one
of the following:
• File
• Folder
• Group (in the format Display Name (Domain))
• User (in the format Display Name (Domain))
• Computer (in the format Display Name (Domain))
The following table describes all columns that can be included in the Processes tab:
Committed By (SAM The name of the user (in the format Domain\SAM
Account Name) Account Name) who performed the commit operation.
Commit Time The date and time at which the commit action was
executed by the user. The time format is displayed in
accordance with the IDU Server's local settings.
Complete Time The date and time at which the commit process was
completed (i.e., all changes included in the process
were committed by the system). The time format is
displayed in accordance with the IDU Server's local
settings.
Original Process ID The unique identifier of the original process which was
rolled back or is in the process of being rolled back.
This ID is displayed only if a commit process was rolled
back.
Run Start Time The date and time at which the commit process was
executed by the system (i.e., the time at which the first
change in the process was committed). The time format
is displayed in accordance with the IDU Server's local
settings.
Schedule Time The date and time at which the commit process was
scheduled. The time format is displayed in accordance
with the IDU Server's local settings.
When events are archived, they are placed into a ZIP file and moved to a directory whose name
includes the name of the file server. For example, a file server named netapp4 would archive to a
directory named Archive_netapp4 under the Varonis directory, whose location is defined during
installation. These directories can be included in a normal backup schedule.
2. From the Archive type drop-down list, select one of the following options:
• Events
• Statistics
• Commit
3. From the File server drop-down list, select the file server containing the events or statistics to
be archived.
6. To change the operation for a particular event from Archive to Cancel Archive, click the
button for the event in the Operation column.
7. Click OK.
1. Locate the tables to be archived by entering the relevant search criteria. For instructions on
setting search criteria, see Selecting Events, Statistics and Committed Processes.
2. Click Search.
3. Click the action button in the Archive column to set their status to Pending archive.
4. Click Run Now.
The CIFS events, statistics or commit processes for that day are archived, and the table's
status becomes Archived.
1. Locate the tables to be restored by entering the relevant search criteria. For instructions on
setting search criteria, see Selecting Events, Statistics and Committed Processes.
2. Click Search.
3. Click the Restore/Delete action button in the Archive column.
4. From the popup menu, select Restore to set the tables' status to Pending restore.
5. Click Run Now.
The data is restored, and the table's status becomes Active.
For example, if User A is suspected of having deleted a file three years ago, it is possible to
restore back to the database (SQL Server) only those events created by User A, (excluding all the
events for all users for the past three years). The search period will be limited to seven years.
The data that already exists in the original archive file will remain intact.
3. Do as follows:
a. File Servers - Select one or more file servers.
b. Specific Entities - Select all users or restrict the scope to a single user. If you select the
single user option, select that user from the Directory Services Search dialog box (you
can select up to 50 users).
c. Dates - Select the date range of the archives to be restored (the default is a month earlier
than 180 days ago).
Note: The date picker is not limited to only seven years back. If there are events
archived for a period longer than seven years, those will also be restored unless the
customer has SQL storage limitations.
d. Archive Type - Select the relevant archive type (events or statistics) to restore. Note that
all types are selected by default.
e. Reset button ( )- Sets the filters to the following state:
• File Server – Clears the servers that were selected.
• Entities – Selects all users.
• Dates - The last month relative to the current date.
• Archive Type - Selects all checkboxes (all types).
4. Click Search.
The search results are displayed at the bottom in the results grid.
5. Each row in the table displays all data for the date range for the server/specific user per
archive type. Refer to the following:
• User Name - The user's name; this column is changed dynamically based on the selected
search filter.
• If all users and folders were selected – All users is displayed.
• If specific users were selected– the domain/user name is displayed.
• File Server – The file server's name as it is displayed in DatAdvantage.
• File Server Type – The file server's type as it is displayed in DatAdvantage.
• Archive Status – The table's status; this column can have Archived, Pending Restore or
Mixed statuses. The Mixed status is displayed if some of the days are in Archived status
and some with Pending Restore status.
• Archive Type - Displays events and/or statistics.
• Archive Period - The date range of the archive. The first and last dates that data exists for
this server or specific user will define the displayed range.
• Status Details – Displays details of the various archive statuses.
6. Select the files to restore and click the Restore Now button above the table. The files are
restored.
7. Schedule for Restore - The files are restored on the next run of the weekly table maintenance
job.
Note: The data will not be deleted from the original archive file. It will be re-archived
after the extraction of the selected data.
1. Locate the tables to be deleted by entering the relevant search criteria. For instructions on
setting search criteria, see Selecting Events, Statistics and Committed Processes.
2. Click Search.
3. Click the Restore/Delete action button in the Archive column.
4. From the popup menu, select Delete to set the tables' status to Pending delete.
5. Click Run Now.
The data is deleted.
2. Click Servers.
The IDU Server Editor dialog box is displayed.
2. Click Servers.
The IDU Server Editor dialog box is displayed.
3. From the list, select the IDU to be removed. You cannot remove the currently active IDU.
4. Click Remove.
Configuring Dictionaries
One way to create and update a rule efficiently is to define a dictionary of the terms you want your
rule to search. You can define as many dictionaries as you want.
Note: These numbers are recommendations. You can define dictionaries with more
records (up to 60,000), or with shorter records, but they may classify your data less
effectively.
• You can schedule a job that automatically uploads and updates dictionaries.
• Dictionaries may be selected as conditions within rules, which means they may be used as
part of a complex boolean expression (different dictionaries combined with strings and regular
expressions.)
Dictionaries are encrypted in the database using a Triple DES-based symmetric encryption system.
To configure a dictionary:
Adding Dictionaries
To add a new dictionary:
b. Type the term you want to add to the dictionary. For example, type ini if you want to
define a rule to be run on all files of the INI type.
c. Click OK.
The term is added to the dictionary list, along with the following additional information:
• Entry - The term itself.
• Enabled - Indicates whether the term is enabled in the dictionary. Terms that are
disabled are not included in the classification process.
• Modified Date - The date on which the term was last modified.
• Source - Indicates whether the term comes from a predefined dictionary or is user-
defined.
5. To edit a term:
a. In the Edit Dictionary dialog box, select the term to be removed from the dictionary list.
b. Click the red , or right-click and select Delete Entry from the context menu.
Editing Dictionaries
To edit an existing dictionary:
Cloning Dictionaries
To clone an existing dictionary and all its entries:
Removing Dictionaries
When you remove a dictionary, all the rules that include this dictionary in their conditions are
erased along with all matching file results. However, the data that is erased is maintained in history
(the amount of time history is maintained depends on the organization's retention policy).
To remove a dictionary:
Note: If your selection includes at least one predefined dictionary (indicated by a lock
icon), the Remove button is disabled.
3.
Click the red , or right-click and select Delete Dictionary.
However, collection of data for so many users across an entire file system can result in a
good deal of needless overhead in terms of storage space and licensing costs. Therefore,
DatAdvantage enables you to select users and folders you do not want to monitor and remove
them from DatAdvantage storage, either temporarily or permanently.
The lists of unmonitored users and folders are easily configurable and can be changed on the fly,
both through the Configuration window and during daily work in DatAdvantage (see Configuring
Unmonitored Folders and Configuring Unmonitored Users).
Note: If you make a change to resume monitoring an unmonitored entity, the change
takes effect either after the nightly run of ADWalk and PullWalk, or after these jobs are run
manually.
For directory service objects, the icon does not change when an object's monitoring status is
changed.
Note: The available options depend on the current state of the entity. If an entity is
currently monitored, the only available option is Stop Monitoring. If the entity is not
currently being monitored, the only available option is Monitor. However, both the
Monitor and the Stop Monitoring options may be available for a group if the group
contains both monitored and unmonitored users.
Attention: Setting an object as unmonitored filters out all the object's events, and future
events are not collected, This means the recommendations that IDU Analytics makes for
this object may be inaccurate.
Note: This is only possible if the administrator has enabled global flags through the
Management Console.
c. To change a flag's color, click the Browse button to open the color palette and select the
required color.
d. To remove a flag, select its checkbox and click Remove.
Note: This action removes the selected flags from all the entities to which they are
assigned.
In addition to adding new tags and global flags, you can use this procedure to convert existing
personal flags to global flags, detach flags and tags from objects, and change the color of a flag or
tag.
The CSV file for uploading follow-up indicators can contain two types of rows:
• Definition of flags and tags - Use to identify the flag/tag, as well as the action to be performed
• Definition of assigned objects - Use to identify the objects to which flags and tags are attached
Fields that are not required for a particular action can be empty.
Options are:
• GLOBAL
• PERSONAL
Flag Created • Domain users and groups: Domain Name/SAM Account Name • CHANGE_COLOR - If more than one flag
By • Local SharePoint users and groups: Domain\user exists, an error occurs.
• MAKE_GLOBAL - All flags with the flag
Note: This does not have to be the user uploading the file. name and type are converted into a
single global flag.
Only for personal flags. • Existing personal flags are deleted.
Specify the user that created the flag for ATTACH, DETACH, CHANGE_COLOR and • ATTACH - If more than one flag exists, an
MAKE_GLOBAL operations. error occurs.
• DETACH - If more than one flag exists, an
error occurs.
Old Flag Only for flags. Specify the previous flag color to identify the flag for ATTACH, DETACH, • CHANGE_COLOR - If more than one flag
Color CHANGE_COLOR and MAKE_GLOBAL operations. exists, an error occurs.
• MAKE_GLOBAL - All flags with the flag
name and type are converted into a
single global flag.
• Existing personal flags are deleted.
New Flag Mandatory in the NEW and CHANGE_COLOR operations. When a new flag is created and no color is
Color assigned, an error occurs.
Fields that are not required for a particular action can be empty.
Object Type • DIR - File or folder from the directory tree This field cannot be empty
• DIR_LOGICAL - Logical path to file or folder from the directory tree
• DIR_DFS - DFS path to File or folder from the directory tree
• USER - User
• GROUP-group
File Server For directories and files, the name of the file server on which the object resides. None
Name
Access Path/ Object to assign the flag/tag to, or logical path/DFS path/physical path/user/group This field cannot be empty
User/Group name according to the File Server Name parameter.
Change color FLAG,CHANGE_COLOR,MyFlag,,,#005500,#FF0000 • Use the color to identify the flag if there
global flag 1 are two global flags with the same name.
with old color • The color is in hexadecimal format.
to identify the
flag
Make global FLAG,MAKE_GLOBAL, MyFlag ,PERSONAL,,#005500 Merges personal flags with the same name
action and color into a single global flag.
Attach tag to • TAG,ATTACH,MyTag The tag is added to the group and the two
objects (Tag/ • USER,, PM-LAB.COM\MyUser paths.
Flag row) • GROUP,, PM-LAB.COM\MyGroup
• DIR,PM-LAB-DV1,C:/Lila,Y
Attach flag to • FLAG,ATTACH, MyPersonalFlag, PERSONAL,Varonis\lherman Attaches a personal flag to the specified
objects (Tag/ • USER,, PM-LAB.COM\MyUser objects. If there is more than one personal
Flag row) • DIR,PM-LAB-DV1,C:/Lila,Y flag with this name and created by this user,
an error is returned.
Detach flags • FLAG, DETACH, MyPersonalFlag, PERSONAL,Varonis\lherman ,#005500 Detaches a personal flag from the specified
from objects • DIR,PM-LAB-DV1,C:/Lila,Y objects. Specify the flag's color to identify it.
(Tag/Flag
row)
Example
TAG,NEW,My Tag
TAG,ATTACH,My Tag
DIR,PM-LAB-DV1,C:/Lila,Y
FLAG,NEW,My Flag1,,,,#FF0000
FLAG,ATTACH,MY Flag1
DIR,PM-LAB-DV1,C:/Lila,Y
USER,,PM-LAB.COM/MyUser
FLAG,My Flag1,PERSONAL,Varonis/Lila
DIR,,PM-LAB-DV1,C:/Lila,Y
FLAG,ATTACH,My Flag,PERSONAL
DIR,PM-LAB-DV1,C:/Lila,Y
FLAG,MAKE_GLOBAL,MyFlag,PERSONAL,Varonis/Lila
FLAG,MAKE_GLOBAL,MyFlag,PERSONAL
FLAG,MAKE_GLOBAL,MyFlag,PERSONAL,,#FF0000
FLAG,CHANGE_COLOR,MyFlag,PERSONAL,,#FF0000,#005500
FLAG,CHANGE_COLOR,MyFlag,PERSONAL,,,#005500
All other users' follow-up indicators (tags, global flags, and notes) that were set on that entity
are cleared.
Note: This option is displayed only if the user is defined as an Enterprise Manager.
4. To clear all your own follow-up indicators on a specific entity, right-click the entity, and from
the context menu, and select Follow Up > Clear All My Follow-Up Indicators.
All your follow-up indicators that were set on that entity are cleared.
Managing Flags
Flags can be defined as personal, for only the specific user who implements them, or as global, for
all users. Flags can be used in searches and filters, but only global flags may be used in report and
log filters.
Only users specified by the administrator can create new global flags. Other users are free to
attach global flags to the entities they are interested in.
If a global flag is changed to personal or deleted, it becomes a personal flag for all other users that
have implemented it.
If a personal flag is changed to global, all users will see all instances of it.
Multiple flags of each type (global and personal) can be set on a single entity.
Note: If a flag is set to only the current object and you want to apply it to the child
objects, you must first clear the flag from the current object and then reapply it to all
child objects.
6. To set a defined flag that does not appear in the list, select More from the submenu.
The Manage Flags dialog box is displayed.
Inheriting Flags
If a flag is set to only the current object and you want to apply it to the child objects, you must first
clear the flag from the current object and then reapply it to all child objects.
This option is not relevant for virtual groups. Since users cannot be added to virtual groups,
such groups cannot have child objects; therefore, such inheritance is not relevant. Virtual groups
include: Everyone, ANONYMOUS, LOGON, Authenticated Users, Terminal Server Users, Other,
Default.
6. On the Manage Flags dialog box, select the Inherited checkbox for that flag.
7. Click OK. The flag is now inherited by the current object's child objects.
Flags that are inherited from parent objects to which the flags are still attached cannot be cleared.
This procedure describes how users can clear their global and personal flags. Additionally, users
assigned to the Enterprise Manager role can clear global flags to entities attached by other
DatAdvantage users.
Note:
• Users assigned to the Enterprise Manager role will see their flags (personal and
global) and other users' global flags.
• Users not assigned to the Enterprise Manager role will see their flags (personal and
global) and other users' global flags.
a. To select specific flags, select the checkbox to the left of the flag.
b. To select all flags, click the Select All button.
c. To uncheck all flags, click the Clear All button.
7. Click OK.
Managing Tags
Tags are keywords or terms that help describe the selected entity. Tags are always global, and
can be used in searches and filters. They cannot be deleted.
Note: If a tag is set to only the current object and you want to apply it to the child
objects, you must first clear the tag from the current object and then reapply it to all
child objects.
6. To set a defined tag that does not appear in the list, select More from the submenu.
The Manage Tags dialog box is displayed.
9. To set a tag to be inherited by the entity's child objects, select the Inherited checkbox for that
tag.
10. Click OK.
The tag's icon is displayed to the left of the entity.
This procedure describes how users can clear a tag from an entity. Additionally, users assigned
to the Enterprise Manager role can clear tags to entities attached by other DatAdvantage users,
including entities attached by other users also assigned to the Enterprise Manager role.
Inheriting Tags
If a tag is set to only the current object and you want to apply it to the child objects, you must first
clear the tag from the current object and then reapply it to all child objects.
Tags that are inherited from parent objects to which the tags are still attached cannot be cleared.
3. Right-click the selected entity, and from the context menu, select Follow Up.
4. Select Clear All Follow-Up Icons. All the flags that were set on that entity and inherited by its
child entities are cleared.
Managing Notes
Notes are free-text comments that are defined by individual users on specific entities. However,
while they are defined by users (as opposed to administrators), they are global and can be viewed
and edited by all users. Because notes can be edited by anyone, each note includes the time at
which it was last edited and the name of the user who made the change.
5. Type the text of the note in the text box. The text is limited to 500 characters.
6. Click OK.
The note is added to the entity.
To remove a note:
3. Right-click the selected entity, and from the context menu, select Follow Up.
4. From the submenu, select Notes.
The Add/Edit Note dialog box is displayed.
5. Click Remove.
The note is removed from the entity and the dialog box is closed.
6. Alternatively, you can perform a general removal process which removes all notes together
with all follow-up indicators (flags and tags) on the selected entity. Do as follows:
• To remove all global follow-up indicators for all users (including yours), select Follow Up >
Clear All Users' Follow-Up Indicators.
• To remove all your follow-up indicators only, select Follow Up > Clear All My Follow-Up
Indicators.
The list of excluded users is easily configurable and can be changed on the fly, both through the
Management Console and during daily work in DatAdvantage (see the Management Console User
Guide.
Note: If you set an entity to included or excluded, the change takes effect either after the
nightly run of ADWalk and PullWalk, or after these jobs are run manually.
2. Drag the column headings to the area above the list or table marked Drag a column header
here to group by that column. The list or table is grouped.
1. Above the list or table, click the name of the column by which the data has been grouped.
2. Drag it away from that area. When you release the mouse button, the list or table is
ungrouped.
Note: When searching for the name of a deleted entity in the Statistics view, the percent
sign (%) can be used as a wildcard; for example, %leg%; %leg; leg%. The percent sign
may not be used between letters.
Important: Changes you make through these dialog boxes are implemented immediately in
the real environment.
Advanced Searching
Advanced search capabilities are available in several views and products throughout the Metadata
Framework.
2. In the To field:
a. Click the arrow, and select the ending date of the time frame from the calendar.
b. Click the hour and minutes in the To field to set them as necessary.
The time frame for the activity is set.
There are two ways to add groups: through the toolbar, or through the context menu.
Filters can only be nested within groups; they cannot be nested within other filters.
Adding Filters
In Filter mode, you may add as many filters as you want.
• In the Reports view, the filters are equivalent to the headings of the report columns (with the
exception of the User Access Log report, which is, in effect, a log).
• In the Logs view, the filters are specially-defined categories.
To add filters:
Changing Operators
To change the operator in a statement:
• Right-click the operator for the relevant filter, and select the required operator from the context
menu.
Note: For reports, other filter options may be displayed depending on the Active
Directory properties that are defined in the system.
1. Right-click the parent filter and select New Filter. The Group Name filter is added.
2. Right-click the Group Name filter and select Include/Exclude Groups. The Group Name filter is
changed to Include/Exclude Groups, and an Include filter is nested within it.
By default, the cap mechanism is disabled, and should be configured only with assistance from
Varonis Support.
Underlying Technology
Based on the SQL Server Resource Governor, the mechanism enables database administrators to
manage SQL Server workload and critical system resource consumption.
When the cap mechanism is configured, one or both of the following keyvalues is set to a value
greater than 0:
• MaxAllowedCost - Set to configure the cap mechanism for logs and reports
• MaxAllowedCostDCF - Set to configure the cap mechanism for the DCF
The values represent the top time or size threshold permitted for generating the report or log, or
executing the DCF rule on which it is set. Once the values are set, they apply to all queries run in
the system.
Once it is configured, users may enable or disable the cap mechanism as needed by clicking
the Cap button in the Advanced Search pane or the DCF Rule dialog box. (This button is only
displayed when the relevant keyvalue is set to be greater than 0.)
1. On the Advanced Search toolbar, click Save/Load > Save As or Import/Export Filter > Export
to File, as relevant.
2. Save the search according to standard Windows procedures.
1. On the Advanced Search toolbar, click Save/Load > Load or Import/Export File > Import from
File as relevant.
2. Locate the required search according to standard Windows procedures and click Open. The
search is loaded.
The DatAdvantage Work Area provides greater visibility to data and the effective rights users have
to that data on the network. This area also displays a virtual view of user and group rights, based
on recommendations made by IDU Analytics or changes made manually by the administrator. The
representation of data in this area allows for direct comparison between the permissions currently
associated with users and groups, and DatAdvantage recommendations made after analyzing and
classifying actual data usage in the environment. Administrators can see the recommendations for
removing or adding access rights to directories and files, and editing user and group relationships
before committing the changes in the Active Directory environment.
Viewing Permissions
While the procedure for viewing permissions is the same throughout the Work Area, the actual
display of permissions depends on the type of entity you have selected (that is, the current active
entity).
To view the permissions a user or group actually has for a specific directory:
• Full Access
• Send As
• Send On Behalf
Standard Exchange sharing permission
levels:
• None
• Owner
• Publishing Editor
• Editor
• Publishing Author
• Author
• Nonediting Author
• Reviewer
• Contributor
• None
If you are working with a directory or directory service object, you may find that the
permissions are displayed in parentheses. This indicates Deny permissions.
For POSIX ACLs, lowercase letters indicate that the permission has been granted, but is
masked; in effect, this means the permission does not exist.
Note:
It is recommended that, in the ordinary course of work, you check the permissions
of the protected and unique directories (those whose folder icon is decorated with a
person). In general, all other directories (that is, those that are not unique) inherit their
permissions from the unique parent, and are therefore color-coded the same way the
parent directories are.
However, on NTFS, permissions can be set for only a specific directory, or to a specified
set of sub-directories. This means there may be unique directories whose color-coding
is different than the directories from which they inherited, since they have different
permissions.
However, the Permission Sources window displays highly detailed permission data. Specifically,
it lists all the groups from which a permission mask is inherited, along with the root folder of the
inheritance.
Note: For deleted users, the user name is displayed in the Permission Sources window.
• NTFS-based platforms:
• Detailed inheritance
• SharePoint/SharePoint Online/OneDrive:
• The site in which the current and recommended permission levels are defined
• The site collection administrators group permission and root folder
• Unix:
• Permission type
• Root user permission
• Exchange/Exchange Online:
• Permission type
• The mailbox folder from which mailbox permissions are inherited
• Directory service objects:
• Detailed inheritance of permission roles
Important: If a particular role has one ACE in one row and other ACEs in other rows
(due to different flags or inheritance sources), full details are displayed in the header.
This display is only available for roles that are Read/Write for property sets. It is not
available for generic roles.
• Time of Permission Change - The date and time of when the DA user/system editing
action occurred (based on IDU server time).
• Change By - The name of the user who created the editing command.
• Current Permissions via Source - The current permission the entity has on the folder in
the Admin Set but only through this source.
• Current Flags via Source - The current permission flags the entity has on the folder in the
Admin Set but only through this source.
• Recommended Permissions via Source - The recommended permission the user has on
the folder in the Existing Set but only through this source based on the displayed editing
command.
• Recommended Flags via Source - The recommended permission the user has on the
folder in the Existing Set but only through this source.
• Change Description - A description of the permission change.
Viewing Recommendations
While the procedure for viewing recommendations is the same throughout the Work Area, the
actual display of recommendations depends on the type of entity you have selected (that is, the
current active entity).
To view the recommendations that have been made for a user, group, directory or file:
Managing Permissions
4. In either the Directories pane or the Recommended Users and Groups list, locate the entity
whose permissions you want to edit.
5. Right-click the entity, and from the context menu, select Edit Permissions. The Properties
dialog box is displayed.
Important: This is not Microsoft's standard Permissions dialog box. Changes made here
do not affect the real environment until they are actually committed.
6. In the Group or User Names area, select the group or user whose permissions you want to
edit.
7. In the Permissions For area, select the permissions to be added to the entity, and clear the
permissions to be removed from the entity.
• The changes you make are marked in green and red, to indicate added and removed
permissions respectively.
• Each change you make automatically results in changes to other permissions in the
virtual sandbox. For example, if a user had full control permissions on file, and you
choose to deny the user write permissions, the Full Control, Modify and Write options are
automatically cleared in the Allow column.
Note: If you add permissions to a directory or file whose permission type is Inherited, the
permission type becomes Unique.
8. To define special permissions and advanced settings, click Advanced. The Advanced
Security Properties dialog box is displayed.
a. To add a permission entry to the entity, click Add and define the permissions as relevant.
b. To edit an existing permission entry:
1. Click Edit. The Permission Entry For dialog box is displayed.
2. From the Apply to drop-down list, select the objects to which the permissions will be
applied.
3. To apply these permissions to objects or containers within the current container,
select the relevant checkbox at the bottom of the dialog box.
8. Click OK.
Adding Permission Levels to On-Premises SharePoint and SharePoint Online Directories and
Files
This operation adds a permission level to a site.
• The scope of the permission level includes the site and all its descendants (except for sites with
protected permission levels and their descendants).
• Once the permission level is added, it can be assigned to users on items in the scope.
• Permission levels can only be added to sites with protected permission levels.
• Two permission levels cannot have the same name.
• You can restore a permission level that was previously deleted. This undoes the Remove
Permission Level command.
• Names are not case-sensitive.
Adding Permissions
This operation adds permissions to a user or group for an entity.
• It creates Limited Access assignments for the user in all parent-protected items up to the first
protected site (if they do not already exist).
• You cannot assign the Limited Access permission level directly.
• You cannot assign permission levels to the Site Collection Administrators group.
• You can assign anonymous permission levels only to sites and lists (not to children of lists).
• For sites and document libraries you can only add the View (Anonymous) permission level.
• DatAdvantage only supports lists of the Document Library type.
• For the Anonymous user, Limited Access ACEs are not created.
• You cannot assign a deleted permission level.
• You can restore deleted permissions or an entire user. This cancels the Remove Assignment
command and restores the deleted ACEs.
Removing Permissions
This operation removes permissions from a user on an item.
• There are two modes for this operation:
• Remove a single regular permission - Simple mode, in which only the permission is
removed.
• Remove all a user's permissions - Complex mode.
• This operation removes all the permissions for this user in child items down to protected
sites.
• Removing the last permission level on an item from a user also removes the entire user.
• This does not apply to the Anonymous user.
• Removing a permission that was added but not committed removes the permission and cancels
the Add Permission command.
• You can remove the anonymous permissions from sites and lists.
• You cannot remove the Full Control permission level from the Site Collection Administrators
group.
The operation marks the item as protected and copies all the assignment from the protected
parent.
Caution: This operation might cause data corruption on SharePoint versions earlier than
service pack 2.
Caution: This operation might cause data corruption on SharePoint versions earlier than
service pack 2.
To edit permissions:
5. In the Group or User Names area, select the group or user whose permissions you want to
edit. (To add a user or group, click Add and browse to the required entity.)
6. In the Permission Levels area, set the entity's permissions as follows:
a. To add a permission level, click Add. The Select Permission Levels dialog box is
displayed.
b. Select the required permission level and click OK. The permission level is added to the
entity.
c. To remove a permission level from the entity, select it and click Remove. The permission
level is removed from the entity.
7. Click OK.
Note: If you add permissions to a directory or file whose permission type is Inherited, the
permission type becomes Unique.
• Contribute
• Can be customized and deleted
• Has a special permission level type in SharePoint
• Is automatically given to a site when protecting its permission levels, even when choosing to
not copy the permission levels from the parent
• Design
• Can be customized and deleted
• Has a special permission level type in SharePoint
• Is automatically given to a site when protecting its permission levels, even when choosing to
not copy the permission levels from the parent
Anonymous permission levels appear in DatAdvantage for all SharePoint objects (except for Web
sites) as follows:
Anonymous permission levels appear in DatAdvantage for SharePoint Web sites as follows:
• Lists and libraries (Anonymous)
• Entire Web site (Anonymous)
• Sites can only be assigned with the View (Anonymous) permission level.
• Document libraries can only be assigned with the View (Anonymous) permission level.
• Sub-items of lists cannot be assigned with anonymous permission levels.
• Protected items of lists are never accessible to anonymous.
For SharePoint sites that are monitored by DatAdvantage, you can customize the permissions
available in these permission levels (except for the Limited Access and Full Control permission
levels), or you can create new permission levels that contain specific permissions.
Permission levels are inherited from the parent site. This means that to edit a site's permission
levels, you must either edit the parent site, or break the inheritance.
b. In the bottom pane, select the permissions to be added to the permission level. You
may select permissions from any of the following categories (see the descriptions in the
dialog box for more information):
• List permissions
• Site permissions
• Personal permissions
c. Click OK.
The permissions are changed and marked as follows:
• Additional permissions are marked in green
• Removed permissions are marked in red
Each change you make automatically results in changes to other permissions. For
example, if you remove the View Pages permission, the Use Self-Service permission
is automatically removed.
7. To remove permissions from a permission level:
a. In the top list, select the relevant permission.
b. Click Remove.
After a change is made, the name of the changed permission level and an asterisk (*) are
displayed when you click a user. These indications remain in place until the change to the
permission level is either committed or undone.
Attention: DatAdvantage supports only manual editing for Exchange storage groups; it does
not provide recommendations.
Note: Editing permissions and permission levels in Exchange Online is not supported.
You can only edit mailbox permissions at the level of the mailbox itself. You cannot edit the
permissions defined for a mailbox's folders, such as its inbox or its calendar. (However, sharing
permissions may be edited for the mailbox's individual folders.)
Note: You can access this dialog from the Users & Groups panes by clicking the name
of the permission level associated with the entity, but in this case the dialog box is
opened in read-only mode.
4. In the User or Group Names area, select the group or user whose permissions you want to
edit. (To add a user or group, click Add and browse to the required entity.)
5. In the Permissions for User area, select the permissions to be added to the entity, and clear
the permissions to be removed from the entity.
• The changes you make are marked in green and red, to indicate added and removed
permissions respectively.
• Each change you make automatically results in changes to other permissions in the virtual
sandbox.
6. Click OK.
You may edit sharing permissions for an entire mailbox, for individual folders within the mailbox, or
for public folders as necessary.
3. Right-click the mailbox or folder, and from the context menu, select Edit Permissions. The
Permissions dialog box is displayed, with the Mailbox Permissions tab open.
Note: You can access this dialog from the Users & Groups panes by clicking the name
of the permission level associated with the entity, but in this case the dialog box is
opened in read-only mode.
5. In the upper area, select the group or user whose permissions you want to edit. (To add a
user or group, click Add and browse to the required entity.)
The entity's permission level is indicated in the lower area.
6. Edit the entity's permissions as follows:
• To change the entity's permissions according to a built-in permission level, select the
required permission level from the list.
• To create custom permissions for the entity, select or clear the permissions in the lower
area as required.
• The changes you make are marked in green and red, to indicate added and removed
permissions respectively. This markup is also used to indicate the differences if you
change the built-in permission level associated with the entity.
• Each change you make automatically results in changes to other permissions in the virtual
sandbox.
7. Click OK.
• If opened from the Directories pane, this window displays all ACLs that exist on the
selected entity.
• If opened from the Users and Groups pane (following the selection of a directory service
entity), this window displays only the roles and ACEs that exist on that directory for the
selected account.
4. To view special permissions and advanced settings, click Advanced.
The Advanced Security Properties window is displayed.
This window displays all permission entries, or ACL trustees, that comprise the ACL.
5. To set the permission entries as inherited from their parent objects, select the option: Inherit
permission entries from parent that apply to child objects. Include these with entries explicitly
defined here.
6. To view more information about a permission entry, select it and click View.
The Permission Entry window is displayed.
7. Select Apply these permissions to objects and/or containers within this container only as
necessary.
4. On the New Group page of the wizard, set the following properties for the group you want to
create:
• Group path - Select the domain or OU in which to create the new group.
• Group name - Define a name for the new group.
• Group name (pre-Windows 2000) - If necessary, define the SAM account name for the
new group. Automatically populated when the Group name field is populated.
• Description - Enter a free-text description of the group, up to 1024 characters.
• Group scope - Determine the scope of the new group.
Note: This pane is only visible for Active Directory 2000 and higher.
• Domain local - A domain local group is a security or distribution group that can contain
universal groups, global groups, other domain local groups from its own domain, and
accounts from any domain in the forest. You can give domain local security groups
rights and permissions on resources that reside only in the same domain in which the
domain local group is located.
• Global - A global group is a group that can be used in its own domain, in member
servers and in workstations of the domain, and in trusting domains. In all those
locations, you can give a global group rights and permissions and the global group can
become a member of local groups. However, a global group can contain user accounts
that are only from its own domain.
• Universal - A universal group is a security or distribution group that contains users,
groups, and computers from any domain in its forest as members. You can give
universal security groups rights and permissions on resources in any domain in the
forest. Universal groups are not supported for Windows 2000.
• Group type - Determine whether the group is a security group or a distribution group.
5. Click Next.
The Members page is displayed.
6. To add members to the group, click Add and search for the required users in the Directory
Services Search dialog box.
Note: The entities available for selection are determined by the group scope you
defined earlier.
7. For advanced options in adding members to the group, click one of the following:
Note: The entities available for selection are determined by the group scope you
defined earlier.
• Add members from other groups - (this option will only display groups) opens the Directory
Services Search dialog box.
Use the functionality to search for users from other groups and then select one of the
following options in the Select which accounts are added area at the bottom:
• All selected accounts - All objects in Selected Entities will be added as direct members
to the new group and will be shown in the Members pane in the Group Creation
Wizard.
• All nested user and computer accounts - All user/computer members (direct and
indirect) are copied from the selected groups to the Members pane in the Group
Creation Wizard.
• Only the selected groups' first level child members - All selected users and direct group
members directly under the selected groups are copied to the Members pane in the
Group Creation Wizard.
• Add users or groups with existing permissions - opens the Users/Groups with Existing
Permissions dialog box and displays current existing permissions on the selected folder.
Select the users and groups from the Available Entities area for display in Selected
Entities. Select one of the following options in the Select which accounts are added area
at the bottom:
• All selected accounts - All objects in Selected Entities will be added as direct members
to the new group and will be shown in the Members pane in the Group Creation
Wizard.
• All nested user and computer accounts - All user/computer members (direct and
indirect) are copied from the selected groups to the Members pane in the Group
Creation Wizard.
• Only the selected groups' first level child members - All selected users and direct group
members directly under the selected groups are copied to the Members pane in the
Group Creation Wizard.
8. To remove members, select them from the list and click Remove.
Note: If you click Back and change the group scope or type, the members you already
selected will be removed from the list.
9. Click Next. The Excluded Users and Groups dialog box is displayed, with a list of exceptions
of users\groups that can not be added.
a. To add a permission entry to the entity, click Add and define the permissions as relevant.
b. To edit an existing permission entry:
1. Click Edit. The Permission Entry For dialog box is displayed.
2. From the Apply to drop-down list, select the objects to which the permissions will be
applied.
3. To apply these permissions to objects or containers within the current container,
select the relevant checkbox at the bottom of the dialog box.
14. After you have reviewed your work, click Execute to create the group.
15. Select the Commit these changes option to commit the changes immediately and click Finish.
Note: You may be required to provide your credentials before the Commit dialog box is
displayed.
Note: If the folder has inconsistent ACLs, the Commit these changes option is disabled.
4. Select the entity (user or group) to receive permission for the directory or file.
5. Click OK.
The Directory Services Search dialog box is closed, and the entities are granted minimum
permissions for the directory or file:
• R - Read. The user or group may read from the directory or file
• X - Execute. The user or group may execute files in the directory or file
6. Edit the permissions as necessary.
• The changes you make are marked in green and red, to indicate added and removed
permissions respectively.
• Each change you make automatically results in changes to other permissions in the virtual
sandbox.
7. Synchronize the system.
1. In the Work Area, right-click the folder for which you want to create a sub-folder, and select
Create New Folder.
The Create New Folder dialog box is displayed. Note that Parent folder path is already
populated according to the folder you selected.
2. Do as follows:
• Parent folder path - Browse for the parent folder of the folder that you are creating, or
accept the default.
• Folder name - The name of the folder that you are creating.
• Share Folder - Select whether to share the folder. If so, the share will have the same name
as the folder. Additionally, the share will be created with the Everyone group with full
control permissions.
• Commit these changes - Select to commit the changes.
• Cancel - Leave the process without saving any changes.
3. Click OK.
The new folder is displayed in the Work Area, in sandbox mode.
The changes take effect when you commit them to the environment.
Note:
• In addition to the method described here, you can also change a folder with inherited
permissions to Protected by removing any of the inherited permissions. If you do so, a
confirmation message is displayed, enabling you to change the folder to Protected before
removing the permissions.
The entity's icon is decorated with a lock to indicate it is protected. The Recommended Users
and Groups list is updated accordingly.
5. Synchronize the system.
You are about to remove the protection flag from this directory.
Do you want to leave existing unique permissions?
The lock decorating the entity's icon is removed. The Recommended Users and Groups list is
updated accordingly.
5. Synchronize the system.
The person image decorating the entity's icon is removed. The Recommended Users and
Groups list is updated accordingly.
5. Synchronize the system.
Creating Groups
Before your first use of the Group Creation Wizard, configure the relevant settings on the Group
Creation tab in the Management Console. Only users with the Commit/Edit role can create groups.
To create a new group:
4. On the New Group page of the wizard, set the following properties for the group you want to
create:
• Group path - Select the domain or OU in which to create the new group.
• Group name - Define a name for the new group.
• Group name (pre-Windows 2000) - If necessary, define the SAM account name for the
new group. Automatically populated when the Group name field is populated.
• Description - Enter a free-text description of the group, up to 1024 characters.
• Group scope - Determine the scope of the new group.
Note: This pane is only visible for Active Directory 2000 and higher.
• Domain local - A domain local group is a security or distribution group that can contain
universal groups, global groups, other domain local groups from its own domain, and
accounts from any domain in the forest. You can give domain local security groups
rights and permissions on resources that reside only in the same domain in which the
domain local group is located.
• Global - A global group is a group that can be used in its own domain, in member
servers and in workstations of the domain, and in trusting domains. In all those
locations, you can give a global group rights and permissions and the global group can
become a member of local groups. However, a global group can contain user accounts
that are only from its own domain.
• Universal - A universal group is a security or distribution group that contains users,
groups, and computers from any domain in its forest as members. You can give
universal security groups rights and permissions on resources in any domain in the
forest. Universal groups are not supported for Windows 2000.
• Group type - Determine whether the group is a security group or a distribution group.
5. Click Next.
The Members page is displayed.
6. To add members to the group, click Add and search for the required users in the Directory
Services Search dialog box.
Note: The entities available for selection are determined by the group scope you
defined earlier.
7. For advanced options in adding members to the group, click Advanced Options to open the
Directory Services Search dialog box.
Note: The entities available for selection are determined by the group scope you
defined earlier.
8. Use the functionality to search for users from other groups and then select one of the
following options in the Select which accounts are added area at the bottom:
• All selected accounts - All objects in Selected Entities will be added as direct members to
the new group and will be shown in the Members pane in the Group Creation Wizard.
• All nested user and computer accounts - All user/computer members (direct and indirect)
are copied from the selected groups to the Members pane in the Group Creation Wizard.
• Only the selected groups' first level child members - All selected users and direct group
members directly under the selected groups are copied to the Members pane in the
Group Creation Wizard.
9. To remove members, select them from the list and click Remove.
Note: If you click Back and change the group scope or type, the members you already
selected will be removed from the list.
10. Click Next. The Excluded Users and Groups dialog box is displayed, with a list of exceptions
of users\groups that can not be added.
12. After you have reviewed your work, click Execute to create the group.
Deleting Groups
You can delete groups from the Recommended Users and Groups pane, according to the
following guidelines:
• Only Active Directory and local host groups can be deleted.
• Abstract and built-in groups cannot be deleted.
• Rollback is not supported. Once a group is deleted, the same group with the same SID cannot
be recreated with the original permissions.
To delete a group:
Note:
• This procedure cannot be performed on distribution groups.
• You cannot view the mailboxes of synchronized cloud users or groups if you have
selected to display only entities from the Azure domain in the Users & Groups pane. In this
case, to view the mailboxes related to a synchronized cloud user or group, you must first
locate the domain user or group. For more information, see Locating Domain Users and
Groups.
Note: The user list must be filtered to display only users or groups from the Azure
domain. For instructions, see Viewing Azure Active Directory Objects in the Users &
Groups Pane.
3. To locate the domain user that was synchronized to Azure Active Directory, from the context
menu, select Locate Domain User.
4. To locate the domain group that was synchronized to Azure Active Directory, from the context
menu, select Locate Domain Group.
The domain user or group is identified and displayed in the Recommended Users & Groups
pane.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Select Account Management > Create User.
The Create User dialog box is displayed.
3. Set all properties as required on each tab and click OK when finished.
4. Enter the credentials of the user authorized to perform the commit action.
5. Click OK.
The Action Processing dialog box is displayed.
6. To filter the processing results, select the relevant option in the Filter by area:
• All
• Successful
• Failed
• Skipped
7. To export the processing results to a CSV file, click the Export to CSV button on the right and
select the required export path.
8. Click Close.
2. Click the Browse button next to the Path text box to select the organizational unit in which the
user will be created from the Organizational Unit dialog box.
The path is the organizational unit or domain in which the user is created.
3. Enter the user's first name.
4. Enter the user's last name.
5. Enter the user's initials (maximum 6 characters).
6. Enter the user's full name (mandatory field).
7. Enter the user's display name (maximum 20 characters).
8. Enter the user's logon name (mandatory field).
9. Enter the user's logon name (pre-Windows 2000). This is a mandatory field.
10. Enter the user's Email address.
11. If there are comments, enter them in the Description text box.
2. In the Password area, enter the user's password according to configured password policy.
a. Select Auto-generate Password if you want to use an automatically generated password.
b. To enter a password of your choice, select Type a Password. Enter and confirm the
password (mandatory fields).
c. Tick the User must change name at next logon checkbox to select this option.
d. Tick the User cannot change password checkbox to select this option.
e. Tick the Password never expires checkbox to select this option.
3. In the Account area, select the date on which the account expires.
a. If the account never expires, select Never.
b. If the account expires on a specific date, select End of and select the date from the
calendar.
4. Select the relevant options for configuring the account:
• Account is disabled
• Store password using reversible encryption
• Smart card is required for interactive logon
• Account is trusted for delegation (Win 2000/2003)
• Account is sensitive and cannot be delegated
• Use Kerberos DES encryption types for this account
• This account supports Kerberos AES 128-bit encryption (Win 2008, 2008R2 and higher)
• This account supports Kerberos AES 256-bit encryption (Win 2008, 2008R2 and higher)
• Do not require Kerberos pre-authentication
Note: To enable creating mailboxes from within DatAdvantage, basic authentication must
be enabled on the Exchange server through the IIS manager. See Metadata Framework
Installation Guide for details.
2. To add properties, open the Management Console and select Configuration > Active
Directory Properties.
The Domain users group is added automatically and set as the Primary Group. It is possible to set
a different group as the Primary Group if you want to remove the original one.
Note: There is no need to change the Primary Group unless you have Macintosh clients or
POSIX-compliant applications. Only a Domain group whose scope is global or universal can
be set as the Primary Group.
Note: A path must be configured on the General tab. The path is the organizational unit
or domain in which the user will be created.
2. To add the required groups, click Add to select the group from the dialog box.
The group is added to the group list.
3. To remove a group, select the group and click Remove.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Right-click the user and select Account Management > Edit.
The Edit User dialog box is displayed.
3. Select the tab and make the necessary changes. Enter all required properties.
4. Click OK.
5. Enter the credentials of the user authorized to perform the commit action.
6. Click OK.
The Action Processing dialog box is displayed.
7. To filter the processing results, select the relevant option in the Filter by area:
• All
• Successful
• Failed
• Skipped
8. To export the processing results to a CSV file, click the Export to CSV button on the right and
select the required export path.
9. Click Close.
3. Select each tab in turn and enter the necessary information. See the instructions for the other
tabs for more information.
4. On the Member Of tab, click Remove All Recommendations
5. Click OK.
6. Enter the credentials of the user authorized to perform the commit action.
7. Click OK.
The Action Processing dialog box is displayed.
8. To filter the processing results, select the relevant option in the Filter by area:
• All
• Successful
• Failed
• Skipped
9. To export the processing results to a CSV file, click the Export to CSV button on the right and
select the required export path.
10. Click Close.
Creating Groups
Before your first use of the Group Creation Wizard, configure the relevant settings on the Group
Creation tab in the Management Console. Only users with the Commit/Edit role can create groups.
To create a new group:
4. On the New Group page of the wizard, set the following properties for the group you want to
create:
• Group path - Select the domain or OU in which to create the new group.
• Group name - Define a name for the new group.
• Group name (pre-Windows 2000) - If necessary, define the SAM account name for the
new group. Automatically populated when the Group name field is populated.
• Description - Enter a free-text description of the group, up to 1024 characters.
• Group scope - Determine the scope of the new group.
Note: This pane is only visible for Active Directory 2000 and higher.
• Domain local - A domain local group is a security or distribution group that can contain
universal groups, global groups, other domain local groups from its own domain, and
accounts from any domain in the forest. You can give domain local security groups
rights and permissions on resources that reside only in the same domain in which the
domain local group is located.
• Global - A global group is a group that can be used in its own domain, in member
servers and in workstations of the domain, and in trusting domains. In all those
locations, you can give a global group rights and permissions and the global group can
become a member of local groups. However, a global group can contain user accounts
that are only from its own domain.
• Universal - A universal group is a security or distribution group that contains users,
groups, and computers from any domain in its forest as members. You can give
universal security groups rights and permissions on resources in any domain in the
forest. Universal groups are not supported for Windows 2000.
• Group type - Determine whether the group is a security group or a distribution group.
5. Click Next.
The Members page is displayed.
6. To add members to the group, click Add and search for the required users in the Directory
Services Search dialog box.
Note: The entities available for selection are determined by the group scope you
defined earlier.
7. For advanced options in adding members to the group, click Advanced Options to open the
Directory Services Search dialog box.
Note: The entities available for selection are determined by the group scope you
defined earlier.
8. Use the functionality to search for users from other groups and then select one of the
following options in the Select which accounts are added area at the bottom:
• All selected accounts - All objects in Selected Entities will be added as direct members to
the new group and will be shown in the Members pane in the Group Creation Wizard.
• All nested user and computer accounts - All user/computer members (direct and indirect)
are copied from the selected groups to the Members pane in the Group Creation Wizard.
• Only the selected groups' first level child members - All selected users and direct group
members directly under the selected groups are copied to the Members pane in the
Group Creation Wizard.
9. To remove members, select them from the list and click Remove.
Note: If you click Back and change the group scope or type, the members you already
selected will be removed from the list.
10. Click Next. The Excluded Users and Groups dialog box is displayed, with a list of exceptions
of users\groups that can not be added.
12. After you have reviewed your work, click Execute to create the group.
1. From the Recommended Users and Groups pane, right-click the group to which you want
to add the members of another group as members, and select Account Management >
Advanced Membership.
The Directory Services Search dialog box is displayed.
2. Use the functionality to search for users from other groups and then select one of the
following options in the Select which accounts are added area at the bottom:
• All selected accounts - All objects in Selected Entities will be added as direct members to
the group in the the Recommended Users and Groups pane.
• All nested user and computer accounts - All user/computer members (direct and indirect)
are copied from the selected groups to the group in the Recommended Users and Groups
pane.
• Only the selected groups' first level child members - All selected users and direct group
members directly under the selected groups are copied to the group in the Recommended
Users and Groups pane.
3. Click OK when done.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Select Account Management > Delete User/Computer.
The Delete User/Computer dialog box is displayed.
7. To filter the processing results, select the relevant option in the Filter by area:
• All
• Successful
• Failed
• Skipped
8. To export the processing results to a CSV file, click the Export to CSV button on the right and
select the required export path.
9. Click Close.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Right-click the chosen entities and select Account Management > Delete User/Computer.
A confirmation message is displayed.
Note: When selecting multiple entities, it is possible that not all entities are valid for this
action for this entity type, domain type, or for unmonitored, abstract, or built-in accounts.
3. Click Yes.
4. Enter the credentials of the user authorized to perform the commit action.
5. Click Yes.
The Action Processing dialog box is displayed.
6. To filter the processing results, select the relevant option in the Filter by area:
• All
• Successful
• Failed
• Skipped
7. To export the processing results to a CSV file, click the Export to CSV button on the right and
select the required export path.
8. Click Close.
Resetting Passwords
There are two methods for resetting a password:
• Through the Account Management button
• Through the context menu
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Select Account Management > Reset Password.
The Reset Password dialog box is displayed.
10. To filter the processing results, select the relevant option in the Filter by area:
• All
• Successful
• Failed
• Skipped
11. To export the processing results to a CSV file, click the Export to CSV button on the right and
select the required export path.
12. Click Close.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Right-click the chosen entities and select Account Management > Reset Password.
The Reset Password dialog box is displayed.
Note: When selecting multiple entities, it is possible that not all entities are valid for this
action for this entity type, domain type, or for unmonitored, abstract, or built-in accounts.
6. Enter the credentials of the user authorized to perform the commit action.
7. Click OK.
The Action Processing screen is displayed.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Select Account Management > Unlock.
The Unlock User dialog box is displayed.
7. To filter the processing results, select the relevant option in the Filter by area:
• All
• Successful
• Failed
• Skipped
8. To export the processing results to a CSV file, click the Export to CSV button on the right and
select the required export path.
9. Click Close.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Right-click the chosen entities and select Account Management > Unlock.
The Unlock User dialog box is displayed.
Note: When selecting multiple entities, it is possible that not all entities are valid for this
action for this entity type, domain type, or for unmonitored, abstract, or built-in accounts.
3. Click OK.
4. Enter the credentials of the user authorized to perform the commit action.
5. Click Yes.
The Action Processing dialog box is displayed.
6. To filter the processing results, select the relevant option in the Filter by area:
• All
• Successful
• Failed
• Skipped
7. To export the processing results to a CSV file, click the Export to CSV button on the right and
select the required export path.
8. Click Close.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Select Account Management > Disable/Enable.
The Disable/Enable Account dialog box is displayed.
7. To filter the processing results, select the relevant option in the Filter by area:
• All
• Successful
• Failed
• Skipped
8. To export the processing results to a CSV file, click the Export to CSV button on the right and
select the required export path.
9. Click Close.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Right-click the chosen entities and select Account Management > Disable/Enable.
The Disable/Enable Account dialog box is displayed.
Note: When selecting multiple entities, it is possible that not all entities are valid for this
action for this entity type, domain type, or for unmonitored, abstract, or built-in accounts.
6. To filter the processing results, select the relevant option in the Filter by area:
• All
• Successful
• Failed
• Skipped
7. To export the processing results to a CSV file, click the Export to CSV button on the right and
select the required export path.
8. Click Close.
Moving Entities
There are two methods for moving entities:
• Through the Account Management button
• Through the context menu
Entities can only be moved to another location within their current domain.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Select Account Management > Move.
The Move Account dialog box is displayed.
8. To filter the processing results, select the relevant option in the Filter by area:
• All
• Successful
• Failed
• Skipped
9. To export the processing results to a CSV file, click the Export to CSV button on the right and
select the required export path.
10. Click Close.
1. Select the Existing Users and Groups pane on the left, or the Recommended Users and
Groups pane on the right.
2. Right-click the chosen entities select Account Management > Move.
The Move Account dialog box is displayed.
Note: When selecting multiple entities, it is possible that not all entities are valid for this
action for this entity type, domain type, or for unmonitored, abstract, or built-in accounts.
6. To filter the processing results, select the relevant option in the Filter by area:
• All
• Successful
• Failed
• Skipped
7. To export the processing results to a CSV file, click the Export to CSV button on the right and
select the required export path.
8. Click Close.
About Synchronization
To conserve resources, the effects of manual changes are not automatically calculated across
the system. This means that changes remain visible, but the sandbox is not updated and no error
calculation occurs.
However, you can choose to synchronize your manual changes as necessary. The synchronization
process implements the manual changes in the virtual environment, so that erroneous
recommendations and the explanations provided in the Directories pane for removing permissions
are up to date.
When the system is not synchronized, the Status bar displays a message saying "Calculate Access
Errors".
In addition, the Errors pane does not display the most updated information.
Synchronizing Recommendations
To synchronize changes in the system:
3. To refresh the Directories pane, double-click the entity that was changed.
DataPrivilege objects and owners are also synchronized to DatAdvantage for monitored
resources. However, if a file server managed in DataPrivilege does not exist in DatAdvantage,
the synchronization engine does not create it in DatAdvantage since this would require a full
installation procedure.
However, if the previous synchronization ended with errors or conflicts, it may be necessary to
execute the Synchronization process manually.
If this happens, you must manually change one of the base folders so that it is no longer defined
as a base folder, and rerun the synchronization process.
By default, IDU Analytics looks back 120 days to make recommendations (this can be configured at
installation).
Use the list as a reference to determine which rights can be removed without impacting on users'
ability to access the data they need in order to do their work.
Immediately after IDU Analytics runs, no errors due to analysis are listed. If user behavior changes
between analyses, the unexpected behavior is reflected in the error list. Over time, the analysis
becomes more accurate as additional user behavior data is processed by subsequent runs of
IDU Analytics. This means the number of analysis errors (as opposed to manual editing errors)
decreases.
The system must be synchronized so that the Errors pane displays the most updated information.
Note: The tactical errors calculation is based on statistics collected for the previous IDU
Analytics period. If the statistics archive policy is shorter than the IDU Analytics period, then
the tactical errors calculation will be based only on statistics that are not archived.
Note:
If the removed permission has not been used by any event performed by the user during the
most recent IDU Analytics-defined period of time, no error will be generated.
Note: In the Review Area, the Expected Access Errors pane is automatically filtered by
the selected object.
3. Use DatAdvantage's standard sorting and grouping functions to locate the data you need
quickly.
4. To view recommended permissions for entities, double-click the relevant directory or file in
the Errors tab to display the recommended permissions in the Directories pane.
5. Accept or reject the recommendations as required.
Note: If the Remove protection without unique permissions and Add protection with
copy permissions from parent commands are created on a folder together, only the
remove permission commands related to actual removed permissions are displayed. The
add permission commands that result from the add protection action are not seen. The
error is calculated only if the total effective permissions resulting from the remove and
add protection commands are not enough based on the events.
2. On the New Group page of the wizard, set the following properties for the group you want to
create:
• Group path - Select the domain or OU in which to create the new group.
• Group name - Define a name for the new group.
• Group name (pre-Windows 2000) - If necessary, define the SAM account name for the
new group. Automatically populated when the Group name field is populated.
• Description - Enter a free-text description of the group, up to 1024 characters.
• Group scope - Determine the scope of the new group.
Note: This pane is only visible for Active Directory 2000 and higher.
• Domain local - A domain local group is a security or distribution group that can contain
universal groups, global groups, other domain local groups from its own domain, and
accounts from any domain in the forest. You can give domain local security groups
rights and permissions on resources that reside only in the same domain in which the
domain local group is located.
• Global - A global group is a group that can be used in its own domain, in member
servers and in workstations of the domain, and in trusting domains. In all those
locations, you can give a global group rights and permissions and the global group can
become a member of local groups. However, a global group can contain user accounts
that are only from its own domain.
• Universal - A universal group is a security or distribution group that contains users,
groups, and computers from any domain in its forest as members. You can give
universal security groups rights and permissions on resources in any domain in the
forest. Universal groups are not supported for Windows 2000.
• Group type - Determine whether the group is a security group or a distribution group.
3. Click Next.
The Fix Errors page is displayed.
4. To add members to the group, click Add and search for the required users in the Directory
Services Search dialog box.
Note: The entities available for selection are determined by the group scope you
defined earlier.
Use the functionality to search for users from other groups and then select one of the
following options in the Select which accounts are added area at the bottom:
• All selected accounts - All objects in Selected Entities will be added as direct members
to the new group and will be shown in the Members pane in the Group Creation
Wizard.
• All nested user and computer accounts - All user/computer members (direct and
indirect) are copied from the selected groups to the Members pane in the Group
Creation Wizard.
• Only the selected groups' first level child members - All selected users and direct group
members directly under the selected groups are copied to the Members pane in the
Group Creation Wizard.
• Add users or groups with existing permissions - opens the Users/Groups with Existing
Permissions dialog box and displays current existing permissions on the selected folder.
Select the users and groups from the Available Entities area for display in Selected
Entities. Select one of the following options in the Select which accounts are added area
at the bottom:
• All selected accounts - All objects in Selected Entities will be added as direct members
to the new group and will be shown in the Members pane in the Group Creation
Wizard.
• All nested user and computer accounts - All user/computer members (direct and
indirect) are copied from the selected groups to the Members pane in the Group
Creation Wizard.
• Only the selected groups' first level child members - All selected users and direct group
members directly under the selected groups are copied to the Members pane in the
Group Creation Wizard.
6. To remove members, select them from the list and click Remove.
Note: If you click Back and change the group scope or type, the members you already
selected will be removed from the list.
7. Click Next. The Excluded Users and Groups dialog box is displayed, with a list of exceptions
of users\groups that can not be added.
a. To add a permission entry to the entity, click Add and define the permissions as relevant.
b. To edit an existing permission entry:
1. Click Edit. The Permission Entry For dialog box is displayed.
2. From the Apply to drop-down list, select the objects to which the permissions will be
applied.
3. To apply these permissions to objects or containers within the current container,
select the relevant checkbox at the bottom of the dialog box.
13. After you have reviewed your work, click Execute to create the group.
14. Select the Commit these changes option to commit the changes immediately and click Finish.
15. (Optional) Commit the changes.
Note: You may be required to provide your credentials before the Commit dialog box is
displayed.
The Review Area enables you to review the effects of the manual or recommended changes to
permissions on actual user activity. Use this view to test "what if" scenarios, prior to applying the
changes to the domain.
Sometimes IDU Analytics recommends that a user's permissions to a directory or file be removed,
but the user later accesses the directory. This means the recommendation to remove permissions
was made in error. That is, IDU Analytics has recommended removing a user's rights to files and
directories to which the user actually needs access. If the removal of permission were applied to
the domain, the user's work would be disrupted by the lack of permissions.
DatAdvantage identifies these errors by applying the modified permission set to past user
activity and examining the results. When a user's access to a resource would be denied due to a
recommended change in the user's permissions, the denial is flagged as an error and displayed in
both the Review Area and the Work Area.
Use the Review Area to identify such errors and eliminate them prior to applying changes to the
domain, to avoid potential disruption to work.
Before you begin to work with the Review Area, it is recommended that you synchronize the
system.
Note: Directory service permissions are not visible in the Review Area.
To view the status of permissions a user or group has for a specific directory:
Synchronizing Recommendations
To synchronize changes in the system:
3. To refresh the Directories pane, double-click the entity that was changed.
Note:
If the removed permission has not been used by any event performed by the user during the
most recent IDU Analytics-defined period of time, no error will be generated.
Note: In the Review Area, the Expected Access Errors pane is automatically filtered by
the selected object.
3. Use DatAdvantage's standard sorting and grouping functions to locate the data you need
quickly.
4. To view recommended permissions for entities, double-click the relevant directory or file in
the Errors tab to display the recommended permissions in the Directories pane.
5. Accept or reject the recommendations as required.
Note: If the Remove protection without unique permissions and Add protection with
copy permissions from parent commands are created on a folder together, only the
remove permission commands related to actual removed permissions are displayed. The
add permission commands that result from the add protection action are not seen. The
error is calculated only if the total effective permissions resulting from the remove and
add protection commands are not enough based on the events.
3. Use DatAdvantage's standard sorting and grouping functions to locate the data you need
quickly.
The Statistics view allows you to review the cumulative data collected by the DatAdvantage Probe.
At the end of each day, DatAdvantage generates the information required to view statistics. The
data is available for viewing the day after the events were recorded and collected, and remains
available for direct access until it is archived.
Table view:
3. Click each directory or file to drill down and view its utilization.
• The directories and files are displayed are from all the volumes of the selected resource.
They are not categorized into volumes, as they are in the Directory pane displayed in the
Work Area.
• The current directory or file is displayed at the top of the chart as the Parent Directory or
File.
• If you cannot click a directory, no further drill-down is possible. This occurs either because
there are no subdirectories, or because no events were logged for any subdirectory.
• Color-coding indicates the entity type:
• Yellow - Current directory
• Purple - Subdirectories
• Blue - Special files
4. Click the Back button at the top left of the chart to return to a higher level.
Graph view:
Table view:
abnormal user behavior. Your attention should be drawn to users with unexpectedly high event
counts.
To view statistics on user utilization:
Table view:
Graph view:
Table view:
Table view:
Graph view:
Table view:
Table view:
For Exchange resources, the chart displays bars for the selected resource's mailbox store and
public folders. With drill-down through the mailbox store, the bars display the same alphabetical
grouping that is used in the Directories pane. Further drill-down displays the actual mailboxes.
Graph view:
Table view:
Table view:
Graph view:
Table view:
Table view:
Graph view:
Table view:
Graph view:
Table view:
Graph view:
Table view:
Table view:
Graph view:
Table view:
If you jump to the Logs view, the log is automatically loaded with the relevant filters, so that it
reflects the events that comprise the selected graph portion.
BEST PRACTICE: It is important to emphasize that Varonis recommends you always start with
the Statistics view, identify the interesting information, and then drill down to the required log.
This provides the best system performance, and is the best workflow for smart usage of logs for
auditing purposes.
1. While you are working in the Statistics view, right-click the bar or pie slice for the entity in
question. A context menu is displayed, listing the views to which you can jump.
2. Select the required view. DatAdvantage jumps to that view, while maintaining focus on the
entity with which you are working.
1. From the Users and Groups pane or the Directories pane, select the group or the directory for
which you want to set an owner.
2. In the Graphs pane, select User Activity. A pie chart indicating usage per user is displayed.
3. Right-click the pie slice for the user you want to set as owner. A context menu is displayed.
4. Select Set Ownership. A confirmation message is displayed, asking you to confirm setting the
selected user as owner of the selected entity.
5. Click Yes. The user is set as the entity's owner
Inactive N/A
Directories
The Logs view enables you to browse and search the event logs from all the monitored resources
for a specific day, down to the level of a single event.
Viewing Logs
You can view the logs based on the entity you selected in the Entity Selection pane as follows:
• Resource - Displays all the events for a given resource.
• Directory - Displays all the events for a directory, subdirectories and files.
• OU - Displays all the events for a given OU.
• User or group - Displays the events for a specific user or group.
To view a log:
Note: You may use only the Search and Advanced Search options if you want, without
first selecting an entity.
4. In the Search pane, set the value of the criterion you want to search by. Options are:
• When did the event occur? - Select the time frame in which the event occurred. If you
select Today, you must first synchronize events (select Tools > Log > Synchronize Latest
Events).
Note: It is not recommended to select Today as your time frame, as it may produce
limited results and the synchronization process may have a negative effect on
performance.
• Where did the event occur? - Select the resources you want to search in.
• What type of even occurred? - Select the checkboxes of the operations you are interested
in.
• Who generated the event? - Click the Browse button to select users you are interested in.
• Directory filters
• Which object was accessed? - Click the Browse button to select a specific folder, file,
user or group. Select the Search in child objects checkbox as necessary.
• Which files were accessed? - Type the names of specific files you are interested in. Use
a comma (,) to separate names.
• Mail-related filters - Only for Exchange mailboxes
• Which user received the email? - Type the email address of the mail recipient you are
interested in.
• Who sent the mail? - Type the name of the mail sender you want to search for.
• Which file was attached? - Type the name of the file that was attached to the mail
message.
• What is the event item type? - Select the type of mailbox event you are interested in.
5. To define more complex criteria, click Advanced Search and define the search string
as required. Any criteria you have already defined in the simple search are populated
automatically in the advanced search. See Advanced Searching.
• Computer accounts do not appear in any of the pickers. To search for a computer account,
type the name of the computer in the relevant user filter.
Note: For a complete description of all available filters, see DatAdvantage and Sub-
Products Filters.
6. To save your search criteria or load a saved search, click Save/Load Query Definitions and
then select either Save or Load, as relevant.
7. When you are done setting search criteria, click the Search button. The relevant log file is
displayed in the bottom pane. For information on all columns that can be displayed in the log,
see Log Columns.
8. To navigate the log:
• Click Retrieve 200 More to view another 200 records.
Important: This button retrieves the records at random, without regard to the first,
last, next, sorted sets, data source (i.e., resource), etc. Each time the button is clicked,
• Click Retrieve All to view all the records in the log (this may take some time).
• Use the Up and Down arrows next to the Page field to move to the required page of the
log.
• Use the Up and Down arrows for the Records per page field to set the number of records
displayed on each page of the log.
9. To view the log data for a single event, double-click the event's row in the log. The Event
Details window is displayed, showing the event's data on the General tab.
Note: The Event Details window shows information on all columns in the log. To add or
remove log columns, see Adding and Removing Log Columns.
10. To view changes made to Group Policy Object (GPO) settings, select the GPO Changes tab.
The GPO Changes tab is displayed, showing the GPO setting changes.
Note: The GPO Changes tab is displayed only if GPO settings for that event were
modified.
Log Columns
You can customize which columns are included in logs (for more information, see Adding and
Removing Log Columns).
You can also change the order in which the columns are displayed, sort columns, and group
columns as required. For more information, see Working with Lists and Tables. Display
preferences are automatically saved in the user's profile.
The following table describes all columns and column types that can be included in the log:
Commit Process The ID of the process in which the change was committed.
ID
Device IP The IP address of the user from which the event originated.
Address
Device Name The resolved hostname of the Device IP from which the event
originated.
Event Count The number of times a single event was logged. For example, if the
same file was opened by the user several times in a single day, this
field displays the total number of identical events.
Event Operation Indicates what happened during the event. Also indicates access
denied events, that is, events that failed because the user did not
have sufficient permission.
Event Time The time, as configured on the file server, at which the event
occurred.
File Server/ The name of the file server or domain on which the event
Domain occurred.
Object The display name of the object on which the event occurred.
Object Type The type of object on which the event occurred, which can be:
• File
• Folder
• Group
• User
Path The path name of the accessed object. For directory service
objects, this is the distinguished name.
Permissions After • Audit events - The permissions that existed on the object
Change following the change.
• History of differences events - This column is empty.
Permissions • Audit events - The permissions that existed on the object prior
Before Change to the change.
• History of differences events - This field is empty.
Shared Externally Files, folders and sites in SharePoint Online that are shared with
external users.
Trustee • The name of the user (in the format Domain\Username) that
was granted permission.
• The column is empty if a folder's protection was changed in a
Protection Added or Protection Removed event.
• The name of the new owner (in the format Domain\Username) if
ownership was changed in an Owner Changed event.
Trustee Account Indicates the type of account for which permissions have changed
Type (i.e., a user, group or a computer).
Mail Properties The following columns can be added to the log: (Only available for
Exchange resources.)
• Attachment Name - The name of a file (if any) that was attached
to the mail
• Exchange Client Type - The type of client used to access the
mailbox
• Mail Date - The date on which the mail was sent
• Mail Item Type - The mail type, such as mail message, accept
meeting, and task
• Mail Recipients - The email addresses of the users who
received the mail
• Mail Source - The email address of the user that sent the mail
• Mail Access Type - The type of user who accessed the mailbox,
which can be:
• Owner - The mailbox owner
• Non owner - All users except the mailbox owner
Printing Logs
To print a log:
Note: This function is available only to users who have the Report View role. In addition,
those having the Enterprise Managers, System Administrator, Power User or Users roles can
generate alerts from the Log view if they also have the DatAlert Configuration role.
DatAdvantage tracks the number of access events generated by each user on a daily basis.
Access events include, among other actions, opening, creating, deleting, and moving (renaming)
files or directories.
Each night, DatAdvantage calculates the daily average for each user's access events over the
previous 60 days (the time period is configurable), as well as the standard deviation of each user's
daily access events. If, on any given day, the total number of a user's access events "spikes," or is
greater than that user's daily average by more than a multiple (coefficient, by default=3) of his or
her standard deviation, and the user exceeded the threshold (by default = 10,000), DatAdvantage
generates an alert, which is displayed in the Alerts view.
The severity of an alert is dictated by the number of consecutive days on which the alert was
generated for the specific user. That is, if a user creates an alert three days in a row, one alert is
written with a severity of 3. The maximum severity is set to 8.
Example
When the alerts settings are configured as follows:
• Alert utilization coefficient - set to 3
• Alert utilization threshold - set to 1,000
• Alert configuration period - set 4 days
If on day 5 the user generates 1,300 events, DatAdvantage generates an alert because the user
exceeded his or her daily average by 3.5 times the standard deviation (greater than the set Alert
utilization coefficient) and created more than 1,000 events (greater than the set Alert utilization
threshold).
Viewing Alerts
To view alerts:
• Type - The entity for which the alert was generated. Possible types:
• User
• Group
• Entity Name - The name of the entity for which the alert was generated.
• Alert Type - The type of alert.
• Alert Name - The name of the alert.
• Start Date - The date on which the unusual behavior began.
• End Date - The date on which the unusual behavior ended.
• Severity - The severity of the unusual behavior.
5. Use DatAdvantage's standard sorting and grouping functions to locate the data you need
quickly.
6. In the Activity By Date pane, click the column for a specific date to view information for that
day.
7. Use the Alerts report subscription option to receive regular reports regarding alerts in your
system.
DatAdvantage typically generates a handful of alerts each day, which can usually be investigated
in a short period of time. When you do your daily review of the DatAdvantage alerts, it is helpful to
double-click each alert to determine the following:
• Was the alert generated by a privileged or administrative account?
• Was the activity deviation thousands or tens of thousands of events?
If the answer to either or both of these questions is yes, the alert probably deserves investigation.
Analyzing Alerts
To analyze an alert:
1. Click the bar corresponding to the day on which the alert was generated to jump to the
Statistics view. The directories that were accessed are displayed.
2. Check the Logs view for additional information. The Logs view displays the files that were
accessed, and indicates whether they were opened, deleted, moved, and so on.
Inappropriate Access
While DatAdvantage makes identifying the technical cause of a usage spike simple, it can
sometimes be more difficult to discern whether the activity was appropriate or inappropriate,
well-intentioned or otherwise. Until clear policies and processes concerning appropriate
and inappropriate access are created, distributed, and reviewed, it is usually best to adopt a
methodology similar to the following:
1. Determine a list of directories containing critical or sensitive files, and the parties responsible
for them (that is, their owners).
2. Agree on a process to handle alerts concerning sensitive data with the data owners. This
might include notification, generation of activity reports, and so on.
3. When an alert arises concerning sensitive data, follow the agreed upon process.
4. When a user or administrator account generates an alert on any other (non-sensitive) data
and the cause is unknown or not easily discernible, ask the user or administrator in question if
they know what might have caused a spike in his or her activity.
5. If the cause still cannot be determined and the pattern is repeated, consider asking the user
to change his or her password.
The Reports view enables you to define reports to be sent periodically (or only once) by email,
or be stored on a file system share. You can also view reports online, and store snapshots of
important reports. This view comprises the following panes:
• Reports List
• My Subscriptions
• Viewer - Includes the following panes:
• Search conditions
• Help display
• Table view
For a complete description of all reports available in DatAdvantage, see Metadata Framework
Reports.
• In the Find Report field, type the terms by which you want to search. The search is carried out
on the following fields:
• Template name
• Template description
• ID column (even if the view mode is not set to Hide Categories)
• Report name
• Report category
• The search is not case-sensitive.
• Use a plus sign (+) to search for more than one term. For example, searching everyone +
permissions returns all reports that include both everyone and permissions.
• The categories and reports in the results are fully expanded following your search, regardless
of other view options you may have set.
• To reload the full report list, click the X in the Find Report field or delete the input you entered.
1. Group and sort the list as necessary according to standard DatAdvantage procedures (see
Working with Lists and Tables).
2. To expand or collapse the grouped, sorted list, right-click a category and select Expand All
Groups or Collapse All Groups, as relevant.
3. To hide the report categories and view all report templates as a flat list, select View > Hide
Categories.
• A flat list is displayed, regardless of other grouping, sorting or search criteria you may have
set.
• To show report categories again, clear this option.
After you have accessed the DatAdvantage Operational Log, you can customize a template for it
or create a subscription to it according to standard DatAdvantage procedures.
With report templates, authorized users can start with a predefined template, and then:
• Set the default filters and filter values you want for the template.
• Choose the columns to be displayed in the report, based on:
• Directory service (Active Directory) properties
• File system properties
• Other available columns
• Set sorting and grouping options.
• Choose the look and feel of reports.
• Select predefined themes, including your own customized themes
• Use a custom logo in generated reports
• Set various display options for the selected columns.
Upgrade
During upgrade, subscriptions that were created before templates were introduced or customized
are updated accordingly, such that new templates are created that include the relevant
customizations.
Roles
The following roles can customize report templates:
• Enterprise managers
• System administrators
• Users with the Reports view-based role
Note: If you make changes to a predefined template, you must click Save As to save it
under a new name.
1. In the Search pane, select the Filters tab and set filters as relevant. For complete instructions
on setting filters, see Advanced Searching.
2. To export your filter definitions to an XML file for easy reuse, select Import/Export Filter >
Export to File and save the file.
3. To import your saved filter definitions, select Import/Export Filter > Import from File and
select the relevant file.
4. To save the filters as part of your template, click Save or Save As, as relevant.
Note: If you make changes to a predefined template, you must click Save As to save it
under a new name.
2. From Available columns on the left, select the columns you want to add to the report and click
the right arrow to move your choices to Your selection on the right.
3. In the Your selection area, do the following as preferred:
• To group report results by a particular column, select the Grouped by check box for that
column.
• To reorder columns, select a column to move and use the up and down arrows to set its
position in the report.
4. Click Reset to restore the set of columns and groupings that were last saved with your
template.
2. From the Available metrics on the left, select the metrics you want to add to the report and
click the right arrow to move your choices to Your selection on the right.
3. In the Your selection area, do the following as preferred:
• To change the line color for each metric, select the required color from the Color drop-
down list for that metric.
• To change the line type for each metric, select the required color from the Line Type drop-
down list for that metric. The following line types are available:
• Solid
• Dotted
• Dashed
Note: By default, the color and line type for each metric are automatically selected.
4. To view the data labels on the Y axis of the line chart, select the Show data labels on chart
check box on the top right of the Chart Data tab.
5. Click Reset to restore the set of metrics, colors and line types that were last saved with your
template.
2. From the Business units selection on the left, do one of the following:
• Select the Top business units for the selected trend option and set the number of business
units for display in the bar chart.
Note: If selected, the bar chart will display the selected number of business units
with the highest average metric values during the defined time period. An overview
of business unit metrics is displayed in the bar chart. This option does not display the
data according to the time period defined by the interval filter.
• Select the Manually select the business units option and do the following:
• Select the business units you want to add to the report and click the right arrow to
move your choices to Your selection on the right.
• To change the color for each business unit, select the required color from the Color
drop-down list for that business unit.
Note: This step is optional. By default, the color for each business unit is
automatically selected.
Note: The Manually select the business units option is selected by default.
3. To view the data labels on the Y axis of the bar chart, select the Show data labels on chart
check box on the top right of the Chart Data tab.
4. Click Reset to restore the set of business units and colors that were last saved with your
template.
Note: The Title and Subtitle options you set are also applied to your subscriptions for
this template.
• Look and feel - If you have prepared a customized look and feel, select it from the drop-
down list.
• Show in report - Select the report elements you want to show in your template:
• Description - Displays the template's description as part of the generated report
• Filter - Displays the filters you set as part of the generated report
• Logo - Displays the logo you choose (or the default Varonis logo) as part of the
generated report
• Results grouping - Select your preferences for grouping the results returned in the
generated report. Options are:
• Collapse groups
• Hide number of nested rows
When you create or edit a template, you can select the users that can see it. Only users who have
permission can:
The Privacy Settings tab is only visible to the template owner and the Enterprise Manager (if
configured).
2. From the drop-down list, select the users that can see the template. Options are:
• All users
• The template owner
Note:
• See Setting Display Options for instructions on setting the owner.
• Keep in mind the Enterprise Manager may be able to see all templates and
subscriptions, regardless of the setting you choose here. See the Management
Console User Guide for more information.
• The template owner and the following users/groups - If you select this option, click the
green plus sign to select the required users and groups.
If you have well-defined filters, you can export them to XML files for later use and import saved
files.
1. Expand the Reports List and select the customized report template you want to edit.
2. Edit the template as required.
3. Save the edited template.
1. Expand the Reports List and select the customized report template you want to edit.
2. Click Delete.
The template is deleted.
• In the Search pane, click Hide Search. The Search pane is hidden.
•
From the Table View, click the Help View button . The Help View is displayed.
Previewing Reports
The report preview window displays the fully formatted report, not just the raw report data.
To preview reports:
3. On the report toolbar, use the following buttons to perform various activities with the report:
•
- To navigate the report.
• - To stop rendering the generated report.
• - To refresh the generated report.
• - To print the report.
• - To set the print layout.
• - To determine the page setup for the printed report.
• - To save the generated report to Word, Excel or PowerPoint.
•
- To set the screen magnification.
•
- To find specific text in the generated report.
4. Once column order and grouping options are defined, you can expand or collapse rows in the
generated report as necessary:
1. In the Search pane, click Run. The report results are displayed in the Table View.
Exporting Reports
You can export reports to the following formats:
• CSV
• HTML
• Excel
• PDF
Subscribing to Reports
BEST PRACTICE
For performance reasons, Varonis highly recommends you subscribe to reports so that you can
receive them regularly by email, instead of generating them directly in the Viewer.
To subscribe to a report:
1. In the Reports List or the Viewer, click the Subscription button. The Subscription dialog box
is displayed.
The Report Server - Email option enables you to send a report subscription to designated
recipients.
• Priority - From the drop-down list, select the relevant delivery priority.
• Comment - Type a free-text comment in the field as necessary.
4. Click OK to close the subscription form, or click another tab to continue defining the
subscription.
The Report Server Email (Data-Driven) option enables you to filter report contents according to the
recipient's owned objects.
For several reports, you can define subscriptions that include the data of both data owners
and their subordinates. This hierarchical subscription means managers can view information
regarding all the data for which they are ultimately responsible, without the need to be data
owners themselves.
To send the report only to selected owners (both users or groups - if the latter, first-level members
will receive the email):
Note: Data-driven subscriptions are not sent to group owners or domain custodians if the Do
not provide activity information to group owners or domain custodians option is selected on
the DatAdvantage Security page of the Management Console.
1. From the Delivered by drop-down list, select Report Server Email (Data-Driven).
2. Select the Always send this report, even if empty option as required.
3. Choose Selected Recipients.
6. Add recipients as necessary. Select users and/or groups that are defined as resource/domain
custodians.
7. Set the required email settings:
• Subject - Type the subject line of the report.
• Display report data in the subject field - Select to display the template name and creation
date as a prefix to the subject. If the subject field is otherwise empty, the report data is
displayed as the subject.
• Include report - Select to include the actual report in the email.
• Format - From the drop-down list, select the format in which the report is to be delivered
(only if you chose to include the report with the email).
• Acrobat (PDF) file
• CSV (comma-delimited) file
• Excel (xls)
• Excel (xlsx)
• TIFF file
• Web archive
• XML
• Include link - Select to include a link to the report's location on the IDU server.
• Priority - From the drop-down list, select the relevant delivery priority.
• Comment - Type a free-text comment in the field as necessary.
8. Click OK to close the subscription form, or click another tab to continue defining the
subscription.
The Report Server Email (Data-Driven) option enables you to filter report contents according to the
recipient's owned objects.
Note: Data-driven subscriptions are not sent to group owners or domain custodians if the Do
not provide activity information to group owners or domain custodians option is selected on
the DatAdvantage Security page of the Management Console.
>
1. From the Delivered by drop-down list, select Report Server Email (Data-Driven).
2. Select the Always send this report, even if empty option as required.
3. Choose Recipients by rule.
4. From the AD Property dialog box, select the property by which the recipients are identified:
• Display Name
• SAM Account Name
• Email
5. In the Equals field, enter the actual recipients. Use a semicolon (;) to separate values.
• Priority - From the drop-down list, select the relevant delivery priority.
• Comment - Type a free-text comment in the field as necessary.
7. Click OK to close the subscription form, or click another tab to continue defining the
subscription.
The Report Server Email (Data-Driven) option enables you to filter report contents according to the
recipient's owned objects.
Note: Data-driven subscriptions are not sent to group owners or domain custodians if the Do
not provide activity information to group owners or domain custodians option is selected on
the DatAdvantage Security page of the Management Console.
1. From the Delivered by drop-down list, select Report Server Email (Data-Driven).
2. Select the Always send this report, even if empty option as required.
3. Choose All owners. Each owner will receive a portion of the report that corresponds to his
managed objects.
4. Set the required email settings:
• Subject - Type the subject line of the report.
• Display report data in the subject field - Select to display the template name and creation
date as a prefix to the subject. If the subject field is otherwise empty, the report data is
displayed as the subject.
• Include report - Select to include the actual report in the email.
• Format - From the drop-down list, select the format in which the report is to be delivered
(only if you chose to include the report with the email).
• Acrobat (PDF) file
• CSV (comma-delimited) file
• Excel (xls)
• Excel (xlsx)
• TIFF file
• Web archive
• XML
• Include link - Select to include a link to the report's location on the IDU server.
• Priority - From the drop-down list, select the relevant delivery priority.
• Comment - Type a free-text comment in the field as necessary.
5. Click OK to close the subscription form, or click another tab to continue defining the
subscription.
The Report Server File Share (Data-Driven) option enables you to send a report subscription to a
file system share according to the specified recipients' owned objects. With this option, a folder
is created in the destination folder for each recipient and a copy of the report that contains only
information relevant to that recipient is placed in the folder.
The folders are named according to the SAM account to ensure their uniqueness. They are
granted Read permissions for the relevant owner, and inherit permissions from the selected
destination folder. Each time the subscription is run, a new copy of the report is generated with a
name that includes the date on which it was generated.
The Report Server File Share option enables you to send a report subscription to a file system
share.
1. From the Delivered by drop-down list, select Report Server File Share.
2. Select the Always send this report, even if empty option as required.
3. Set the following parameters:
• File Name - Type the name of the file containing the report.
• Add a file extension when the file is created - Select this option to determine the type of
file in which the report is saved.
• Path - Click the Browse button to select the path on which the report resides.
• If the ShouldAlwaysLimitReportServerExportOutputRows configuration key is set to 1 -
For all subscriptions, two files are created:
• One small file in the specified render format, containing a 10-row random sampling
of the report results. It is named as specified in the subscription.
• A CSV file is created, containing the entire report output. The full file has a suffix of
_full.
• If the ShouldAlwaysLimitReportServerExportOutputRows configuration key is set to 0
• If the report results exceed the maximum number of rows (configured in the
Management Console):
• A small file is created in the specified render format, containing a 10-row random
sampling of the report results. It is named as specified in the subscription.
• A CSV file is created, containing the entire report output. The full file has a suffix
of _full.
• If the report results do not exceed the maximum number of rows, only a single file
is created and saved to the share path, containing the complete report results. This
file is in the specified render format.
• Render Format - From the drop-down list, select the format in which the report is to be
delivered. Options are:
• Credentials used to access the file share - Enter the user name and password required to
access the file share on which the report resides.
• Overwrite options - Select the relevant option:
• Overwrite an existing file with a newer version
• Do not overwrite the file if a previous version exists
• Increment file names as newer versions are added (according to the default SQL
reporting naming conventions)
4. Click OK to close the subscription form, or click another tab to continue defining the
subscription.
The Report Server File Share (Data-Driven) option enables you to filter report contents according
to the recipient's owned objects.
For several reports, you can define subscriptions that include the data of both data owners
and their subordinates. This hierarchical subscription means managers can view information
regarding all the data for which they are ultimately responsible, without the need to be data
owners themselves.
Note: Data-driven subscriptions are not sent to group owners or domain custodians if the Do
not provide activity information to group owners or domain custodians option is selected on
the DatAdvantage Security page of the Management Console.
1. From the Delivered by drop-down list, select Report Server File Share (Data-Driven).
2. Select the Always send this report, even if empty option as required.
3. Choose Selected recipients.
The Recipients box is displayed, providing the following information:
• Owner Name - The name of the data or group owner that is selected to receive the report.
• Ownership Types - The types of entities for which the owner is responsible.
• Include Subordinates Data - Select to include the data owned by all the owner's
subordinates in the report. (This option is only visible in reports supporting hierarchical
subscriptions.)
4. Next to the Recipients box, click Add.
Note: Data-driven subscriptions are not sent to group owners or domain custodians if the Do
not provide activity information to group owners or domain custodians option is selected on
the DatAdvantage Security page of the Management Console.
1. From the Delivered by drop-down list, select Report Server File Share (Data-Driven).
2. Select the Always send this report, even if empty option as required.
3. Choose Recipients by rule.
4. Set the following parameters:
• AD Property - From the drop-down list, select the property by which the recipients are
identified:
• Display Name
• SAM Account Name
• Email
• Equals - Enter the actual recipients in this field.. Use a semicolon (;) to separate values.
• File Name - Type the name of the file containing the report.
• Add a file extension when the file is created - Select this option to determine the type of
file in which the report is saved.
• Add timestamp (date and time) to the file name - Select this option to add the date and
time at which the report was generated to the file name.
• Path - Click the Browse button to select the path on which the report resides. Within this
path, a folder is created for each specified recipient. A copy of the report that contains
only information relevant to that recipient is placed in the folder.
• If the ShouldAlwaysLimitReportServerExportOutputRows configuration key is set to 1 -
For all subscriptions, two files are created:
• One small file in the specified render format, containing a 10-row random sampling
of the report results. It is named as specified in the subscription.
• A CSV file is created, containing the entire report output. The full file has a suffix of
_full.
• If the ShouldAlwaysLimitReportServerExportOutputRows configuration key is set to 0
• If the report results exceed the maximum number of rows (configured in the
Management Console):
• A small file is created in the specified render format, containing a 10-row random
sampling of the report results. It is named as specified in the subscription.
• A CSV file is created, containing the entire report output. The full file has a suffix
of _full.
• If the report results do not exceed the maximum number of rows, only a single file
is created and saved to the share path, containing the complete report results. This
file is in the specified render format.
• Render Format - From the drop-down list, select the format in which the report is to be
delivered. Options are:
• Credentials used to access the file share - Enter the user name and password required to
access the file share on which the report resides.
5. Click OK to close the subscription form, or click another tab to continue defining the
subscription.
Selecting All owners automatically sends subscriptions to all the owners defined in DatAdvantage.
Owners receive only the relevant sections of the report, based on their managed objects.
Note: Data-driven subscriptions are not sent to group owners or domain custodians if the Do
not provide activity information to group owners or domain custodians option is selected on
the DatAdvantage Security page of the Management Console.
1. From the Delivered by drop-down list, select Report Server File Share (Data-Driven).
2. Select the Always send this report, even if empty option as required.
3. Choose All owners.
4. Set the following parameters:
• File Name - Type the name of the file containing the report.
• Add a file extension when the file is created - Select this option to determine the type of
file in which the report is saved.
• Add timestamp (date and time) to the file name - Select this option to add the date and
time at which the report was generated to the file name.
• Path - Click the Browse button to select the path on which the report resides. Within this
path, a folder is created for each specified recipient. A copy of the report that contains
only information relevant to that recipient is placed in the folder.
• If the ShouldAlwaysLimitReportServerExportOutputRows configuration key is set to 1 -
For all subscriptions, two files are created:
• One small file in the specified render format, containing a 10-row random sampling
of the report results. It is named as specified in the subscription.
• A CSV file is created, containing the entire report output. The full file has a suffix of
_full.
• If the ShouldAlwaysLimitReportServerExportOutputRows configuration key is set to 0
• If the report results exceed the maximum number of rows (configured in the
Management Console):
• A small file is created in the specified render format, containing a 10-row random
sampling of the report results. It is named as specified in the subscription.
• A CSV file is created, containing the entire report output. The full file has a suffix
of _full.
• If the report results do not exceed the maximum number of rows, only a single file
is created and saved to the share path, containing the complete report results. This
file is in the specified render format.
• Render Format - From the drop-down list, select the format in which the report is to be
delivered. Options are:
• Credentials used to access the file share - Enter the user name and password required to
access the file share on which the report resides.
5. Click OK to close the subscription form, or click another tab to continue defining the
subscription.
Sending Data-Driven Reports to File Shares for Owners with Limited Visibility
Due to security constraints, some owners may not be allowed to view the entire file system.
Owners with such limited visibility can only create file system subscriptions for their personal use.
They can also send data-driven subscriptions by email to other owners.
Note: Data-driven subscriptions are not sent to group owners or domain custodians if the Do
not provide activity information to group owners or domain custodians option is selected on
the DatAdvantage Security page of the Management Console.
1. From the Delivered by drop-down list, select Report Server File Share (Data-Driven).
2. Select the Always send this report, even if empty option as required.
3. Set the following parameters:
• File Name - Type the name of the file containing the report.
• Add a file extension when the file is created - Select this option to determine the type of
file in which the report is saved.
• Add timestamp (date and time) to the file name - Select this option to add the date and
time at which the report was generated to the file name.
• Path - Click the Browse button to select the path on which the report resides. Within this
path, a folder is created for each specified recipient. A copy of the report that contains
only information relevant to that recipient is placed in the folder.
• If the ShouldAlwaysLimitReportServerExportOutputRows configuration key is set to 1 -
For all subscriptions, two files are created:
• One small file in the specified render format, containing a 10-row random sampling
of the report results. It is named as specified in the subscription.
• A CSV file is created, containing the entire report output. The full file has a suffix of
_full.
• If the ShouldAlwaysLimitReportServerExportOutputRows configuration key is set to 0
• If the report results exceed the maximum number of rows (configured in the
Management Console):
• A small file is created in the specified render format, containing a 10-row random
sampling of the report results. It is named as specified in the subscription.
• A CSV file is created, containing the entire report output. The full file has a suffix
of _full.
• If the report results do not exceed the maximum number of rows, only a single file
is created and saved to the share path, containing the complete report results. This
file is in the specified render format.
• Render Format - From the drop-down list, select the format in which the report is to be
delivered. Options are:
• Credentials used to access the file share - Enter the user name and password required to
access the file share on which the report resides.
4. Click OK to close the subscription form, or click another tab to continue defining the
subscription.
Scheduler Tab
1. In the Reports view, select the My Subscriptions pane. Your subscriptions are displayed in
table form, one row per subscription (if you are an enterprise manager, the table displays all
the subscriptions that have been defined in the system).