Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
Arctera Insight Information Governance Administrator's Guide
- Section I. Getting started
- Introduction to Arctera Insight Information Governance administration
- Configuring Information Governance global settings
- About Information Governance licensing
- SQLite WAL mode
- Configuring SMTP server settings
- About scanning and event monitoring
- Monitoring Indexer Node Storage Utilization
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Information Governance integration with Data Loss Prevention (DLP)
- Importing sensitive files information through CSV
- Configuring advanced analytics
- About open shares
- About user risk score
- Configuring file groups
- Configuring Workspace data owner policy
- Configuring Management Console settings
- About bulk assignment of custodians
- Configuring Watchlist settings
- Configuring Metadata Framework
- Proof of concept
- Section II. Configuring Information Governance
- Configuring Information Governance product users
- Configuring Information Governance product servers
- About Information Governance product servers
- Adding a new Information Governance server
- Managing Information Governance product servers
- Viewing Information Governance server details
- About node templates
- Adding Portal role to a Information Governance server
- Adding Classification Server role to a Information Governance server
- Assigning Classification Server to a Collector
- Associating a Classification Server pool to a Collector
- Viewing in-progress scans
- Configuring Information Governance services
- Configuring advanced settings
- Monitoring Information Governance jobs
- Rotating the encryption keys
- Viewing Information Governance server statistics
- About automated alerts for patches and upgrades
- Deploying upgrades and patches remotely
- Using the Upload Manager utility
- About migrating storage devices across Indexers
- Viewing the status of a remote installation
- Configuring saved credentials
- Configuring directory service domains
- About directory domain scans
- Adding a directory service domain to Information Governance
- Managing directory service domains
- Fetching users and groups data from NIS+ scanner
- Configuring attributes for advanced analytics
- Deleting directory service domains
- Scheduling scans
- Configuring business unit mappings
- Importing additional attributes for users and user groups
- Configuring containers
- Server Pools
- Section III. Configuring native file systems in Information Governance
- Configuring clustered NetApp file server monitoring
- About configuring a clustered NetApp file server
- About configuring FPolicy in Cluster-Mode
- Pre-requisites for configuring clustered NetApp file servers
- Credentials required for configuring a clustered NetApp file server
- Preparing a non-administrator local user on the clustered NetApp filer
- Preparing a non-administrator domain user on a NetApp cluster for Information Governance
- Persistent Store
- Preparing Information Governance for FPolicy in NetApp Cluster-Mode
- Preparing the ONTAP cluster for FPolicy
- About configuring secure communication between Information Governance and cluster-mode NetApp devices
- Enabling export of NFS shares on a NetApp Cluster-Mode file server
- Enabling SSL support for Cluster Mode NetApp auditing
- Configuring EMC Celerra or VNX monitoring
- Configuring EMC Isilon monitoring
- About configuring EMC Isilon filers
- Prerequisites for configuration of Isilon or Unity VSA file server monitoring
- Credentials required for configuring an EMC Isilon cluster
- Configuring audit settings on EMC Isilon cluster using OneFS GUI console
- Configuring audit settings on EMC Isilon cluster using the OneFS CLI
- Configuring Isilon audit settings for performance improvement
- Preparing Arctera Insight Information Governance to receive event notifications from an EMC Isilon or Unity VSA cluster
- Creating a non-administrator user for an EMC Isilon cluster
- Utilizing access zone's SmartConnect Zone/Alias mappings
- Purging the audit logs in an Isilon filer
- Configuring EMC Unity VSA file servers
- Configuring Hitachi NAS file server monitoring
- Configuring Windows File Server monitoring
- Configuring Arctera File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- About configuring filers
- Viewing configured filers
- Adding filers
- Add/Edit NetApp cluster file server options
- Add/Edit EMC Celerra filer options
- Add/Edit EMC Isilon file server options
- Add/Edit EMC Unity VSA file server options
- Add/Edit Windows File Server options
- Add/Edit Arctera File System server options
- Add/Edit a generic storage device options
- Add/Edit Hitachi NAS file server options
- Custom schedule options
- Editing filer configuration
- Deleting filers
- Viewing performance statistics for file servers
- About disabled shares
- Adding shares
- Managing shares
- Editing share configuration
- Deleting shares
- About configuring a DFS target
- Adding a configuration attribute for devices
- Configuring a DFS target
- About the DFS utility
- Running the DFS utility
- Importing DFS mapping
- Renaming storage devices
- Configuring clustered NetApp file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About SharePoint server monitoring
- Credentials required for configuring SharePoint servers
- Configuring a web application policy
- About the Information Governance web service for SharePoint
- Viewing configured SharePoint data sources
- Adding web applications
- Editing web applications
- Deleting web applications
- Adding site collections
- Managing site collections
- Removing a configured web application
- Configuring monitoring of SharePoint Online accounts
- About SharePoint Online account monitoring
- Configuring user with minimum privileges in Microsoft 365
- Creating an application in the Microsoft Azure portal
- Configuring application without user impersonation for Microsoft 365
- Adding SharePoint Online accounts
- Managing a SharePoint Online account
- Adding site collections to SharePoint Online accounts
- Managing site collections
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Configuring monitoring of Box accounts
- Configuring OneDrive account monitoring
- Configuring Azure Netapp Files Device
- Managing cloud sources
- Section VI. Configuring Object Storage Sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Configuring policies
- About Information Governance policies
- Managing policies
- Create Data Activity Trigger policy options
- Create User Activity Deviation policy options
- Create Real-time Data Activity Policy options
- Create Real-time Permitted User-based Activity Policy options
- Create Real-time Restricted User-based Activity Policy options
- Create Real-time Sensitive Data Activity policy options
- Managing alerts
- Configuring policies
- Section IX. Remediation
- Configuring remediation settings
- Section X. Reference
- Appendix A. Information Governance best practices
- Appendix B. Migrating Information Governance components
- Appendix C. Backing up and restoring data
- Appendix D. Arctera Information Governance health checks
- About Information Governance health checks
- Services checks
- Deployment details checks
- Generic checks
- Information Governance Management Server checks
- Information Governance Indexer checks
- Information Governance Collector checks
- Information Governance Windows File Server checks
- Information Governance SharePoint checks
- Classification server health checks
- Information Governance self service portal server health checks
- About Information Governance health checks
- Appendix E. Command File Reference
- Appendix F. Arctera Information Governance jobs
- Appendix G. Troubleshooting
- About general troubleshooting procedures
- About the Health Audit report
- Location of Information Governance logs
- Downloading Information Governance logs
- Migrating the data directory to a new location
- Troubleshooting FPolicy issues on NetApp devices
- Troubleshooting EMC Celera or VNX configuration issues
- Troubleshooting EMC Isilon configuration issues
- Troubleshooting SharePoint configuration issues
- Troubleshooting Hitachi NAS configuration issues
- Troubleshooting installation of Tesseract software
- Troubleshooting RHEL 9 upgrade issue
- Troubleshooting CyberArk Password Manager Configuration Issues
Registering Information Governance with Microsoft to scan Azure AD
To authorize Information Governance to scan Azure AD, you must create an application for every Information Governance installation and register it with Microsoft Azure Active Directory. This step involves associating a set of credentials with the application and providing the application with the required permissions, which enables communication between Information Governance and Microsoft. This step also creates an authorization token that is stored as a named credential in the Information Governance configuration.
A M365 user with the Microsoft Minimum privilege user role or with a role which has lesser admin privileges than the Minimum privilege user can create and register an application with Microsoft. However, the user must be granted the following four roles at the minimum:
Application Administrator : To create a Microsoft application
User Administrator: To get the access to OneDrive account of all the users in tenant
SharePoint Administrator: To fetch all users and groups present across Azure AD.
Privileged Role Administrator: To give admin consent to Azure Application
A custom role (View-Only Audit Logs) in the Exchange Admin Center
To assign the first three roles, refer to the Azure documentation.
To create and assign the View-Only Audit Logs role to a non-Global admin user
- Login to Microsoft Admin Portal with the Minimum privilege user role, navigate to Exchange Admin Center and click Classic Exchange Admin Center in the left pane.
- Click Permissions > Admin roles and click the + icon to create a new role.
The Role Group pop-up opens.
- In the Role Group pop-up, enter a desired role name (ex. AuditReadRole).
- In the Roles section, click + and select the role "View-Only Audit Logs" and click OK.
- In the Members section, click + and select the member that you want to assign the minimum privilege role.
- After selecting the member, click OK and then click Save.
To create and register an application with Microsoft
- Login as a global admin user or minimum privilege user to https://portal.azure.com/#home and search App Registrations.
- On the Register an application page, enter a desired name for the app.
- In Supported account types select Accounts in this organizational directory only (<organization-name> only - Single tenant)
- On the Register an application page, click Register to register the app. (Redirect URI can be provided later.)
Your new application is created and the app Overview page is displayed.
- Copy-save the Application (Client ID) and Directory (Tenant) ID. You will be required to provide it later while adding an account in Information Governance.
- Copy-save the . You will be required to provide it later while adding an account in Information Governance.
- On the left sidebar of your app dashboard, click Certificates and Secrets.
- In the Client secrets section, click New client secrets to generate the access token required for calling the required APIs
- Set the expiry to Never and click Add.
- Copy the Client Secret Value is generated. You will be required to provide it later while adding an account in Information Governance.
- Then you need to grant permissions to the app to use the Microsoft Graph and M365 APIs.
On the left sidebar of your app, click API permissions, and then click Add a permission.
- On the Request API permissions panel that opens, select Microsoft Graph and M365 respectively, click Application permissions and grant the permissions as per the table given below:
API
Permission name
Microsoft Graph
Files.Read.All
Group.Read.All
RoleManagement.Read.Directory
Sites.Read.All
User.Read.All
M365 Management APIs
ActivityFeed.Read
ActivityFeed.ReadDlp
SharePoint
Sites.FullControl.All
Note:
As per Microsoft guidelines, while using minimum permissions application, few advanced permissions like limited access permissions given to Limited Access System Group for the folder, permissions of sites, Site collections, Document Library will not be visible. To fetch those permission, add Sites.FullControl.All scope to MS Application
- Then click Grant admin consent for.., and confirm.
- Now add the redirect URI.
Go to the Overview page of the app and click Add redirect URI. The Authentication page opens
- Click Add a platform
- On the Configure platforms panel that opens, click Web
- Provide the Information Governance Management Server IP address, as a redirect URI in the following format: https://datainsight.us3.archive.veritas.com/api/DirectoryServices/azureADRedirect
For more details, refer https://docs.microsoft.com/en-us/azure/active-directory/develop/reply-url.
You can authenticate using FQDN in the redirect URL by setting node Level property.
To set the node Level property,
Navigate to Settings > Servers and click the configured Management Server and then click Advance Settings tab.
In the Advance Settings tab, clickSet custom properties
In the Property Name box, add node.azure.ad.auth.via.fqdn
In the Property Value box, add true
Click Save and Close.
Note:
Property value should be set to true for authenticating via FQDN and false for authenticating via IP.
If you want to modified any existing property value,
change the redirect URI in the Azure App accordingly.
Delete the cookie from <DATA_DIR>\connectors\sponline\cookie\dataStore on the collector node.
Re-authorize the application.
- Click Configure to save it.
- On the same page, set theSupported account types to Accounts in any organizational directory (Any Azure AD directory - Multitenant).
Once the app is created, anybody in the organization can access the app. As per Microsoft recommendation, restrict the access to specific users.
For information on how to require the user assignment for an app via the Azure portal, refer to Configure an application to require user assignment Azure documentation
For information on how to assign users or groups to an app via the Azure portal, refer to Assign users to an app Azure documentation