2. Service Deployment and Configuration | Sensitive Data Cleanup and Monitoring

2.1 Activity Summary

Activity Description	This stage outlines the work that is required to progress your project plan by deploying on premise connectors, configuring them, and validating their operation.
Goals	1. On Premise collectors are operational. 2. Discovery process has been validated.
Participants	Project Manager, IT Team, Application Administrator
Pre-requisites	Project plan defined. Repository inventory prepared. Deployment architecture defined.
Outputs	Data discovery process validated. Initial users have access.

Activities

2.2 Provision Collector Hosts, Collector Groups, and Install Collectors

If the project involves discovering on-premises file share content, then the deployment plan will incorporate an appropriate number of on-premises Collectors.

The on-premises Collectors may be deployed to existing application servers, or you may prefer to deploy new hosts. If using an existing server, you should consider whether the load from operation of a Collector process may impact any other applications hosted on the server:

Feature extraction from object content can result in significant CPU and memory usage.
While retrieving content for Feature Extraction may impact the available network and disk bandwidth.

Feature Extraction from object content can lead to heavy CPU and memory usage while retrieval of content for Feature Extraction may impact on available I/O bandwidth.

The basic steps for downloading and installing a Collector, and the considerations for the specification and security of the host application server are outlined in the Collector Installation Guide at the link below:

https://support.activenav.com/collector-installation-guide

Before installation you should configure the Collector Groups for your physical locations according to the deployment plan. Once the Collector Groups are created, they will be assigned a unique Collector Install ID. When installing a Collector you should ensure that you use the Collector Install ID for the Collector Group that you want the Collector to be associated with.

2.3 Add Users

When your tenant is provisioned, a single administrator user will be added. You should now add additional users from your project team to allow them to assist in this deployment and configuration phase. Further users can be added at any time.

The addition of users, and the access that is associated with each available user role is outlined at the link below:

Managing Users (📺)

2.4 Deploy Credentials

Before a Data Source can be created to validate the operation of Collectors the credentials that will be used to gain access must be configured within the system. You will have prepared the required credentials during the Preparation phase, if you did not record details of the credentials in ActiveNav Cloud at the time, you should do so now.

The links below outline the steps to add credentials to the ActiveNav Cloud platform for different repository types.

Adding Basic Credentials

Adding Azure Credentials

Creating the GWD Credentials

2.5 Validate Operation

At this stage we recommend that the overall operation of the system is tested by performing Discovery and Feature Extraction on a small test location. This will allow you to confirm connectivity of your Collectors to both the back end ActiveNav Cloud platform and the validity of the credentials you have prepared.

In the interest of being able to quickly confirm the end-to-end operation of the system, it is recommended that a dedicated test location is set up with a small number of files. The files should be primed with some fake sensitive data (e.g. bank account / credit card / social security numbers) to allow the scoring of data to be demonstrated.

Data Source Creation

Follow the steps in this KBA to define your test data source:
https://support.activenav.com/how-to-create-a-data-source

You should ensure:

That you use a path with just a small amount of test data
That you choose “Discovery with Feature Extraction”
That you select the appropriate Collector Group for your data path

After you have saved your test Data Source configuration, you can observe it being scheduled for operation on the Data Sources overview page in the ActiveNav Cloud UI. A small amount of test data should take only a few minutes to process.

Confirm in the details for the data source that the expected quantity of data was discovered.

Data Visualization

To review the results from your Data Source discovery you should open the ActiveNav Cloud UI as a user who has the Analyst role. This will allow you to open the Analyst Home page where your newly discovered data will be assigned to the “No Business Unit” category.

The Analyst Home Page shows you how findings will be visualized and how you can explore the details of the findings for specific containers / objects.

Analyst Home Page

Other Repositories / Collectors

If you have on-premises Collectors installed in different physical locations, you may choose to run a test for each location – this will allow you to identify any variation in network connectivity that may impact on operation.

Cloud Collectors are not affected by network configuration as they are hosted within the ActiveNav Cloud platform, but validating credentials for cloud-based repositories is a sensible step.

2.6 Introduce Users

This is a good time to introduce Data Analysts to the application by providing them with a basic introduction to the platform and walking them through the application using the discovered test data as a case study.

Next Step

First Discovery represents the first full scale discovery of the project, or the first discovery for a specific repository type.