From 088e1d19ed9ee533cb77c508b8c5a558739e693f Mon Sep 17 00:00:00 2001 From: Ben Hayman Date: Fri, 27 Feb 2026 11:58:27 +0000 Subject: [PATCH 01/20] Assorted tweaks and improvements to existing docs --- .../introduction/addsource/addbox.md | 2 +- .../introduction/addsource/adddropbox.md | 10 +- .../addsingledatabase/addsingledatabase.md | 16 +- .../introduction/addsource/addsource.md | 8 +- .../addsqlserversource/addsqlserversource.md | 18 ++- .../addsqlserversource/mysqlserver.md | 20 +++ .../addsqlserversource/postgresqlserver.md | 21 +++ .../introduction/manage/managefilesystem.md | 21 ++- .../taxonomies/builtintaxonomies.md | 4 +- docs/dataclassification/5.7/dashboards.md | 13 +- docs/dataclassification/5.7/index.md | 48 +++--- .../deployment/clouddeployment.md | 15 +- .../deployment/ndcserverandclient/dqsmode.md | 137 ++++++++++++------ .../ndcserverandclient/ndcserverandclient.md | 24 +-- .../initialconfiguration/healthalert.md | 7 +- .../initialconfiguration/modes.md | 10 +- .../initialconfiguration/overview.md | 2 +- .../processingsettings.md | 8 +- .../initialconfiguration/security.md | 14 +- .../introduction/install/ndcsqldatabase.md | 33 +++-- .../5.7/introduction/install/overview.md | 44 +++--- .../5.7/introduction/introduction.md | 2 +- .../requirements/hardwarerequirements.md | 25 ++-- .../requirements/supportedcontenttypes.md | 2 +- .../5.7/introduction/upgrade.md | 26 +++- .../indexmaintenance/indexmaintenance.md | 6 +- .../configuration/communicationsettings.md | 6 +- .../coreconfiguration/administration.md | 7 +- .../classifier/classifier.md | 5 +- .../classifier/conceptclassifier.md | 2 +- .../classifier/generaloptions.md | 9 +- .../classifier/monitoredcontent.md | 3 +- .../coreconfiguration/collector.md | 3 +- .../coreconfiguration/coreconfiguration.md | 2 +- .../coreconfiguration/indexer.md | 3 +- .../configuration/coreconfiguration/system.md | 13 +- .../configuration/texthandling.md | 1 + .../users/passwordmanager.md | 4 +- .../users/securendc.md | 8 +- .../users/usermanagement.md | 19 +-- 40 files changed, 365 insertions(+), 256 deletions(-) create mode 100644 docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md create mode 100644 docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addbox.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addbox.md index 03592e67d2..c47ff41caa 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addbox.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addbox.md @@ -25,7 +25,7 @@ Configure the following: | Setting | Description | | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Basic settings** | | -| JSON Import | Drag and drop the JSON file with Box app configuration settings that you downloaded at [Step 1. Create the App](/docs/dataclassification/5.7/introduction/introduction/box.md#step-1-create-the-app) (see #12). The program then parses this file so that many settings are filled in automatically. | +| JSON Import | Drag and drop the JSON file with Box app configuration settings that you downloaded at [Step 1. Create the App](/docs/dataclassification/5.7/introduction/introduction/box.md#step-1-create-the-app) (see #12). The program then parses this file and fills in the relevant settings automatically. | | Enterprise ID | Specifies the internal unique identifier for your Box account (filled in automatically). | | API Key | _Client ID_ of the Box app created at [Step 1. Create the App](/docs/dataclassification/5.7/introduction/introduction/box.md#step-1-create-the-app)(Filled in automatically.) | | Client Secret | Will be generated when allowing access to the Netwrix Data Classification app. Is also known as the “App Key”. | diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md index ff719ef6a7..8a2a9496c5 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md @@ -9,7 +9,7 @@ sidebar_position: 20 The Dropbox source configuration screen allows you to enable the crawling and classification of content stored in Dropbox cloud storage. -**IMPORTANT!** Make sure you created App for Dropbox crawling before start adding the source. +**IMPORTANT!** Make sure you created a suitable App for Dropbox crawling before adding the source. [See Configure Dropbox for Crawling for more information.](/docs/dataclassification/5.7/introduction/introduction/dropbox.md) ![source_dropbox_thumb_0_0](/images/dataclassification/5.7/admin/sources/dropbox/source_dropbox_thumb_0_0.webp) @@ -18,10 +18,10 @@ Complete the following fields: | Option | Description | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| App key | The value, which is generated automatically as you create your Dropbox app. | -| App secret | The value, which is generated automatically as you create your Dropbox app. Click Show in the Dropbox app to view the value. | +| App key | Generated automatically as you create your Dropbox app. | +| App secret | Generated automatically as you create your Dropbox app. Click Show in the Dropbox app to view the value. | | Authorization code | Select Generate and copy the code from your app. | | Access Shared Team Folder as | If you have team folders in your Dropbox namespace and you want to crawl one or more of these folders with Netwrix Data Classification, provide the email address of an account that has access to the desired team folders. For personal folders, this option is not required. For more information, refer to Dropbox [Namespace guide](https://www.dropbox.com/developers/reference/namespace-guide). | -| OCR Processing mode | Select documents' images processing mode: | -| Source Group | Netwrix recommends creating a dedicated source group for Dropbox. | +| OCR Processing mode | Select document images processing mode: | +| Source Group | Netwrix recommends creating a dedicated source group for Dropbox. If none exists, a source group named Dropbox Sources will be created automatically. | | Pause source on creation | Select if you want to make other configuration changes before collection of the source occurs. | diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md index bb5611e0e6..532d179b1c 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md @@ -6,8 +6,8 @@ sidebar_position: 120 # Add Single Database -The Database source configuration screen allows you to enable the crawling and classification of -content stored in your Microsoft SQL Server, MySQL, and Oracle databases. +The Database source configuration screen allows you to configure the crawling and classification of +content stored in your Microsoft SQL Server, MySQL, PostgreSQL, and Oracle databases. Content must either be configured / crawled using the configured service accounts (IIS Application Pool User, Windows Services) or by using specific connection details. @@ -28,13 +28,13 @@ Complete the following fields: | Option | Description | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Connection Type | Select your connection type: MS SQL, MySQL, or Oracle. | +| Connection Type | Select your connection type: MS SQL, MySQL, PostgreSQL, or Oracle. | | Server | Specify the server name of the database system to be crawled ("." can be used to indicate the local server). | -| Database Name | Specify the database that will be crawled. It is possible to configure multiple databases from the same server. | -| Authentication Method | Select authentication method: **Integrated** or **SQL**. | -| OCR Processing Mode | Select processing mode for images in the documents: | -| Source Group | If you want to add database to a source group, select existing, or create a new one. | -| Pause source on creation | Select to make other configuration changes before the initial data collection starts. | +| Database Name | Specify the name of the database that will be crawled. It is possible to configure multiple databases from the same server. | +| Authentication Method | Select authentication method: **Integrated** or **SQL**. | +| OCR Processing Mode | Select processing mode for images in the documents: | +| Source Group | If you want to add the database source to a source group, select an existing source group or create a new one. | +| Pause source on creation | Pauses the source upon creation, to allow for further configuration before collection begins. | After the source configuration is completed, you will be prompted to lauch SQL crawling diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsource.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsource.md index 38c486bbf4..b8543b1db6 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsource.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsource.md @@ -20,7 +20,8 @@ Follow the steps to add a content source. the sources: - [Box](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addbox.md) -- [Add Single Database](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md) (Microsoft SQL Server or Oracle database) +- [Add Single Database](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md) (Microsoft SQL Server, MySQL, PostgreSQL or Oracle database) +- [Add Database Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md) (Microsoft SQL Server, MySQL, PostgreSQL or Oracle databases on a server) - [Dropbox](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md) - [Exchange Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangeserver.md) or [Exchange Mailbox](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailbox.md) @@ -34,8 +35,7 @@ All your content sources will be listed in the **Sources** section. :::note When adding a source or managing source configuration, the most commonly used source settings are displayed by default. However, some source types have additional configuration options -that can be displayed by clicking the Advanced Settings ("wrench" icon). You can allow these -advanced settings to be always shown to authorized users. +that can be displayed by clicking the Advanced Settings ("wrench" icon) in the bottom left. You can +set the Advanced Settings to display by default in User Preferences. [Users and Security Settings](/docs/dataclassification/5.7/systemconfigurationoverview/users/users.md) - ::: diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md index 4473e32554..5b90dbadb3 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md @@ -7,8 +7,8 @@ sidebar_position: 110 # SQL Server The SQL Server source configuration screen allows you to enable the crawling and classification of -content stored in your MS SQL and Oracle servers. In comparison to the **SQL database**, you can -crawl the whole server. +content stored in your MS SQL, MySQL, PostgreSQL, and Oracle servers. Where the **SQL database** source crawls a single database, +the **SQL Server** source crawls all databases found on a given server. Once connected it is possible to create an intelligent content mapping, crawling certain fields as unstructured index text, and other fields as mapped metadata. @@ -20,8 +20,18 @@ To crawl SQL server: 3. Specify [MS SQL Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mssqlserver.md) or [Oracle Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/oracleserver.md). ![sqlserver_source](/images/dataclassification/5.7/admin/sources/sqlserver/sqlserver_source.webp) - -4. Select Save. +4. Complete the following fields: + +| Option | Description | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Connection Type | Select your connection type: MS SQL, MySQL, PostgreSQL, or Oracle. | +| Server | Specify the server name of the database system to be crawled ("." can be used to indicate the local server). | +| Database Name | Specify the name of the database that will be crawled. It is possible to configure multiple databases from the same server. | +| Authentication Method | Select authentication method: **Integrated** or **SQL**. | +| OCR Processing Mode | Select processing mode for images in the documents: | +| Source Group | If you want to add the database source to a source group, select an existing source group or create a new one. | +| Pause source on creation | Pauses the source upon creation, to allow for further configuration before collection begins. | +5. Select Save. You can then review summary, text, metadata, classifications, and properties of your crawling by selecting information icon against your server. You can also build the report for more details. diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md new file mode 100644 index 0000000000..52956c6d1d --- /dev/null +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md @@ -0,0 +1,20 @@ +--- +title: "Add MySQL Server Source" +description: "Add MySQL Server" +sidebar_position: 30 +--- + +# Add MySQL Server + +Once you choose to add SQL server source, you opt to add MySQL server as a source. For more +information, go to the main article[SQL Server ](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md). + +To connect to a MySQL server: + +1. On the **Source Configuration** screen, select **MS SQL**. +2. Specify MySQL server. + + ![sqlserver_source3](/images/dataclassification/5.7/admin/sources/sqlserver/sqlserver_source3.webp) + + +3. Select Save. diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md new file mode 100644 index 0000000000..f1d3d1f64b --- /dev/null +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md @@ -0,0 +1,21 @@ +--- +title: "Add PostgreSQL Server Source" +description: "Add PostgreSQL Server" +sidebar_position: 40 +--- + +# Add PostgreSQL Server + +Once you choose to add SQL server source, you opt to add PostgreSQL server as a source. For more +information, go to the main article[SQL Server ](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md). + +To connect to a PostgreSQL server: + +1. On the **Source Configuration** screen, select **SQL Server**. +2. Specify PostgreSQL server. + + ![sqlserver_source3](/images/dataclassification/5.7/admin/sources/sqlserver/sqlserver_source3.webp) + +3. Insert the Master Database name. + +4. Select Save. diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/manage/managefilesystem.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/manage/managefilesystem.md index 6b4d3efbf0..124bc4bfa5 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/manage/managefilesystem.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/manage/managefilesystem.md @@ -60,12 +60,12 @@ classifications attributes to the classified documents: **To configure tagging on a source level** -1. Go to **Sources** → **General**, highlight the source you need and click the "pencil" symbol on - the right. -2. The list of global taxonomy configurations will be displayed. To apply these global settings, - select **Use Global Configuration** checkbox on top. To configure source-specific settings, clear - this checkbox. -3. Select the taxonomy you need and click **Edit**. +1. Go to the **Sources** view, select the source you wish to enable classifications for and click the "pencil" symbol on + the right side of the table. +2. The list of global taxonomy configurations will be displayed. To apply these settings globally, + select the **Use Global Configuration** checkbox at the top of the page. To configure settings for the selected source specifically, make sure + this checkbox is unchecked. +3. Select the taxonomy you wish to write back and click **Edit**. 4. In the taxonomy properties, select the **Enabled** checkbox and specify the settings described in the table above. @@ -86,8 +86,13 @@ To specify inclusions, do the following: 3. To modify an extension (for example, add a wildcard), click **Edit**. To add a new one, click **Add**. +Two wildcards are supported: +- \* - matches to one or more instances of any character +- . - explicitly includes files with no extension + + :::note -Inclusions are case-insensitive. A wildcard (\*) is supported. +Inclusions are case-insensitive. ::: @@ -102,7 +107,7 @@ You can also configure the list of file locations to exclude from processing. 2. In the **Details** window on the **Filter** tab specify the objects (files or folders) to exclude. - To exclude a certain file, enter its full path. For example: _C:\Test Folder\Test Document.docx_ + To exclude a specific file, enter its full path. For example: _C:\Test Folder\Test Document.docx_ Wildcards can be used anywhere in the exclusion pattern definition as follows: diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/builtintaxonomies.md b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/builtintaxonomies.md index cc224c5968..42f5330f79 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/builtintaxonomies.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/builtintaxonomies.md @@ -174,8 +174,8 @@ consumers and businesses. ## Sensitive and Non-Sensitive Taxonomies -While creating your own reports, you can specify whether a taxonomy is sensitive (finance, -сredentials) or non-sensitive (file size, language). +While creating your own reports, you can specify whether a taxonomy is sensitive (e.g. financial details, +сredentials) or non-sensitive (e.g. file size, language). :::note This applies only to customized taxonomies, which you add by yourself. You cannot change diff --git a/docs/dataclassification/5.7/dashboards.md b/docs/dataclassification/5.7/dashboards.md index ae74a18879..a14e56faac 100644 --- a/docs/dataclassification/5.7/dashboards.md +++ b/docs/dataclassification/5.7/dashboards.md @@ -12,20 +12,20 @@ The Dashboard administration area provides a selection of tools to review applic The default screen shows a high-level overview of Netwrix Data Classification statistics, displaying the last active times of each service (with inactive services shown in red). Select the "i" icon -next to each date to view the name of the active server as well as batch processing statistics. You -will also view the processing throughput. +next to each date to view the name of the active server as well as batch processing statistics. +If you have the Distributed Query Server functionality enabled, any instances that are missing their +encryption key will also be displayed. You will also be able to view the average processing throughput. The following statistics are available for each thread type: - Processing Time—The weighted average time for each thread (total batch time / number of documents processed) -- Real Execution Time—The actual execution time of each thread (average of each threads run time) +- Real Execution Time—The actual execution time of each thread (average of each threads' run time) Statistics shown on the Dashboard screen are cached and updated regularly by the Collector service. If the values are not being updated please ensure that the Collector service is running. -New content will be shown as awaiting collection, and progress through to fully processed once it -has been classified. +New content will be shown as Awaiting Collection, and progress through to Fully Processed. Content that has failed to process fully will be indicated under the "Exceptions" section, with the following meanings: @@ -34,8 +34,7 @@ following meanings: the source system) - Text Extraction Errors—Items that failed text extraction (either partially or fully)—this will typically mean that the full text for the affected documents will not be available -- Collection Exclusions—Items that have been excluded due to the specified configuration (such as - Sources → SharePoint → Exclusions) +- Collection Exclusions—Items that have been excluded due to a configured Collection Exclusion - Files Skipped—File share items that have been ignored due to the "Files Included" or "Files Excluded" configuration (Sources → File) - Deleted Automatically—Items that have been detected as removed from the source system diff --git a/docs/dataclassification/5.7/index.md b/docs/dataclassification/5.7/index.md index 7759bcf03c..38e4c27605 100644 --- a/docs/dataclassification/5.7/index.md +++ b/docs/dataclassification/5.7/index.md @@ -32,7 +32,7 @@ Major benefits: # How It Works Netwrix Data Classification identifies and classifies sensitive and business-critical content across -your organization. This way it mitigates the risk of data breaches. The program also meets +your organization, mitigating the risk of data breaches. The program also helps you meet compliance requirements with less effort and expense. You can view the app architecture and components in the figure below. @@ -44,16 +44,16 @@ You can view the app architecture and components in the figure below. ![addsource](/images/dataclassification/5.7/admin/addsource.webp) -2. The configured data sources are saved in the NDC SQL database (SQL Server Collector Database). -3. The NDC Collector service crawls data files in each data source, converts documents into plain - text and populates file metadata in the NDC SQL database. +2. The configured data sources are saved to the NDC SQL database. +3. The NDC Collector service crawls the data files in each data source, converting documents into plain + text and populating file metadata in the NDC SQL database. 4. The NDC Indexer service builds and maintains a full-text search index (NDC Index) based on the content and metadata of the collected files. 5. The NDC Classifier service performs data classification by matching collected files against - installed taxonomies (e.g., Netwrix compliance taxonomies). -6. If Data Tagging is enabled, the assigned classification labels are written to the custom metadata + pre-built taxonomies (the Netwrix compliance taxonomies) and/or customer-created taxonomies. +6. If Classification Writing is enabled, the assigned classification labels are written to the custom metadata columns for supported document types. -7. If Remediation Workflows are enabled, the configured workflows are run on documents that meet the +7. If any Workflows have been defined and are enabled, they are run on documents that meet the workflow conditions. ## QueryServer @@ -81,14 +81,13 @@ The NDC Collector is implemented as a Microsoft Windows Service. ## Indexer -The Indexer takes each new document collected by the conceptCollector and inserts the appropriate -information in the NDC Index Database. +The Indexer takes each new document collected by the conceptCollector and indexes terms from +the extracted text within the NDC Index. -This activity can proceed concurrently with retrieval activity. However, heavy-duty indexing -activity can significantly impair retrieval performance and so, if on-going indexing is very -significant, then the conceptIndexer should either be run during quiet periods (perhaps overnight) -or alternatively new information should be constructed off-line with a batch process updating the -live index periodically. +The index can be read from concurrently with the indexing process. However, significant indexing +activity can lead to a corresponding drop in index performance, in which case the Indexer should +either be run during quiet periods (e.g. overnight) or the indexing should be performed separately +with a batch process updating the live index periodically. If the Indexer is to update the live index as a background task then it is vital that this process runs on the same server where the NDC Index Database is located. @@ -121,24 +120,23 @@ Database such as: the document title, body text, etc. However, this information using a primary key and so is very efficient. The hitlist itself is always constructed and ranked using information contained in the proprietary conceptDatabase. -The current release of Netwrix Data Classification supports SQL Server 2008 R2 or later. +The current release of Netwrix Data Classification supports SQL Server 2008 R2 or later version. -## NDC Index Database +## NDC Index -The NDC Index Database contains the probabilistic index to all documents in the system. All files -use the extension “.cse” but will use the extension “.tmp” when merging changes into the index. +The NDC Index contains a probabilistic index for all documents that have been indexed by the system. The index files +use the extension “.cse”, but temporary files (extension “.tmp”) are used when merging changes into the index. -The NDC Index Database files should normally be located on the same server as the Netwrix Data -Classification server due to the fact that the query and indexing processes can be disk intensive. +The NDC Index Database files should be located on the same server as the Netwrix Data +Classification server due to the fact that the query and indexing processes can be highly disk-intensive. Note that “text.cse” is not supplied since it will be created automatically when the first documents are collected. ## Classifier -Classifier can be used to classify documents post index time. When this option is being used then an -application can map documents to any external classification system such as a corporate taxonomy or -user profiles. - -Classification can be used as a method browsing the document collection or to filter ad hoc queries. +The Classifier is used to classify documents after they have been indexed. It can make use of the built-in +taxonomies and any custom taxonomies created by the user, and can be linked to SharePoint termsets to classify +against them as well. It also runs user-configured workflows against any documents that meet the conditions +of the workflow, and is used to perform Data Subject Access Requests. The Classifier is implemented as a Microsoft Windows Service. diff --git a/docs/dataclassification/5.7/introduction/deployment/clouddeployment.md b/docs/dataclassification/5.7/introduction/deployment/clouddeployment.md index 639cdd9c6c..322ec2b90e 100644 --- a/docs/dataclassification/5.7/introduction/deployment/clouddeployment.md +++ b/docs/dataclassification/5.7/introduction/deployment/clouddeployment.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Data Storages and Sizing -Netwrix Data Classification utilizes two data storages: +Netwrix Data Classification utilizes two forms of data storage: - NDC SQL database — SQL Server database that stores product configuration and metadata for the data sources. @@ -21,11 +21,11 @@ It is recommended to create the NDC SQL database on a dedicated SQL Server inst - Minimal requirement is SQL Server 2008 R2 Standard Edition. - Estimate required disk space assuming _10 - 12 KB_ per indexed object. For example, for _5, 000, - 000_ objects, the database size will be approximately _50 GB_. - Therefore, SQL Server Express edition will be only suitable for evaluation and PoC environments - (up to 1, 000,000 documents to process). + 000_ objects, the database size will be approximately _50 GB_. + Therefore, SQL Server Express edition is only suitable for evaluation and PoC environments + (processing up to 1,000,000 documents). - **TIP:** Netwrix recommends using SSD storage for both: database and Netwrix Data Classification + **TIP:** Netwrix strongly recommends using SSD storage for both of the database and Netwrix Data Classification servers. - If configuring database settings via SQL Server Management Studio, you will need to set @@ -41,8 +41,9 @@ It is recommended to create the NDC SQL database on a dedicated SQL Server inst Required disk space for the NDC Index file storage will depend, in particular, on the data processing mode you plan to use (_No Index_, _Keyword_ or _Compound Term_). -As a rule of thumb, required space can be calculated as 35% of data you plan to be indexed. For -example, if you have 45 GB of files, they will require up to 15 GB for the NDC Index files. +As a rule of thumb, required space can be calculated as 35% of the total size of the data you +plan to be indexed. For example, if you have 45 GB of files, they will require up to 15 GB for +the NDC Index files. ## Scalability and Performance diff --git a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md index 7a4f11bb91..2b34393169 100644 --- a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md +++ b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md @@ -1,62 +1,59 @@ --- title: "NDC Server Cluster" -description: "Configuring NDC Servers Cluster and Load Balancing with DQS Mode" +description: "Configuring an NDC Server Cluster and Load Balancing with DQS Mode" sidebar_position: 10 --- -# Configuring NDC Servers Cluster and Load Balancing with DQS Mode +# Configuring an NDC Server Cluster and Load Balancing with DQS Mode -The Distributed Query Server (DQS) mode allows you to balance the load between multiple Netwrix Data -Classification Servers (NDC Servers) while data collection, indexing and classification. This -approach is strongly recommended if you need to process large data volumes, for example: +The Distributed Query Server (DQS) mode allows you to balance the processing load of data collection, +indexing and classification over multiple Netwrix Data Classification Servers (NDC Servers) with a single shared database. +This approach is strongly recommended if you need to process large data volumes, for example: -- File Servers—Up to 64 m objects per cluster of 4 servers. -- SharePoint—Up to 32 m objects per cluster of 4 servers. +- File Servers — recommended if processing over 16m objects, +supports up to 64 m objects per cluster of 4 servers. +- SharePoint — Recommended if processing over 8m objects, +supports up to 32 m objects per cluster of 4 servers. -To apply Distributed Query Server mode, you need to arrange your NDC Servers in a 'cluster' for load -distribution, as described below. Each clustered NDC Server will store its own set of .CSE files — -that is, **NDC Index** will be a distributed index. To assemble and combine data required for the +To make use of Distributed Query Server mode, you need to arrange your NDC Servers in a 'cluster' for load +distribution as described below. Each clustered NDC Server will store its own set of .CSE index files, +thus distributing the **NDC Index** over the clustered servers. To assemble and combine data required for the search results, each NDC Server will automatically communicate with the other clustered servers. :::note All NDC Servers in the cluster will share a single NDC SQL database. ::: +This functionality is implemented through the _Query Server_ functionality of NDC Server. -This functionality is implemented through the _QueryServer_ application installed together with NDC -Server. +## Configuring DQS Mode -## Applying DQS Mode - -DQS mode can be configured via the administrative web console. +DQS mode is configured via the administrative web console and, from version 5.7.10 onwards, the installer. If you want to implement DQS configuration for your NDC deployment, consider the following: -- This action cannot easily be undone, so before applying the DQS mode, take a full backup of your - NDC deployment. Also, read the related documentation sections thoroughly before you start. -- Make sure all servers you plan to add to the DQS cluster have proper network connection and are - visible to each other across the network. Adjust firewall settings if necessary. -- Initially, all existing documents will be ‘allocated’ to the first server in the 'cluster' and - then re-distributed across all configured servers. +- This action cannot easily be undone so, before applying the DQS mode, take a full backup of your + NDC deployment. Also, read the DQS documentation sections thoroughly before you start. +- Make sure all servers you plan to add to the DQS cluster have a network connection and are + visible to each other across the network. Adjust your firewall settings if necessary. -To be able to configure the DQS mode, current account requires a **Superuser** role. +DQS mode can only be configured by a user whose account has the **Superuser** role. -To arrange NDC Servers cluster and apply DQS mode + :::note + Once DQS mode is enabled, you cannot roll back your configuration. Netwrix + strongly recommends ensuring that you have taken a full backup of your environment prior to enabling DQS. + ::: + +### Enabling DQS Mode (5.7.9 and earlier versions) 1. Install and configure the first Netwrix Data Classification Server as described in the [Install Netwrix Data Classification](/docs/dataclassification/5.7/introduction/install/overview.md) section. -2. Open administrative web console. -3. Navigate to Settings → Utilities → DQS. +2. Open the administrative web console. +3. Navigate to Settings → Config → Utilities → DQS. 4. Select Enable DQS. - :::note - Once the DQS mode is enabled, you cannot roll back your configuration. Netwrix - strongly recommends to ensure that you have taken a full backup of your environment. If ready, - confirm the DOS enablement operation when prompted. - ::: - -5. On the DQS tab, click Add to add servers you prepared, one by one. +5. On the DQS tab, click Add to adopen the DQS addition menu, and input the details for the first additional NDC server. ![dqs_mode_page_thumb_0_0](/images/dataclassification/5.7/requirements/dqs_mode_page_thumb_0_0.webp) @@ -64,25 +61,24 @@ To arrange NDC Servers cluster and apply DQS mode | Setting | Value | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | - | Server | Provide the NDC Server name or IP address (name format is case-insensitive). | - | QS Path | Path to the solution component responsible for DQS mode, residing on the server being added. Filled in automatically; leave the default value. | - | Active | Select to enable clustering for the instance being added. | - | Alternate Server | Netwrix recommends using default values. | - | Alternate QS Path | Netwrix recommends using default values. | - -6. Click **Save** to close the dialog. -7. Prepare to install other Netwrix Data Classification Server instances, assuming each server + | Server | The NDC Server name or IP address (name format is case-insensitive). | + | QS Path | The path to the solution component responsible for DQS mode, residing on the server being added. This is filled in automatically when filling in the server name; leave the default value. | | + | Alternate Server | Optional, Netwrix recommends using default values. | + | Alternate QS Path | Optional, Netwrix recommends using default values. | + +6. Click **Save** to close the dialog. Repeat steps 5 and 6 for each server you intend to add. +7. Prepare to install the other Netwrix Data Classification Server instances on their dedicated servers. To make best use of resources, each NDC server requires a dedicated machine. Make sure they meet the [Hardware Requirements](/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md) and general [Software Requirements](/docs/dataclassification/5.7/introduction/requirements/softwarerequirements.md) 8. On each server, follow the installation steps as described in the - [Install Netwrix Data Classification](/docs/dataclassification/5.7/introduction/install/overview.md) section until SQL Database - configuration. + [Install Netwrix Data Classification](/docs/dataclassification/5.7/introduction/install/overview.md) section up to the SQL Database + configuration step. 9. On the SQL Database step, provide the name of the SQL Server instance that hosts NDC SQL database you configured for the first NDC Server. :::note -Ignore the confirmation dialog on the existing schema in the selected SQL database. +Ignore the confirmation dialog informing you of the existing schema in the selected SQL database. ::: @@ -92,9 +88,58 @@ Ignore the confirmation dialog on the existing schema in the selected SQL databa ![dqs_servers_list_thumb_0_0](/images/dataclassification/5.7/requirements/dqs_servers_list_thumb_0_0.webp) -12. If you were configuring the DQS mode for the existing NDC deployment, you will be prompted to - re-collect data from the data sources —in order to re-distribute the content index across all - NDC Servers in the cluster. +### Enabling DQS Mode (5.7.10 and later versions) + +1. Install and configure the first Netwrix Data Classification Server as described in the + [Install Netwrix Data Classification](/docs/dataclassification/5.7/introduction/install/overview.md) section. +2. Open the administrative web console. +3. Navigate to Settings → Config → Utilities → DQS. +4. Select Enable DQS. +5. Prepare to install other Netwrix Data Classification Server instances. Make sure each NDC server meets the + [Hardware Requirements](/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md) and general + [Software Requirements](/docs/dataclassification/5.7/introduction/requirements/softwarerequirements.md) +6. On each server, follow the installation steps as described in the + [Install Netwrix Data Classification](/docs/dataclassification/5.7/introduction/install/overview.md) section up to the SQL Database + configuration step. +7. On the SQL Database step, provide the details of the SQL Server instance that hosts the NDC SQL database + you configured for the first NDC Server. +8. When you click next, a message box should appear stating that an NDC configuration was detected and + that the new install will be added to the existing DQS environment - click OK. + + :::note + When upgrading an existing NDC instance the installer will attempt to resynchronise the DQS instances in the + background and, if successful, will skip the DQS Synchronisation step. You can then skip ahead to step 13. The DQS Synchronisation + step will only display for an upgrade if this process fails - this is not an issue, simply follow the steps below + to resynchronise the NDC instance with the primary NDC server. + ::: + +9. The Primary NDC Server Url field should have the server url of the primary NDC server (i.e. the first row in the DQS table) + automatically inserted. If it is not present or is incorrect, enter the address from the QS Path column of the first row of + the DQS table. Then click Connect to connect the installer to that server. +10. Once the installer has successfully connected to the primary NDC server, it will generate an authentication + code and display it in the Authentication Code field. Click Sync to open the NDC DQS settings page in a web browser. +11. On the web page, click on Register/Resync. This will open the authentication code entry tab - the authentication code generated by the installer + should be present in the input field. Click Submit to submit the authentication code. + + :::note + If the authentication code is not autofilled, click on the Authentication Code field in the installer to copy the + value to your clipboard, then paste it in the authentication code field in the NDC UI. + ::: + +12. The Register/Resync tab should now display an 8-digit verification code. Copy this, paste it into + the Verification Code field in the installer, then click Join. The NDC installer will then perform + the resynchronisation. +13. Complete the installation. +14. Repeat steps 6 - 13 for each other new NDC Server, then review the list of servers to make sure all new + servers have been successfully added. + +![dqs_servers_list_thumb_0_0](/images/dataclassification/5.7/requirements/dqs_servers_list_thumb_0_0.webp) + + +If you were configuring the DQS mode for an existing NDC deployment, you will be prompted to + re-collect data from the data sources in order to re-distribute the content index across all + NDC Servers in the cluster. This will result in all data sources being recollected, which may + take a significant amount of time. :::note To force re-distribution when necessary, you can use the Re-Collect command available diff --git a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/ndcserverandclient.md b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/ndcserverandclient.md index 34c3f1220f..3ee9d57fb9 100644 --- a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/ndcserverandclient.md +++ b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/ndcserverandclient.md @@ -6,14 +6,15 @@ sidebar_position: 10 # NDC Server -Netwrix Data Classification **Server** can be deployed on a physical server or on a virtual machine -in the virtualized environment on VMware or Microsoft Hyper-V platform. +Netwrix Data Classification **Server** can be deployed on a physical server or on a virtual machine via software such as +VMware or the Microsoft Hyper-V platform. -When planning for NDC Server, consider a significant CPU load during data processing. Thus, -installing NDC Server on a highly-loaded production machine is not recommended. For more -information, refer to [Hardware Requirements](/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md). +Installing NDC Server on a highly-loaded production machine is not recommended - NDC data +processing is highly resource intensive, and sharing resources with other programs and +processes will decrease the performance of both NDC and the other processes. For more information, +refer to [Hardware Requirements](/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md). -**Web-based client** (management console) is always installed together with the NDC Server, so the +A **web-based client** (management console) is always installed together with the NDC Server, so the IIS server role must be enabled on the target machine. For more information, refer to [Software Requirements](/docs/dataclassification/5.7/introduction/requirements/softwarerequirements.md). @@ -24,12 +25,11 @@ machine image with pre-installed Netwrix Data Classification on Generalized Wind [Requirements to Deploy Virtual Appliance](/docs/dataclassification/5.7/introduction/virtualappliance/systemrequirements.md). ::: - Remember that for production environments, your NDC Server and database server must meet the -[Requirements to Install Netwrix Data Classification](/docs/dataclassification/5.7/introduction/requirements/overview.md). Virtual -appliance configuration is insufficient for production and is not recommended for that purpose. +[Requirements to Install Netwrix Data Classification](/docs/dataclassification/5.7/introduction/requirements/overview.md). +The virtual appliance configuration is insufficient for production and is not recommended for that purpose. -To balance the load while indexing and classifying data in the large-size and extra-large -environments (i.e. with over ≥ 16 mln objects to process), it is strongly recommended to deploy -several NDC Servers and configure **Distributed Query Server** mode for them. +To balance processing load while collecting indexing and classifying data in large-size and extra-large +environments (i.e. 16m+ objects to process), it is strongly recommended to deploy +multiple NDC Servers and configure them as a **Distributed Query Server**. [See Configuring NDC Servers Cluster and Load Balancing with DQS Mode for more information.](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md) diff --git a/docs/dataclassification/5.7/introduction/initialconfiguration/healthalert.md b/docs/dataclassification/5.7/introduction/initialconfiguration/healthalert.md index a7090cd834..e7e0b382ad 100644 --- a/docs/dataclassification/5.7/introduction/initialconfiguration/healthalert.md +++ b/docs/dataclassification/5.7/introduction/initialconfiguration/healthalert.md @@ -16,6 +16,7 @@ Complete the following fields: | Setting | Description | | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Would you like to configure Health Reporting? | Select Setup now if you want to receive health alerts. You can do it later in the communication settings area. [See System Health for more information.](/docs/dataclassification/5.7/dashboards.md) | -| Who should the email be sent from? | Select a user registered in Netwrix Data Classificationadministrative web console in the field or go to the Specific recipients below and specify one or more email addresses outside your organization. | -| What sort of immediate alerts should be sent? | Select the appropriate alerting level: do not receive any alerts at all, receive errors only, or get both: emails for errors and warnings. [See System Health for more information.](/docs/dataclassification/5.7/dashboards.md) | -| Should a daily health summary be sent? | Select whether you want to receive daily summary on the product health. | +| Who should the email be sent from? | Select a user registered in Netwrix Data Classification administrative web console in the field or go to the Specific recipients below and specify one or more email addresses outside your organization. | +| What sort of immediate alerts should be sent? | Select the appropriate alert level for the emails you wish to receive: do not receive any alerts at all, only receive alerts for errors, or get emails for both errors and warnings. [See System Health for more information.](/docs/dataclassification/5.7/dashboards.md) | +| Should a daily health summary be sent? | Select whether you want to receive daily summary on the current health status of NDC. | + | diff --git a/docs/dataclassification/5.7/introduction/initialconfiguration/modes.md b/docs/dataclassification/5.7/introduction/initialconfiguration/modes.md index 2842060ab2..0457960335 100644 --- a/docs/dataclassification/5.7/introduction/initialconfiguration/modes.md +++ b/docs/dataclassification/5.7/introduction/initialconfiguration/modes.md @@ -24,15 +24,15 @@ for data discovery, data security governance and compliance use cases. ## Keyword In this mode the search index will be created; however, disk space required for the core search -index will be of medium size. Both **Browse** and **Search** by keyword will be supported. Overall +index will be of medium size. Both **Browse** and **Search** by keyword are supported. Overall throughput is capable of supporting large number of documents (> 1M). Recommended for compliance, data discovery and classification rules tuning. ## Compound Term -In this mode you will get a fully featured index, supporting **Search** by compound term. Consider -that data storage will require more space, and overall throughput may decrease (compared to the -Keyword mode). Recommended for knowledge management, data storage optimization, legal search, other -content services. +In this mode you will get a fully featured index, supporting **Search** by compound term. Bear in mind +that data storage for compound term processing will require significantly more space, and overall throughput +may decrease (compared to the Keyword mode). Recommended for knowledge management, data storage optimization, +legal search, other content services. Proceed with configuring processing settings. See [Processing Settings](/docs/dataclassification/5.7/introduction/initialconfiguration/processingsettings.md) next. diff --git a/docs/dataclassification/5.7/introduction/initialconfiguration/overview.md b/docs/dataclassification/5.7/introduction/initialconfiguration/overview.md index ee70446c8d..13b8252744 100644 --- a/docs/dataclassification/5.7/introduction/initialconfiguration/overview.md +++ b/docs/dataclassification/5.7/introduction/initialconfiguration/overview.md @@ -9,7 +9,7 @@ sidebar_position: 80 The Product Configuration Wizard allows you quickly configure basic Netwrix Data Classification settings such as processing mode, taxonomies, etc. -In your web browser, navigate to the following URL: http://hostname/conceptQS where hostname is the +In your web browser, navigate to the following URL: http://hostname/NDC where hostname is the name or IP address of the computer where Netwrix Data Classification is installed and perform initial configuration steps. diff --git a/docs/dataclassification/5.7/introduction/initialconfiguration/processingsettings.md b/docs/dataclassification/5.7/introduction/initialconfiguration/processingsettings.md index d31a31e2b5..c574ace2e5 100644 --- a/docs/dataclassification/5.7/introduction/initialconfiguration/processingsettings.md +++ b/docs/dataclassification/5.7/introduction/initialconfiguration/processingsettings.md @@ -15,14 +15,14 @@ Review the following for additional information: | Option | Description | | ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Text Extraction | | -| Should OCR be used on image files? | Optical Characters Recognition is a technology used to extract text from images. Enable OCR if the content being collected contains a large number of scanned documents (for example). Performing OCR on documents can significantly reduce indexing performance. **IMPORTANT!** OCR requires the Visual C++ Redistributable for Visual Studio 2015. Visit Microsoft [website](http://microsoft.com/en-gb/download/details.aspx?id=48145) for downloading. | -| Should images embedded in documents be processed? | Enable this option to recognize documents with integrated images. | +| Should OCR be used on image files? | Optical Characters Recognition is a technology used to extract text from images. Enable OCR if the content being collected contains a large number of scanned documents (for example). Performing OCR on documents can significantly reduce indexing performance. **IMPORTANT!** OCR requires the Visual C++ Redistributable for Visual Studio 2015. Visit the Microsoft [website](http://microsoft.com/en-gb/download/details.aspx?id=48145) to download it. | +| Should images embedded in documents be processed? | Enable this option to perform OCR text extraction on images contained within documents | | Should the collection process optimise text storage by re-using text offsets? | Enable this option to use text offsets. | | Classification Configuration | | -| Should default clues be automatically created? | Enable if you want a clue to be created automatically when a registering taxonomy from SharePoint or term creation. The created clue is standard and matches the term name or a metadata clue depending on the configuration specified at the taxonomy level settings. [See Classification Rules (Clues) for more information.](/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/clues.md) | +| Should default clues be automatically created? | Enable if you want a default clue to be created automatically when registering a taxonomy from SharePoint or creating a classification term within the NDC UI. The created clue will either be a standard clue matching the term name, or a metadata clue, depending on the configuration specified at the taxonomy level settings. [See Classification Rules (Clues) for more information.](/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/clues.md) | | Should boosted phrasematch scoring be enabled? | Enable to boost the score of any phrasematch clues if the phrase appears multiple times in the document. | | Should boosted regex scoring be enabled? | Enable to boost the score of any regex clues if the regular expression appears multiple times in the document. | | How should regular expressions be processed? | Enables and disables case sensitivity when processing regular expressions. | -| Store trimmed classifications to improve reclassification performance? | Enable to store trimmed classifications to SQL database (trimmed due to the maximum number of classifications being hit for a document). This improves classification performance, however, this may lead to additional data in the SQL database. | +| Store trimmed classifications to improve reclassification performance? | Enable to store trimmed classifications to the SQL database (trimmed due to the maximum number of classifications being hit for a document). This improves classification performance, however, this will increase the size of the SQL database. | Proceed with adding taxonomies. diff --git a/docs/dataclassification/5.7/introduction/initialconfiguration/security.md b/docs/dataclassification/5.7/introduction/initialconfiguration/security.md index 478495d850..3d15b00f55 100644 --- a/docs/dataclassification/5.7/introduction/initialconfiguration/security.md +++ b/docs/dataclassification/5.7/introduction/initialconfiguration/security.md @@ -6,19 +6,19 @@ sidebar_position: 40 # Security -On this step, you are prompted to restrict access to administrative web console by adding users. +On this step, you are prompted to choose how access to the administrative web console is controlled. ![initial_config_users](/images/dataclassification/5.7/install/initialconfiguration/initial_config_users.webp) -- Enable user management – select to add super users and prevent unauthorized access to - administrative web console. By default, any authenticated users have access to the console. +- Enable User Management - (Recommended) This enables control over access to different sections + of the administrative web console on a user by user basis. Users can be set as super users, granting + full access, or can have their access granularly controlled using the Users settings page. :::note - Netwrix recommends enabling this option. + Netwrix strongly recommends enabling this option. ::: - - When selected, you are prompted to add super users. Type the name of the new user and click + on - the right. + When selected, you will be prompted to add super users. Type the name of any super user you wish to add and click + on + the right. USers with restricted access to NDC will need to be added via the Users configuration page at a later point. - Allow access for all users – select to allow any user access administrative web console. diff --git a/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md b/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md index 2637b035ef..61158f4066 100644 --- a/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md +++ b/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md @@ -6,17 +6,17 @@ sidebar_position: 10 # Configure NDC SQL database -Netwrix Data Classification uses Microsoft SQL Server database as metadata storage. During -installation, you have been prompted to create a dedicated NDC SQL database on your SQL Server +Netwrix Data Classification uses a Microsoft SQL Server database as metadata storage. During +installation, you are prompted to create a dedicated NDC SQL database on your SQL Server instance. Upon installation completion, you need to configure it as shown below for the product to -function properly. You can create the database manually prior to the product installation—Using SQL -Server Management Studio or Transact-SQL. Refer to the following Microsoft article for detailed +function properly. You can create the database manually prior to the product installation using SQL +Server Management Studio or any other Microsoft SQL management program. Refer to the following Microsoft article for detailed instructions on how to create a new database: [Create a Database](https://docs.microsoft.com/en-us/sql/relational-databases/databases/create-a-database). :::note -For performance purposes, Netwrix strongly recommends to separate NDC and SQL Server -machine. +For performance purposes, Netwrix strongly recommends to install NDC and the SQL Server hosting +the NDC database on separate servers. ::: @@ -30,22 +30,23 @@ role. ::: -1. On the computer where SQL Server instance with the NDC SQL database resides, navigate to Start → - All Programs → Microsoft SQL Server → SQL Server Management Studio. -2. Connect to the server. -3. Locate the NDC_Database, right-click it and select Properties. -4. Select the Files page and set the Initial Size (MB) parameter for PRIMARY file group to 512 MB. -5. Click Expand next to PRIMARY file group and set Autogrowth / Maxsize as follows: +1. Open SQL Server Management Studio or your desired SQL IDE and connect to the +SQL Server instance hosting the NDC database. Depending on your security +setup, it may be necessary to do this on the server itself. +1. Open the properties window for the NDC database. In SQL Server Management Studio +this is done by selecting the database in the explorer tab on the left side of the window, +right-clicking, and selecting Properties. +1. Select the Files page and set the Initial Size (MB) for the PRIMARY file group to 512MB. +1. Set the Autogrowth and Max Size for the PRIMARY file group as follows: | Option | Description | | ----------------- | -------------------------------------------------- | | File Growth | - Recommended—128 MB. - Large environment— 512 MB. | | Maximum File Size | Select Unlimited. | -6. Go to Options page and make sure that the Recovery model parameter is set to "_Simple_". +1. Select the Options page and make sure the Recovery model is set to "_Simple_". :::note - Netwrix recommends that you do not change the recovery model to avoid log files - growth. - + Netwrix recommends that you do not change the recovery model to avoid excessive log file + growth. ::: diff --git a/docs/dataclassification/5.7/introduction/install/overview.md b/docs/dataclassification/5.7/introduction/install/overview.md index a1ca0e4278..f727f1f186 100644 --- a/docs/dataclassification/5.7/introduction/install/overview.md +++ b/docs/dataclassification/5.7/introduction/install/overview.md @@ -7,23 +7,25 @@ sidebar_position: 40 # Install Netwrix Data Classification 1. Run Netwrix_Data_Classification.exe. -2. Review minimum system requirements and then read the License Agreement. Click Next. +2. Review the minimum system requirements, then read the License Agreement. Click Next. 3. Follow the instructions of the setup wizard. When prompted, accept the license agreement. -4. On the Product Settings step, specify path to install Netwrix Data Classification. For example, +4. On the Product Settings step, specify the folder to install Netwrix Data Classification to. For example, _D:\Data\NDC\Index._ -5. On the Configuration step, specify the directory where Index files reside. For example, +5. On the Configuration step, specify the directory in which the Index files will be stored. For example, _C:\Program Files\NDC\Index_. -6. On the SQL Database step, provide SQL Server database connection details. +6. On the SQL Database step, provide the SQL Server database connection details. Complete the following fields: | Option | Description | | --------------------- | ------------------------------------------------------------------------------------------------------------------------ | - | Server Name | Provide the name of the SQL Server instance that hosts your NDC SQL database. For example, _"WORKSTATIONSQL\SQLSERVER"_. | + | Server Name | Provide the name of the SQL Server instance that hosts or will host your NDC SQL database. For example, _"WORKSTATIONSQL\SQLSERVER"_. | | Authentication Method | Select Windows or SQL Server authentication method. | | Username | Specify the account name. | - | Password | Provide your password. | - | Database Name | Enter the name of the SQL Server database. Netwrix recommends using NDC_database name. | + | Password | Provide the account password. | + | Database Name | Enter the name of the NDC database. Netwrix recommends using NDC as the database name. | + + If the database does not yet exist, you'll need to click Create SQL Database before moving to the next step - this will automatically create the NDC database with the given name and default configuration. :::note The database is created automatically in basic configuration mode. For recommended @@ -31,23 +33,31 @@ sidebar_position: 40 to [Configure NDC SQL database](/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md) section. ::: +7. If you are installing a secondary NDC instance to an [NDC Distributed Query Server](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md), +you will be shown the DQS registration step. Complete the following steps: + a. Confirm that the Primary NDC Server URL displayed matches the QS Path of the primary NDC instance (the first entry in the DQS table in the administrative web console) and click Connect to connect the installer to the primary instance. + b. When the connection succeeds, an Authentication code will be generated and displayed in the Authentication Code textbox. Click Register - this will copy the Authentication code to the clipboard and open the administration console DQS configuration page in a browser window. + c. Click Register/Resync. The authentication code should automatically be inserted into the input box, paste the code if it hasn't been then click Submit. + d. Copy the verification code displayed and input it into the Verification code input box in the installer, then click Join. + e. Once the NDC instance has been successfully joined to the DQS configuration, you can click Next to move to the next installation step. + -7. On the Licensing step, add license. You can add license as follows: +8. On the Licensing step, add your license. You can add the license as follows: - Click the Import button and browse for your license file _OR_ - - Open your license file with any text editor, e.g., Notepad and paste the license text to the + - Open your license file with any text editor, e.g. Notepad, and paste the license text into the License field. -8. On the Administration Web Application step, review default IIS configuration. -9. On the Services step, configure Netwrix Data Classification services: +9. On the Administration Web Application step, review the default IIS configuration. If you select to run the Administration Web Application as a local or domain user, you will need to input the credentials for that user. +10. On the Services step, configure Netwrix Data Classification services: - Select all services to be installed. - - File System Path—Use default path or provide a custom one to store Netwrix Data + - File System Path—Use the default path or provide a custom one to store Netwrix Data Classification's Services files. For example, _C:\Program Files\NDC Services._ - - Provide user name and password for the product services service account. + - Provide credentials for the product services service account. :::note This account is granted the Logon as a service privilege automatically on the @@ -57,7 +67,7 @@ sidebar_position: 40 - Select additional service options, if necessary. -10. On the Pre-Installation Tasks and Checks step, review your configuration and select Install. -11. When the installation completes, open a web browser and navigate to the following URL: - _http://localhost/conceptQS_ where localhost is the name or IP address of the computer where - Netwrix Data Classification is installed. For example, _http://workstationndc/conceptQS_. +11. On the Pre-Installation Tasks and Checks step, review your configuration and select Install. +12. Once the installation completes, open a web browser and navigate to the following URL: + _http://SITENAME/NDC_ where SITENAME is the name or IP address of the computer where + Netwrix Data Classification is installed. For example, _http://workstationndc/NDC_. diff --git a/docs/dataclassification/5.7/introduction/introduction.md b/docs/dataclassification/5.7/introduction/introduction.md index f30ca850aa..985466eff1 100644 --- a/docs/dataclassification/5.7/introduction/introduction.md +++ b/docs/dataclassification/5.7/introduction/introduction.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Deployment -This section lists all information to flawlessly install Netwrix Data Classification. +This section provides instructions for installing Netwrix Data Classification and setting up data sources. Review the following for additional information: diff --git a/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md b/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md index 629fd22dc9..376405fcc4 100644 --- a/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md +++ b/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md @@ -34,19 +34,18 @@ See [Deployment Planning](/docs/dataclassification/5.7/introduction/deployment/o | Cores | 8 Cores | | RAM | 32 GB | | Hard disk | UP TO 35% of all data in scope | -| Hard drive type | SSD storage (recommended) | +| Hard drive type | SSD storage | ## SQL Server -Review the hardware requirements for the computer where Netwrix Data Classification SQL Database -will be deployed. +The requirements in this section are for an SQL database supporting up to 4 linked NDC instances. The NDC database server should only be deployed on a dedicated machine, as sharing resources with additional databases on the same server will degrade performance. | Hardware Component | Up to 16 M objects | Up to 32 M objects and up to 8 M objects for SharePoint | Up to 64 M objects and up to 16 M objects for SharePoint | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | -------------------------------------------------------- | | Processor | 8 cores | 8 cores | 8 cores | | RAM | 32 GB | 64 GB | 128 GB | -| Hard disk | Estimate required disk space assuming _1012 KB_ per indexed object. For example, for _5, 000, 000_ objects, the database size will be approximately _50 GB_. See also [Deployment Planning](/docs/dataclassification/5.7/introduction/deployment/overview.md). | | | -| Hard disk type | SSD storage (recommended) | | | +| Hard disk | Estimate required disk space assuming _1012KB_ per indexed object. For example, for _5,000,000_ objects, the database size will be approximately _50GB_. See also [Deployment Planning](/docs/dataclassification/5.7/introduction/deployment/overview.md). | | | +| Hard disk type | SSD storage | | | ## Network Access @@ -65,12 +64,11 @@ scope. Supported file shares types: Administration Dashboards for most Network Attached Storages include storage usage such as the amount of data and files count. In case you need a tool to calculate file count and size, you can -use NDC script-based -[file scanning tool](https://www.netwrix.com/download/products/DDC/ScanDirs.zip). +use the NDC script-based [file scanning tool](https://www.netwrix.com/download/products/DDC/ScanDirs.zip). **Exchange Mailboxes** -In case you have Exchange on-prem you would need to know the additional information: +If you plan on using NDC to crawl an on-premise Exchange server, you need to know the following: - Number of Mailboxes - Mailbox retention policy (for how long users keep their emails before they are archived) @@ -78,18 +76,15 @@ In case you have Exchange on-prem you would need to know the additional informat The number of emails in all mailboxes can be obtained with the PowerShell script for the Exchange Management Shell bellow. The script will return email stats for every mailbox. Use the script -results calculate the average number of emails per mailbox or provide the total number. +results to calculate the average number of emails per mailbox or provide the total number. ``` Get-Mailbox -ResultSize Unlimited | Get-MailboxStatistics SelectItemCount | ForEach {$totalItems+=$_.ItemCount} ``` -Office 365: Exchange Online, SharePoint Online and One Drive +**Office 365: Exchange Online, SharePoint Online and One Drive** -Provide the total amount of data and total file stored on Office 365. You can use the usage -statistics numbers for 180 days period from the O365 Admin Center dashboard. Refer to the following -Microsoft article for additional information: -[Microsoft 365 Reports in the admin center](https://learn.microsoft.com/en-us/microsoft-365/admin/activity-reports/activity-reports?view=o365-worldwide) +Provide the total amount of data and total number of files stored on Office 365. You can use the usage statistics numbers for 180 days period from the O365 Admin Center dashboard. Refer to the following Microsoft article for additional information: [Microsoft 365 Reports in the admin center](https://learn.microsoft.com/en-us/microsoft-365/admin/activity-reports/activity-reports?view=o365-worldwide) **Databases** @@ -97,7 +92,7 @@ In case your scope includes databases, the following details are required: - Database type (MS SQL, Oracle, MySQL) - What applications and systems those databases support -- How many databases the data need to be classified in +- How many databases the data needs to be classified in Netwrix Data Classification will need to be pointed at certain tables in the specified databases, the customer is expected to know which tables within a database may potentially contain sensitive diff --git a/docs/dataclassification/5.7/introduction/requirements/supportedcontenttypes.md b/docs/dataclassification/5.7/introduction/requirements/supportedcontenttypes.md index 512ec284cf..f331f0ba79 100644 --- a/docs/dataclassification/5.7/introduction/requirements/supportedcontenttypes.md +++ b/docs/dataclassification/5.7/introduction/requirements/supportedcontenttypes.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Supported Content Types -The table below lists types of content and their default extensions supported out of the box. +The table below lists the content types NDC supports out of the box, and their default extensions. :::note To review the full list of available content types, navigate to Config → Text Processing → diff --git a/docs/dataclassification/5.7/introduction/upgrade.md b/docs/dataclassification/5.7/introduction/upgrade.md index ce048ff9fd..6905360b3d 100644 --- a/docs/dataclassification/5.7/introduction/upgrade.md +++ b/docs/dataclassification/5.7/introduction/upgrade.md @@ -7,7 +7,7 @@ sidebar_position: 50 # Upgrade to the Latest Version Netwrix recommends that you upgrade from the older versions of Netwrix Data Classification to the -latest version available in order to take advantage of the new features. +latest version available in order to take advantage of new features and fixes. ## Upgrade Prerequisites @@ -28,22 +28,34 @@ Classification resides. If not, download it from Microsoft website: - On the computer where Netwrix Data Classification is installed, start the Netwrix Data Classification Service Viewer tool. Select **Stop** next to each service. -- Locate the folder containing index files (default location is _C:\Program - Files\ConceptSearching\ConceptDB_) and back it up. +- Locate the folder containing index files (the default location is _C:\Program + Files\Netwrix\Data Classification\Index_) and back it up. -**Step 4 –** Confirm that the NDC services and IIS Application pool are running as the same service -account on all NDC servers. That account also needs to be a domain account. +**Step 4 –** For versions of 5.7 prior to 5.7.10, it was necessary to have all NDC services and the NDC +IIS Application Pool running as the same service account. For 5.7.10 onwards this is no longer necessary, but if upgrading +from an earlier version of 5.7 you should complete the upgrade to 5.7.10 _before_ changing the service account +to prevent any possible issues with the upgrade process. ## Upgrade Process -Seamless upgrade to Netwrix Data Classification 5.7 is supported for versions 5.5 and newer. +It is only possible to upgrade directly to Netwrix Data Classification 5.7 from versions 5.5 and newer. To upgrade your deployment, after taking the preparatory steps described above, run the product setup and follow the wizard steps. When finished, all solution components will be up and running. -If you need to upgrade from an earlier version, you should perform a staged upgrade, first upgrade +If you need to upgrade from an earlier version, you will need to perform a staged upgrade: first upgrade to version 5.5, then perform a second upgrade to version 5.7. +## Upgrading a DQS environment + +When upgrading an NDC environment which utilises the **Distributed Query Server** functionality, the primary server +should be upgraded first before upgrading the secondary instance(s). + +If you are upgrading to 5.7.10 or later from an earlier version of 5.7, if possible you should +run the installer as the NDC service account. If this is not done, you will need to perform a DQS +resynchronisation when upgrading each secondary DQS instance. For further details on this process, +see the [DQS Instructions](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md) page. + ## After the Upgrade During the seamless upgrade from previous versions, Netwrix Data Classification preserves its diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/administration/indexmaintenance/indexmaintenance.md b/docs/dataclassification/5.7/systemconfigurationoverview/administration/indexmaintenance/indexmaintenance.md index 7ecbc62cab..dcf0d98a54 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/administration/indexmaintenance/indexmaintenance.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/administration/indexmaintenance/indexmaintenance.md @@ -10,10 +10,10 @@ This feature is only available for ‘Superusers’. You may need to reprocess content or even clean the environment on a large scale — for example, after a large amount of content has been deleted, or after configuring a DQS environment. In such -scenarios, index should also be maintained — to ensure data consistency. To automate maintenance -operations, you can use a built-in tool named Cleaner. +scenarios, the index should also be maintained — to ensure data consistency. To automate maintenance +operations, you can use the built-in Index Cleaner tool. -Follow the steps to launch the Cleaner tool. +Follow these steps to launch the Index Cleaner tool. 1. Open NDC Management Web Console. 2. Navigate to **Settings** > **Config** and click **Run Cleaner**. diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/communicationsettings.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/communicationsettings.md index 6a2c3e3eb3..05166fd73a 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/communicationsettings.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/communicationsettings.md @@ -15,10 +15,10 @@ configuring email groups and health service notifications. Review the following [](#)Email Servers -Email servers can be configured to enable external communication. For instance when the health -service identifies an issue. +Email servers can be configured to enable external communication. This can be used to send report +subscriptions and health errors to users automatically. -Servers can be amended post configuration by selecting Edit, or, new SMTP servers can be added by +Servers can be amended post-configuration by selecting Edit, and new SMTP servers can be added by selecting Add Email Server Configuration. ![configemailservers](/images/dataclassification/5.7/configuration/configemailservers.webp) diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md index 2fb3677ee7..9c7d5f8c3b 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md @@ -10,7 +10,7 @@ This configuration tab contains general options, as well as those that apply to to Concept Classifier app. By default, only basic options are displayed. To view advanced options, click the "wrench" icon at **Settings** in the bottom-right corner. -Nearly each configuration option has an associated “i” which describes the nature of the setting. +Most options have an associated information popup (the “**i**” symbol next to the option name) which describes what the setting does and how it works. ![core_admin_thumb_0_0](/images/dataclassification/5.7/configuration/core/core_admin_thumb_0_0.webp) @@ -20,7 +20,6 @@ Nearly each configuration option has an associated “i” which describes the n | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **General settings** | | | | Report Source Filter Mode | Use to add an additional filter for either Source Groups (default) or Source(s) | | -| Color Scheme | Select your preferred theme for the UI: orange or blue. | | | Disable Security Trimming | Select this option if you want to ensure that search results retrieved by API or the Taxonomies area will be unfiltered (ignoring the user name of the administrative user). | Disables the application of security trimming from search results (taxonomy browse/search). | | **Advanced settings** | | | | Instance name | Name of the NDC Server instance | | @@ -34,13 +33,13 @@ These settings allow you to customize configuration of classification taxonomies | Option | Description | Comment | | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | | **General settings** | | | -| Create Default Clues | Automatically creates a clue when a new term is created, using the term name as the clue text and default threshold value as the score. | | +| Create Default Clues | Automatically creates a Standard clue when a new term is created, using the term name as the clue text and default threshold value as the score. | | | User Term Suggestions | Enables/Disables a custom form designed to allow end-users to make suggestions on new terms for administrators. | | | User Term Suggestions Notification Email Group | Enables an automatic notification to a pre-configured email group when a term suggestion is created. | | | **Advanced settings** | | | | Synonyms Enabled | Used to control whether synonyms (for each standard clue) are configurable for taxonomies residing in the local SQL database. | | | Working Set Mode | Configures the Working Set functionality under 'Taxonomies'. Possible options: | Changing this option will remove all documents from the current working set. | -| Taxonomy Default Page Size | Number of documents returned by Taxonomy Manager. | | +| Taxonomy Default Page Size | Number of documents returned by default from Taxonomy Manager searches. | | | # Doc Metadata Fields Shown | Number of hint fields to be shown in Taxonomy Manager. | | | Term User Locking Enabled | Enables/Disables the ability to "lock" terms when performing taxonomy management, preventing other users from editing the locked terms. | | | Enable Regex Browse Highlighting | When enabled, any search results found via the Browse UI will have any matched regular expressions highlighted (based on the selected terms clues). | | diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/classifier.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/classifier.md index d79b84f4ee..b10bb1798f 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/classifier.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/classifier.md @@ -10,13 +10,12 @@ The **Classifier** configuration tab contains the classification engine settings standard options are displayed. To view advanced options, click the "wrench" icon at **Settings** in the bottom-right corner. -Each option has an associated “**i**” which describes the nature of the setting. +Each option has an associated information popup (the “**i**” symbol next to the option name) which describes what the setting does and how it works. ![core_thumb_0_0](/images/dataclassification/5.7/configuration/core_thumb_0_0.webp) :::note -To view a complete list of the **Config** settings, click the Details tab. The list also -has an indication of the values that have been changed from the default setting. +To view a complete list of the **Config** settings for your NDC instance, click the Details tab. The list indicates if a setting has been changed from the default value. ::: diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/conceptclassifier.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/conceptclassifier.md index 3ff3bd8e24..b7028f1772 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/conceptclassifier.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/conceptclassifier.md @@ -10,7 +10,7 @@ This section contains the settings related to conceptClassifier application. As options, you should click the screwdriver icon at **Settings** in the bottom-right corner to view them. -Each option has an associated “**i**” which describes the nature of the setting. +Each option has an associated information popup (the “**i**” symbol next to the option name) which describes what the setting does and how it works. ![core_thumb_0_0](/images/dataclassification/5.7/configuration/core_thumb_0_0.webp) diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/generaloptions.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/generaloptions.md index 2c2b4d384a..8068398a97 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/generaloptions.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/generaloptions.md @@ -10,13 +10,12 @@ The **General** section contains general classification engine settings, e.g. . standard options are displayed. To view advanced options, click the screwdriver icon at **Settings** in the bottom-right corner. -Each option has an associated “**i**” which describes the nature of the setting. +Each option has an associated information popup (the “**i**” symbol next to the option name) which describes what the setting does and how it works. ![core_thumb_0_0](/images/dataclassification/5.7/configuration/core_thumb_0_0.webp) :::note -To view a complete list of the **Config** settings, click the Details tab. The list also -has an indication of the values that have been changed from the default setting. +To view a complete list of the **Config** settings for your NDC instance, click the Details tab. The list indicates if a setting has been changed from the default value. ::: @@ -25,8 +24,8 @@ has an indication of the values that have been changed from the default setting. | Option | Description | Comment | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Standard settings** | | | -| Max Categories | Sets the maximum number of classifications to be allocated to each document. Possible values: | If a document matches so many categories that the specified value would be exceeded, then the classification service will select the required number of categories based on those that have the highest score.
**NOTE:** Higher value causes the engine to use more RAM, so it is recommended to use the default setting (unless it is essential that more categories are allocated to each document). | -| Retain Existing Metadata Mode | Specifies how the classification engine should process already existing classification (managed metadata fields). Possible options: | Applies to SharePoint source. | +| Max Categories | Sets the maximum number of classifications to be allocated to each document: | If a document matches enough categories that the specified maximum would be exceeded, then the classification service will select the required number of categories based on those that have the highest score.
**NOTE:** Higher limits cause the classifier engine to use more RAM, so it is recommended to use the default setting (unless it is essential that more categories are allocated to each document). | +| Retain Existing Metadata Mode | Specifies how the classification engine should process documents with existing classifications (managed metadata fields). Possible options: | Applies to SharePoint source. | | Auto-Classification Change Logs | Enables a change log for auto-classification: each "Addition"/"Removal" of a classification against a document will be stored in the database as its classifications change. | Inactive by default. See also [Manage Reports](/docs/dataclassification/5.7/dataanalysisoverview/reportingintroduction/manage.md) | | Classifier Threads | The number of background threads used for classification. Default is **0 (auto)**. | We recommend leaving this setting on its default value. For more information, see this Knowledge Base article: [https://kb.netwrix.com/3863](https://kb.netwrix.com/3863) | | Classifier Write Threads | The number of threads to be utilised by the Classifier to update source systems during "tagging" operations (i.e. writing classification back to source system). | Each thread can be considered a "user" when considering load on the source system. For more information, see this Knowledge Base article: [https://kb.netwrix.com/3863](https://kb.netwrix.com/3863) | diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/monitoredcontent.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/monitoredcontent.md index 10edb9e478..d9c959bed5 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/monitoredcontent.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/monitoredcontent.md @@ -13,8 +13,7 @@ conditions are met, or with a minimum time period between runs. ![core_thumb_0_0](/images/dataclassification/5.7/configuration/core_thumb_0_0.webp) :::note -Each option in this section has an associated “**i**” which describes the nature of the -setting. +Each option has an associated information popup (the “**i**” symbol next to the option name) which describes what the setting does and how it works. ::: diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/collector.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/collector.md index a9a465e1df..ae69ce0840 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/collector.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/collector.md @@ -6,8 +6,7 @@ sidebar_position: 30 # Collector -This configuration tab contains the classification engine settings. Each configuration option has an -associated “i” which describes the nature of the setting. +This configuration tab contains the classification engine settings. Each option has an associated information popup (the “**i**” symbol next to the option name) which describes what the setting does and how it works. ![core_collector](/images/dataclassification/5.7/configuration/core/core_collector.webp) diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/coreconfiguration.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/coreconfiguration.md index 281ac32df1..601defc41d 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/coreconfiguration.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/coreconfiguration.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Core Configuration -Each configuration option has an associated “i” which describes the nature of the setting. Selecting +Each option has an associated information popup (the “**i**” symbol next to the option name) which describes what the setting does and how it works. Selecting the Details tab provides a complete list of the Config settings – as well as an indication of the values that have been changed from the default setting. diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/indexer.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/indexer.md index 24d1c4c94a..e72f9cbbdb 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/indexer.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/indexer.md @@ -6,8 +6,7 @@ sidebar_position: 20 # Indexer -This configuration tab contains the indexing engine settings. Each configuration option has an -associated “**i**” which describes the nature of the setting. To view advanced options, click the +This configuration tab contains the indexing engine settings. Each option has an associated information popup (the “**i**” symbol next to the option name) which describes what the setting does and how it works. To view advanced options, click the screwdriver icon at **Settings** on the right. ![core_indexer_thumb_0_0](/images/dataclassification/5.7/configuration/core/core_indexer_thumb_0_0.webp) diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/system.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/system.md index 1f0de51bd7..e00b99c6dc 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/system.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/system.md @@ -6,8 +6,7 @@ sidebar_position: 60 # System -This configuration tab contains the settings related to system health, operation and logging. Each -configuration option has an associated “i” which describes the nature of the setting. +This configuration tab contains the settings related to system health, operation and logging. Each option has an associated information popup (the “**i**” symbol next to the option name) which describes what the setting does and how it works. ![core_system_thumb_0_0](/images/dataclassification/5.7/configuration/core/core_system_thumb_0_0.webp) @@ -16,12 +15,12 @@ configuration option has an associated “i” which describes the nature of the | Option | Description | Comment | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------- | | **General settings** | | | -| Log Level | Defines logging level that should be persisted to the log targets. Possible options: | | -| Tracing | Used to provide additional information/ functionality. | Will apply to selected components (none by default) | -| Log Targets | Select where the log should be written: to a file, to Windows Event Log, or both. | | -| File Log Location | If you selected to write log to a file, this location path will be used. | Default is _C:\ProgramData\Netwrix Data Classification\Logs_ | +| Log Level | Defines logging level that should be persisted to the log targets. Supported levels: | Each level includes all logs from higher levels. | +| Tracing | Used to control which components of the system persist logs to the log targets. | Will apply to selected components (none by default) | +| Log Targets | Select where the log should be written: to a csv file, to Windows Event Log, or both. | | +| File Log Location | If you selected to write logs to file, the csv log files will be stored at this location path. | Default is _C:\ProgramData\Netwrix Data Classification\Logs_. This cannot be manually changed. | | File Log Retention Period | Number of days (since the last use) that file logs should be kept for before deletion. | To keep all logs (without automatic deletion), specify _0_ . | -| Send anonymous usage statistics? | Disabled by default. When enabled, the program will send a small amount of information of how the product is being used — to improve the functionality and future offering. | Personal information/ company data will not be sent. | +| Send anonymous usage statistics? | Disabled by default. When enabled, the program will send a small amount of information of how the product is being used — to improve the functionality of the product and future offerings. | Personal information/ company data will not be sent. | | **Advanced settings** | | | | Max Database Size | Specifies the max size (in GB) the SQL database will grow to. | When this value is reached, Collector and Indexer components will be suspended. Default is _0_ (no limit). | | Database Maintenance Schedule | Specify the schedule for running database maintenance (including the rebuilding of SQL Server indexes) | Default is _Everyday_. | diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/texthandling.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/texthandling.md index 7e7e5c6538..46c53be00e 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/texthandling.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/texthandling.md @@ -81,6 +81,7 @@ clue – or a search term. The OCR language mapping configuration screen can be used if you wish to OCR non-English images via Tesseract. File paths (including parts of paths) can be mapped to specific Tesseract language packs. +The Page Segmentation Mode used by the Tika OCR can also be overridden here for a given file path. ![configocrlanguagemapping](/images/dataclassification/5.7/configuration/configocrlanguagemapping.webp) diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/users/passwordmanager.md b/docs/dataclassification/5.7/systemconfigurationoverview/users/passwordmanager.md index 0acecea1f9..38e76aaea9 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/users/passwordmanager.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/users/passwordmanager.md @@ -6,13 +6,13 @@ sidebar_position: 30 # Password Manager -Password manager can be used to automatically schedule password changes, for service accounts that +The Password manager can be used to automatically schedule password changes for service accounts that are being used to access external systems. This is particularly useful when there are business policies in place to change passwords on a rolling basis. ![passwordmanager_thumb_0_0](/images/dataclassification/5.7/security/passwordmanager_thumb_0_0.webp) To amend the passwords for a username record first select Passwords from the main display. Then -either click Edit on a particular password row, or, click Add Password to add a new password for the +either click Edit to change a specific password or click Add Password to add a new password for the account. It is not possible to have overlapping date ranges for the defined passwords, nor is it possible to remove all passwords from a user record. diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/users/securendc.md b/docs/dataclassification/5.7/systemconfigurationoverview/users/securendc.md index 3ce58b4662..e6d1c2be66 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/users/securendc.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/users/securendc.md @@ -16,7 +16,7 @@ By default, post installation, all users will be considered Superusers with acce the product. To begin the process of securing the product please follow the below steps: 1. Access the Administration Console. -2. Select Users from the top navigation bar. +2. Select Settings > Users from the top navigation bar. 3. Select Add. 4. Your username will be pre-filled and must first be added to ensure that you do not lose access to the system. @@ -64,11 +64,11 @@ the full text at rest. You can enable this mode by: 1. Access the Administration Console; 2. Select Config from the top navigation bar; -3. Enable the Encrypt Text (Text.cse) option (under advanced settings - select the screwdriver - spanner to show); +3. On the Collector tab, enable the Encrypt Text (Text.cse) option (this is an advanced setting - +select the spanner icon in the bottom left to display it); 4. Select Save. -The remaining files cannot be reverse engineered to retrieve the full document text - however, do +The other index files cannot be reverse engineered to retrieve the full document text - however, do contain the weightings and terms within the text. We recommend restricting access to all files at the file system level as well as considering file system encryption. diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md b/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md index 59f0f7129f..0d165b8985 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md @@ -51,7 +51,7 @@ If these lines are present then users will be required to login using their Wind ## Configure Microsoft Entra ID Authentication -To configure Microsoft Entra ID you need to create aclient application and add two new appSettings +To configure Microsoft Entra ID you need to create a client application and add two new appSettings to the "``" section of the web.config file in the QS directory: - `` @@ -76,8 +76,7 @@ Classification via Microsoft Entra ID authentication: ## Add or Remove Users -More users can be added at any time from the default Users screen, as well as allowing for users to -be removed. +Users can be added and removed via the Users screen at any time. ![adduser](/images/dataclassification/5.7/security/adduser.webp) @@ -94,11 +93,9 @@ be found at: /conceptQS/\_api ## Permission Management -In order to allocate granular permissions to a user (non-Super Users), simply select their username -from the main grid. - -Each tab contains a top level checkbox (“Allow Access”) which defines whether or not a user has -access to each of the top level administrative areas. +In order to allocate granular permissions to a user (non-Super Users), click Edit on their row in the Users table. The +permissions for each section of the administrative web interface will be displayed as tabs. Each tab contains a top level +checkbox ("Access [Section Name]”) which defines whether or not a user has access to each of the top level administrative areas. When an area is enabled there are typically more granular permissions that can be enabled, such as: @@ -110,9 +107,9 @@ When an area is enabled there are typically more granular permissions that can b ![userpermissions_thumb_0_0](/images/dataclassification/5.7/security/userpermissions_thumb_0_0.webp) -### Taxonomy Permissions Summary +### Permissions Summary -The Permissions window lets you restruct permissions for a user. +The Permissions window lets you set permissions for the selected user. ![viewtaxonomypermissionssummary_thumb_0_0](/images/dataclassification/5.7/security/viewtaxonomypermissionssummary_thumb_0_0.webp) @@ -131,7 +128,7 @@ You can restrict permissions for a user to the following areas: ## Super Users -Super Users always have access to all Query Server administrative functions. +Super Users have access to all Query Server administrative functions. Non-Super Users must have their access rights specifically configured and all rights are disabled by default. See User Management section for details about configuring the access rights for non-Super From 4957e7380b6117eaf6e2cb39109b86171d6b79d4 Mon Sep 17 00:00:00 2001 From: Ben Hayman Date: Fri, 27 Feb 2026 16:29:18 +0000 Subject: [PATCH 02/20] Missed unsaved improvement --- .../configuration/coreconfiguration/classifier/engineoptions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/engineoptions.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/engineoptions.md index cd7501f317..077ef0d5ee 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/engineoptions.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/engineoptions.md @@ -9,7 +9,7 @@ sidebar_position: 40 By default, only basic options are displayed. To view advanced options, click the "wrench" icon at **Settings** in the bottom-right corner. -Each option has an associated “**i**” which describes the nature of the setting. +Each option has an associated information popup (the “**i**” symbol next to the option name) which describes what the setting does and how it works. ![core_thumb_0_0](/images/dataclassification/5.7/configuration/core_thumb_0_0.webp) From 873c5dc640cc70b19627d0d5bf18014a15faba22 Mon Sep 17 00:00:00 2001 From: Ben Hayman Date: Fri, 27 Feb 2026 17:30:07 +0000 Subject: [PATCH 03/20] Added documentation for auto-expunging --- docs/dataclassification/5.7/dashboards.md | 4 ++++ .../configuration/coreconfiguration/administration.md | 1 + 2 files changed, 5 insertions(+) diff --git a/docs/dataclassification/5.7/dashboards.md b/docs/dataclassification/5.7/dashboards.md index a14e56faac..1994e26942 100644 --- a/docs/dataclassification/5.7/dashboards.md +++ b/docs/dataclassification/5.7/dashboards.md @@ -40,6 +40,10 @@ following meanings: - Deleted Automatically—Items that have been detected as removed from the source system - Deleted Manually—Items removed manually by an end-user via the administration console +:::note +A deleted document is not immediately removed from NDC in case it was incorrectly deleted. Users must click the Expunge option on Deleted Automatically and Deleted Manually to fully remove those documents from the system. Automatic expunging can be enabled via the [Administration configuration settings](/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md). +::: + ![dashboard_thumb_0_0](/images/dataclassification/5.7/admin/reporting/dashboard_thumb_0_0.webp) ## System Health diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md index 9c7d5f8c3b..44c3687e39 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md @@ -21,6 +21,7 @@ Most options have an associated information popup (the “**i**” symbol next t | **General settings** | | | | Report Source Filter Mode | Use to add an additional filter for either Source Groups (default) or Source(s) | | | Disable Security Trimming | Select this option if you want to ensure that search results retrieved by API or the Taxonomies area will be unfiltered (ignoring the user name of the administrative user). | Disables the application of security trimming from search results (taxonomy browse/search). | +| Auto-Expunge Deleted Pages | When this is enabled, deleted documents will be automatically expunged 7 days after the last collection attempt. | Note that documents that are deleted manually or by the source file watchers may be deleted in fewer than 7 days depending on the last collection date. | | **Advanced settings** | | | | Instance name | Name of the NDC Server instance | | | Administration URL | URL of the web-based management console. Default URL is _http://localhost/conceptQS_. | If necessary, specify another Netwrix standalone server or cluster server instead of local host. You can use server name or IP address. | From 8278c400e5f81088da5807325ed15cf2e06d3983 Mon Sep 17 00:00:00 2001 From: Ben Hayman Date: Mon, 2 Mar 2026 14:05:00 +0000 Subject: [PATCH 04/20] Minor DQS-related adjustments --- docs/dataclassification/5.7/index.md | 2 +- .../deployment/ndcserverandclient/dqsmode.md | 40 ++++++++----------- .../classifier/engineoptions.md | 2 +- 3 files changed, 19 insertions(+), 25 deletions(-) diff --git a/docs/dataclassification/5.7/index.md b/docs/dataclassification/5.7/index.md index 38e4c27605..73efe24b28 100644 --- a/docs/dataclassification/5.7/index.md +++ b/docs/dataclassification/5.7/index.md @@ -120,7 +120,7 @@ Database such as: the document title, body text, etc. However, this information using a primary key and so is very efficient. The hitlist itself is always constructed and ranked using information contained in the proprietary conceptDatabase. -The current release of Netwrix Data Classification supports SQL Server 2008 R2 or later version. +The current release of Netwrix Data Classification supports SQL Server 2008 R2 or later. ## NDC Index diff --git a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md index 2b34393169..77f1fe540a 100644 --- a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md +++ b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Configuring an NDC Server Cluster and Load Balancing with DQS Mode The Distributed Query Server (DQS) mode allows you to balance the processing load of data collection, -indexing and classification over multiple Netwrix Data Classification Servers (NDC Servers) with a single shared database. +indexing and classification over multiple NDC Servers with a single shared database. This approach is strongly recommended if you need to process large data volumes, for example: - File Servers — recommended if processing over 16m objects, @@ -24,18 +24,18 @@ search results, each NDC Server will automatically communicate with the other cl All NDC Servers in the cluster will share a single NDC SQL database. ::: -This functionality is implemented through the _Query Server_ functionality of NDC Server. +This functionality is implemented through the _Query Server_ application. ## Configuring DQS Mode DQS mode is configured via the administrative web console and, from version 5.7.10 onwards, the installer. -If you want to implement DQS configuration for your NDC deployment, consider the following: +If you want to implement DQS configuration for your NDC deployment, bear in mind that doing so +cannot easily be undone. Netwrix recommends that before applying the DQS mode, a full backup of the current +NDC deployment should be created. Also, read the DQS documentation sections thoroughly before you start. -- This action cannot easily be undone so, before applying the DQS mode, take a full backup of your - NDC deployment. Also, read the DQS documentation sections thoroughly before you start. -- Make sure all servers you plan to add to the DQS cluster have a network connection and are - visible to each other across the network. Adjust your firewall settings if necessary. +Make sure all servers you plan to add to the DQS cluster have a network connection and are +visible to each other across the network. Adjust your firewall settings if necessary. DQS mode can only be configured by a user whose account has the **Superuser** role. @@ -53,7 +53,7 @@ DQS mode can only be configured by a user whose account has the **Superuser** ro 4. Select Enable DQS. -5. On the DQS tab, click Add to adopen the DQS addition menu, and input the details for the first additional NDC server. +5. On the DQS tab, click Add to open the DQS addition menu, and input the details for the first additional NDC server. ![dqs_mode_page_thumb_0_0](/images/dataclassification/5.7/requirements/dqs_mode_page_thumb_0_0.webp) @@ -62,7 +62,7 @@ DQS mode can only be configured by a user whose account has the **Superuser** ro | Setting | Value | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | Server | The NDC Server name or IP address (name format is case-insensitive). | - | QS Path | The path to the solution component responsible for DQS mode, residing on the server being added. This is filled in automatically when filling in the server name; leave the default value. | | + | QS Path | The path to the NDC QS process on the server being added. This is filled in automatically when filling in the server name; leave the default value. | | | Alternate Server | Optional, Netwrix recommends using default values. | | Alternate QS Path | Optional, Netwrix recommends using default values. | @@ -74,17 +74,11 @@ DQS mode can only be configured by a user whose account has the **Superuser** ro 8. On each server, follow the installation steps as described in the [Install Netwrix Data Classification](/docs/dataclassification/5.7/introduction/install/overview.md) section up to the SQL Database configuration step. -9. On the SQL Database step, provide the name of the SQL Server instance that hosts NDC SQL database - you configured for the first NDC Server. - -:::note -Ignore the confirmation dialog informing you of the existing schema in the selected SQL database. -::: - - +9. On the SQL Database step, provide connection details for the SQL Server instance that hosts the NDC SQL database + you configured for the first NDC Server. A popup will inform you that an existing NDC schema exists in the database, ignore this and continue. 10. Complete the installation. 11. Repeat steps 2 - 6 for every NDC Server, then review the list of servers to make sure the new - server was included. + server has been added. ![dqs_servers_list_thumb_0_0](/images/dataclassification/5.7/requirements/dqs_servers_list_thumb_0_0.webp) @@ -108,13 +102,13 @@ Ignore the confirmation dialog informing you of the existing schema in the selec :::note When upgrading an existing NDC instance the installer will attempt to resynchronise the DQS instances in the - background and, if successful, will skip the DQS Synchronisation step. You can then skip ahead to step 13. The DQS Synchronisation - step will only display for an upgrade if this process fails - this is not an issue, simply follow the steps below - to resynchronise the NDC instance with the primary NDC server. + background and, if successful, will skip the DQS Synchronisation step. You can then skip ahead in these instructions + to step 13. The DQS Synchronisation step will only display for an upgrade if this process fails - this is not an issue, + simply follow the steps below to resynchronise the NDC instance with the primary NDC server. ::: 9. The Primary NDC Server Url field should have the server url of the primary NDC server (i.e. the first row in the DQS table) - automatically inserted. If it is not present or is incorrect, enter the address from the QS Path column of the first row of + automatically inserted. If it is not present or is incorrect, enter the address from the QS Path column of the corresponding row of the DQS table. Then click Connect to connect the installer to that server. 10. Once the installer has successfully connected to the primary NDC server, it will generate an authentication code and display it in the Authentication Code field. Click Sync to open the NDC DQS settings page in a web browser. @@ -138,7 +132,7 @@ Ignore the confirmation dialog informing you of the existing schema in the selec If you were configuring the DQS mode for an existing NDC deployment, you will be prompted to re-collect data from the data sources in order to re-distribute the content index across all - NDC Servers in the cluster. This will result in all data sources being recollected, which may + NDC Servers in the cluster. **This will result in all data sources being recollected**, which may take a significant amount of time. :::note diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/engineoptions.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/engineoptions.md index 077ef0d5ee..d393b90f2d 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/engineoptions.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/engineoptions.md @@ -26,7 +26,7 @@ has an indication of the values that have been changed from the default setting. | Boosted Regex Scoring | Automatically boosts the score of Regex clues when the regular expression matches multiple occurrences in the same document. | Selecting this option is not recommended when using the Netwrix compliance taxonomies. | | Case-insensitive Regex Processing | Processes any regex or metadata regex rules in a case-insensitive manner. | | | **Advanced settings** | | | -| Redis Caching | Use _redis_ module to enable Classifier data caching between the core Windows services and NDC Servers. | This module can be downloaded from [https://github/MicrosoftArchive/redis/releases.](https://github/MicrosoftArchive/redis/releases) Install it locally and open port **6379** required for its operation. For details on servers cluster, see [Configuring NDC Servers Cluster and Load Balancing with DQS Mode](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md) | +| Redis Caching | Use _redis_ module to enable Classifier data caching between the core Windows services and NDC Servers. | This module can be downloaded from [https://github/MicrosoftArchive/redis/releases.](https://github/MicrosoftArchive/redis/releases) Install it locally and open port **6379** required for its operation. For details on server clusters, see [Configuring NDC Servers Cluster and Load Balancing with DQS Mode](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md) | | Store Trimmed Classification | Enables storing trimmed classifications in SQL (due to max category settings at the global or subset level). | When enabled, classification performance will be improved —however, this will result in additional data within the SQL database. | | Enable Standard Clue Metadata Matching | By default, standard clues are matched against the extracted text, index text, summary, and title. Use this option if you want to match standard clues also on values found in the document's metadata. | To ensure accurate classification results, we recommend running an index rebuild operation after enabling this mode (use Run Cleaner button). | | Disable Unclassified Regex Extraction | By default, any regular expression clue will result in additional metadata being added to a document, based on the extracted value(s). Use this option if you want to only extract values for clues on nodes that have achieved their threshold for classification. | | From 2ac72ea5a13fb443c51da3e7fcf3b9331fb5dca7 Mon Sep 17 00:00:00 2001 From: Ben Hayman Date: Mon, 2 Mar 2026 15:09:45 +0000 Subject: [PATCH 05/20] Created an initial encryption key recovery article --- ...recoveringencryptionkeyindqsenvironment.md | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/recoveringencryptionkeyindqsenvironment.md diff --git a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/recoveringencryptionkeyindqsenvironment.md b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/recoveringencryptionkeyindqsenvironment.md new file mode 100644 index 0000000000..aa873d2cdb --- /dev/null +++ b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/recoveringencryptionkeyindqsenvironment.md @@ -0,0 +1,28 @@ +--- +title: "Recovering the Encryption Key in secondary NDC instances" +description: "Recovering the NDC encryption key in a distributed environment" +sidebar_position: 10 +--- + +# Recovering the Encryption Key in Secondary NDC Instances + +:::note +This article applies to version 5.7.10 and later. +::: + +In a distributed NDC environment, if the encryption key has been removed from the registry on a secondary instance, the key can be recovered by retrieving it from the primary instance and storing it securely on the secondary instance. + +When this occurs, a health error will be displayed on the NDC stats screen and the services will halt. + +The primary instance will self-recover on startup of the collector, so long as the encryption key is stored in the database. If the database key is also no longer present but the key still exists on at least one secondary instance, the services on the primary instance will halt. If this occurs, contact Netwrix support for remediation. + +## Recovering the Encryption Key + +To recover the encryption key on a secondary instance: + +1. Stop all services on the secondary instance. +2. Start the NDC installer and select **Repair**. +3. Run through to the DQS sync step. +4. Follow the instructions listed in [Configuring an NDC Server Cluster and Load Balancing with DQS Mode](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md). + +Once all steps have been performed, the key will be restored to the secondary instance. Start the services again and they should load the key and function correctly. From a18e7213ae61cadfe0796ba9f128221668436556 Mon Sep 17 00:00:00 2001 From: Ben Hayman Date: Mon, 2 Mar 2026 16:30:54 +0000 Subject: [PATCH 06/20] Updated SQL Server source documentation --- .../addsource/addsqlserversource/mssqlserver.md | 7 ++++--- .../addsource/addsqlserversource/mysqlserver.md | 2 +- .../addsource/addsqlserversource/postgresqlserver.md | 6 ++---- 3 files changed, 7 insertions(+), 8 deletions(-) diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mssqlserver.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mssqlserver.md index c3fbd14d7b..5f8f82d272 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mssqlserver.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mssqlserver.md @@ -13,12 +13,13 @@ To connect to a MS SQL server: 1. On the **Source Configuration** screen, select **MS SQL**. 2. Specify MS SQL server. - - ![sqlserver_source3](/images/dataclassification/5.7/admin/sources/sqlserver/sqlserver_source3.webp) - 3. Specify Authentication method: - Integrated - SQL - specify username and password of the MS SQL server. + + + ![sqlserver_source3](/images/dataclassification/5.7/admin/sources/sqlserver/sqlserver_source3.webp) + 4. Select Save. diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md index 52956c6d1d..550343b93f 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md @@ -12,7 +12,7 @@ information, go to the main article[SQL Server ](/docs/dataclassification/5.7/co To connect to a MySQL server: 1. On the **Source Configuration** screen, select **MS SQL**. -2. Specify MySQL server. +2. Specify MySQL server, username, and password. ![sqlserver_source3](/images/dataclassification/5.7/admin/sources/sqlserver/sqlserver_source3.webp) diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md index f1d3d1f64b..8e8fa8c31e 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md @@ -12,10 +12,8 @@ information, go to the main article[SQL Server ](/docs/dataclassification/5.7/co To connect to a PostgreSQL server: 1. On the **Source Configuration** screen, select **SQL Server**. -2. Specify PostgreSQL server. +2. Specify the address of the PostgreSQL server, the Master Database name, username, and password. ![sqlserver_source3](/images/dataclassification/5.7/admin/sources/sqlserver/sqlserver_source3.webp) -3. Insert the Master Database name. - -4. Select Save. +3. Select Save. From d011afeb4ecd3423b60c263f8f26a3cc8f81196e Mon Sep 17 00:00:00 2001 From: Ben Hayman Date: Thu, 5 Mar 2026 09:59:51 +0000 Subject: [PATCH 07/20] Adjusted wording of Show Movements documentation --- .../taxonomies/clues/browse.md | 12 +++++++++++- .../taxonomies/clues/search.md | 2 +- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/browse.md b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/browse.md index 76ccad8d15..2f1bfd89af 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/browse.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/browse.md @@ -12,7 +12,11 @@ documents achieving the minimum score set for classification in the term. :::note This list will include the current classification status of each document and any changes -made to the class, since the last classification, are not taken into account. +made to the class since the last time each document was classified are not taken into account. + +To see how the classification of each document would change based on the current configuration +of the class, tick the Show Movements checkbox. When selected, any change in scoring of each +document since the last time that document was classified will be shown. ::: @@ -38,6 +42,12 @@ You can use the Browse function to: ![browsetab_thumb_0_0](/images/dataclassification/5.7/admin/reporting/browsetab_thumb_0_0.webp) +:::note +By default, results from sources that have not been indexed are not included in the Browse results. +To include these results, tick the Show Unindexed Documents checkbox. +::: + + To restrict the browsing scope, you can either add a URL filter, or add a custom filter, as well as select to show document movements. These options are configured in the same way as for [Search Documents by Clue](/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/search.md). diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/search.md b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/search.md index 4d77651aa6..0dbe02ba4c 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/search.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/search.md @@ -35,7 +35,7 @@ tab and configure search settings. 3. To view how recent changes to the term will affect the document classifications, select Show - document movements. As a result, the “movement” of the document since the last classification + document movements. When selected, any change in scoring of each document since the last time that document was classified will be shown. Possible scenarios are: ![movementskey](/images/dataclassification/5.7/admin/taxonomies/movementskey.webp) From c42257bc4c7efe250d0a9a86cc69d61702f9a910 Mon Sep 17 00:00:00 2001 From: Ben Hayman Date: Mon, 1 Jun 2026 18:25:38 +0100 Subject: [PATCH 08/20] Suggested doc changes --- .../introduction/addsource/adddropbox.md | 2 +- .../addsingledatabase/addsingledatabase.md | 2 +- .../introduction/addsource/addsource.md | 4 +-- .../addsqlserversource/mysqlserver.md | 6 ++-- .../addsqlserversource/postgresqlserver.md | 6 ++-- .../introduction/manage/managefilesystem.md | 2 +- .../taxonomies/builtintaxonomies.md | 2 +- .../taxonomies/clues/browse.md | 6 ++-- docs/dataclassification/5.7/dashboards.md | 8 ++--- docs/dataclassification/5.7/index.md | 4 +-- .../deployment/clouddeployment.md | 2 +- .../deployment/ndcserverandclient/dqsmode.md | 32 +++++++++---------- .../ndcserverandclient/ndcserverandclient.md | 2 +- ...recoveringencryptionkeyindqsenvironment.md | 8 +++-- .../initialconfiguration/healthalert.md | 3 +- .../processingsettings.md | 2 +- .../initialconfiguration/security.md | 6 ++-- .../introduction/install/ndcsqldatabase.md | 2 +- .../5.7/introduction/install/overview.md | 12 +++---- .../requirements/hardwarerequirements.md | 2 +- .../5.7/introduction/upgrade.md | 12 ++++--- .../configuration/communicationsettings.md | 2 +- .../coreconfiguration/administration.md | 2 +- .../configuration/coreconfiguration/system.md | 4 +-- .../configuration/texthandling.md | 4 +-- .../users/securendc.md | 2 +- .../users/usermanagement.md | 8 ++--- 27 files changed, 75 insertions(+), 72 deletions(-) diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md index 8a2a9496c5..d6a13e52e7 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md @@ -22,6 +22,6 @@ Complete the following fields: | App secret | Generated automatically as you create your Dropbox app. Click Show in the Dropbox app to view the value. | | Authorization code | Select Generate and copy the code from your app. | | Access Shared Team Folder as | If you have team folders in your Dropbox namespace and you want to crawl one or more of these folders with Netwrix Data Classification, provide the email address of an account that has access to the desired team folders. For personal folders, this option is not required. For more information, refer to Dropbox [Namespace guide](https://www.dropbox.com/developers/reference/namespace-guide). | -| OCR Processing mode | Select document images processing mode:
  • Disabled – document images will not be processed.
  • Default – defaults to the source settings (if configuring a path) or the global setting (if configuring a source).
  • Normal – images are processed with normal quality settings.
  • Enhanced – upscale images further to increase detail and accuracy of results.
| +| OCR Processing mode | Select document images processing mode:
  • Disabled – document images will not be processed.
  • Default – defaults to the source settings if configuring a path, or the global setting if configuring a source.
  • Normal – images are processed with normal quality settings.
  • Enhanced – upscale images further to increase detail and accuracy of results.
| | Source Group | Netwrix recommends creating a dedicated source group for Dropbox. If none exists, a source group named Dropbox Sources will be created automatically. | | Pause source on creation | Select if you want to make other configuration changes before collection of the source occurs. | diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md index 532d179b1c..7a2736d4a3 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md @@ -31,7 +31,7 @@ Complete the following fields: | Connection Type | Select your connection type: MS SQL, MySQL, PostgreSQL, or Oracle. | | Server | Specify the server name of the database system to be crawled ("." can be used to indicate the local server). | | Database Name | Specify the name of the database that will be crawled. It is possible to configure multiple databases from the same server. | -| Authentication Method | Select authentication method: **Integrated** or **SQL**.
  • With **Integrated** option selected, database will be accessed via the NDC Service Accounts.
  • With **SQL** option selected, you specify the user name and password to be used when accessing the database.
| +| Authentication Method | Select authentication method: **Integrated** or **SQL**.
  • With **Integrated** option selected, database will be accessed via the NDC Service Account (the account the collector is configured to run as).
  • With **SQL** option selected, you specify the user name and password to be used when accessing the database.
| | OCR Processing Mode | Select processing mode for images in the documents:
  • Disabled – document images will not be processed.
  • Default – defaults to the source settings if configuring a path or the global setting if configured on a source.
  • Normal – images are processed with normal quality settings.
  • Enhanced – upscale images further to allow more accurate results. This will provide better accuracy but can lead to longer processing time if the images do not contain text.
| | Source Group | If you want to add the database source to a source group, select an existing source group or create a new one. | | Pause source on creation | Pauses the source upon creation, to allow for further configuration before collection begins. | diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsource.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsource.md index b8543b1db6..3bccb6fdc1 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsource.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsource.md @@ -20,8 +20,8 @@ Follow the steps to add a content source. the sources: - [Box](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addbox.md) -- [Add Single Database](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md) (Microsoft SQL Server, MySQL, PostgreSQL or Oracle database) -- [Add Database Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md) (Microsoft SQL Server, MySQL, PostgreSQL or Oracle databases on a server) +- [Add Single Database](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md) (Microsoft SQL Server, MySQL, PostgreSQL, or Oracle database) +- [Add Database Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md) (All Microsoft SQL Server, MySQL, PostgreSQL, or Oracle databases on a server) - [Dropbox](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md) - [Exchange Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangeserver.md) or [Exchange Mailbox](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/exchangemailbox.md) diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md index 550343b93f..a46ed94f02 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md @@ -6,12 +6,12 @@ sidebar_position: 30 # Add MySQL Server -Once you choose to add SQL server source, you opt to add MySQL server as a source. For more -information, go to the main article[SQL Server ](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md). +When adding a SQL server source, you can choose to add a MySQL server as the source. For more +information, see [SQL Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md). To connect to a MySQL server: -1. On the **Source Configuration** screen, select **MS SQL**. +1. On the **Source Configuration** screen, select **SQL Server**. 2. Specify MySQL server, username, and password. ![sqlserver_source3](/images/dataclassification/5.7/admin/sources/sqlserver/sqlserver_source3.webp) diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md index 8e8fa8c31e..3f3582a260 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md @@ -6,13 +6,13 @@ sidebar_position: 40 # Add PostgreSQL Server -Once you choose to add SQL server source, you opt to add PostgreSQL server as a source. For more -information, go to the main article[SQL Server ](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md). +When adding a SQL server source, you can choose to add a PostgreSQL server as a source. For more +information, see [SQL Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md). To connect to a PostgreSQL server: 1. On the **Source Configuration** screen, select **SQL Server**. -2. Specify the address of the PostgreSQL server, the Master Database name, username, and password. +2. Specify the address of the PostgreSQL server, the Master Database name (commonly `postgres`), username, and password. ![sqlserver_source3](/images/dataclassification/5.7/admin/sources/sqlserver/sqlserver_source3.webp) diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/manage/managefilesystem.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/manage/managefilesystem.md index 124bc4bfa5..6496e80b43 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/manage/managefilesystem.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/manage/managefilesystem.md @@ -87,7 +87,7 @@ To specify inclusions, do the following: **Add**. Two wildcards are supported: -- \* - matches to one or more instances of any character +- \* - matches one or more instances of any character - . - explicitly includes files with no extension diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/builtintaxonomies.md b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/builtintaxonomies.md index 42f5330f79..37bd108f18 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/builtintaxonomies.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/builtintaxonomies.md @@ -175,7 +175,7 @@ consumers and businesses. ## Sensitive and Non-Sensitive Taxonomies While creating your own reports, you can specify whether a taxonomy is sensitive (e.g. financial details, -сredentials) or non-sensitive (e.g. file size, language). +credentials) or non-sensitive (e.g. file size, language). :::note This applies only to customized taxonomies, which you add by yourself. You cannot change diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/browse.md b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/browse.md index 2f1bfd89af..d2e7a4f20e 100644 --- a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/browse.md +++ b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/browse.md @@ -11,8 +11,8 @@ documents achieving the minimum score set for classification in the term. [See Classification Rules (Clues) for more information.](/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/clues.md) :::note -This list will include the current classification status of each document and any changes -made to the class since the last time each document was classified are not taken into account. +This list will include the current classification status of each document. Any changes +made to the classification clues since the last time each document was classified are not taken into account. To see how the classification of each document would change based on the current configuration of the class, tick the Show Movements checkbox. When selected, any change in scoring of each @@ -44,7 +44,7 @@ You can use the Browse function to: :::note By default, results from sources that have not been indexed are not included in the Browse results. -To include these results, tick the Show Unindexed Documents checkbox. +To include these results, select the Show Unindexed Documents checkbox. ::: diff --git a/docs/dataclassification/5.7/dashboards.md b/docs/dataclassification/5.7/dashboards.md index 1994e26942..b59873cf46 100644 --- a/docs/dataclassification/5.7/dashboards.md +++ b/docs/dataclassification/5.7/dashboards.md @@ -13,14 +13,14 @@ The Dashboard administration area provides a selection of tools to review applic The default screen shows a high-level overview of Netwrix Data Classification statistics, displaying the last active times of each service (with inactive services shown in red). Select the "i" icon next to each date to view the name of the active server as well as batch processing statistics. -If you have the Distributed Query Server functionality enabled, any instances that are missing their +If you have the Distributed Query Server functionality enabled, any instances that are missing their encryption key will also be displayed. You will also be able to view the average processing throughput. The following statistics are available for each thread type: - Processing Time—The weighted average time for each thread (total batch time / number of documents processed) -- Real Execution Time—The actual execution time of each thread (average of each threads' run time) +- Real Execution Time—The actual execution time of each thread (an average of each thread's run time) Statistics shown on the Dashboard screen are cached and updated regularly by the Collector service. If the values are not being updated please ensure that the Collector service is running. @@ -36,12 +36,12 @@ following meanings: typically mean that the full text for the affected documents will not be available - Collection Exclusions—Items that have been excluded due to a configured Collection Exclusion - Files Skipped—File share items that have been ignored due to the "Files Included" or "Files - Excluded" configuration (Sources → File) + Excluded" configuration - Deleted Automatically—Items that have been detected as removed from the source system - Deleted Manually—Items removed manually by an end-user via the administration console :::note -A deleted document is not immediately removed from NDC in case it was incorrectly deleted. Users must click the Expunge option on Deleted Automatically and Deleted Manually to fully remove those documents from the system. Automatic expunging can be enabled via the [Administration configuration settings](/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md). +Deleted documents are retained as a safeguard against accidental deletion. Users must click the Expunge option on Deleted Automatically and Deleted Manually to fully remove those documents from the system. Automatic expunging can be enabled via the [Administration configuration settings](/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md). ::: ![dashboard_thumb_0_0](/images/dataclassification/5.7/admin/reporting/dashboard_thumb_0_0.webp) diff --git a/docs/dataclassification/5.7/index.md b/docs/dataclassification/5.7/index.md index 73efe24b28..736e114993 100644 --- a/docs/dataclassification/5.7/index.md +++ b/docs/dataclassification/5.7/index.md @@ -81,7 +81,7 @@ The NDC Collector is implemented as a Microsoft Windows Service. ## Indexer -The Indexer takes each new document collected by the conceptCollector and indexes terms from +The Indexer takes each new document collected by the NDC Collector and indexes terms from the extracted text within the NDC Index. The index can be read from concurrently with the indexing process. However, significant indexing @@ -134,7 +134,7 @@ are collected. ## Classifier -The Classifier is used to classify documents after they have been indexed. It can make use of the built-in +The Classifier classifies collected documents against NDC taxonomies. It can make use of the built-in taxonomies and any custom taxonomies created by the user, and can be linked to SharePoint termsets to classify against them as well. It also runs user-configured workflows against any documents that meet the conditions of the workflow, and is used to perform Data Subject Access Requests. diff --git a/docs/dataclassification/5.7/introduction/deployment/clouddeployment.md b/docs/dataclassification/5.7/introduction/deployment/clouddeployment.md index 322ec2b90e..1038e3d736 100644 --- a/docs/dataclassification/5.7/introduction/deployment/clouddeployment.md +++ b/docs/dataclassification/5.7/introduction/deployment/clouddeployment.md @@ -25,7 +25,7 @@ It is recommended to create the NDC SQL database on a dedicated SQL Server inst Therefore, SQL Server Express edition is only suitable for evaluation and PoC environments (processing up to 1,000,000 documents). - **TIP:** Netwrix strongly recommends using SSD storage for both of the database and Netwrix Data Classification + **TIP:** Netwrix strongly recommends using SSD storage for both the database and Netwrix Data Classification servers. - If configuring database settings via SQL Server Management Studio, you will need to set diff --git a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md index 77f1fe540a..018e3bdda5 100644 --- a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md +++ b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md @@ -10,10 +10,10 @@ The Distributed Query Server (DQS) mode allows you to balance the processing loa indexing and classification over multiple NDC Servers with a single shared database. This approach is strongly recommended if you need to process large data volumes, for example: -- File Servers — recommended if processing over 16m objects, -supports up to 64 m objects per cluster of 4 servers. +- File Servers — Recommended if processing over 16m objects, +supports up to 64m objects per cluster of 4 servers. - SharePoint — Recommended if processing over 8m objects, -supports up to 32 m objects per cluster of 4 servers. +supports up to 32m objects per cluster of 4 servers. To make use of Distributed Query Server mode, you need to arrange your NDC Servers in a 'cluster' for load distribution as described below. Each clustered NDC Server will store its own set of .CSE index files, @@ -100,12 +100,12 @@ DQS mode can only be configured by a user whose account has the **Superuser** ro 8. When you click next, a message box should appear stating that an NDC configuration was detected and that the new install will be added to the existing DQS environment - click OK. - :::note - When upgrading an existing NDC instance the installer will attempt to resynchronise the DQS instances in the - background and, if successful, will skip the DQS Synchronisation step. You can then skip ahead in these instructions - to step 13. The DQS Synchronisation step will only display for an upgrade if this process fails - this is not an issue, - simply follow the steps below to resynchronise the NDC instance with the primary NDC server. - ::: +:::note +When upgrading an existing NDC instance the installer will attempt to resynchronise the DQS instances in the +background and, if successful, will skip the DQS Synchronisation step. You can then skip ahead in these instructions +to step 13. The DQS Synchronisation step will only display for an upgrade if this process fails - this is not an issue, +simply follow the steps below to resynchronise the NDC instance with the primary NDC server. +::: 9. The Primary NDC Server Url field should have the server url of the primary NDC server (i.e. the first row in the DQS table) automatically inserted. If it is not present or is incorrect, enter the address from the QS Path column of the corresponding row of @@ -115,10 +115,10 @@ DQS mode can only be configured by a user whose account has the **Superuser** ro 11. On the web page, click on Register/Resync. This will open the authentication code entry tab - the authentication code generated by the installer should be present in the input field. Click Submit to submit the authentication code. - :::note - If the authentication code is not autofilled, click on the Authentication Code field in the installer to copy the - value to your clipboard, then paste it in the authentication code field in the NDC UI. - ::: +:::note +If the authentication code is not autofilled, click on the Authentication Code field in the installer to copy the +value to your clipboard, then paste it in the authentication code field in the NDC UI. +::: 12. The Register/Resync tab should now display an 8-digit verification code. Copy this, paste it into the Verification Code field in the installer, then click Join. The NDC installer will then perform @@ -131,9 +131,9 @@ DQS mode can only be configured by a user whose account has the **Superuser** ro If you were configuring the DQS mode for an existing NDC deployment, you will be prompted to - re-collect data from the data sources in order to re-distribute the content index across all - NDC Servers in the cluster. **This will result in all data sources being recollected**, which may - take a significant amount of time. +re-collect data from the data sources in order to re-distribute the content index across all +NDC Servers in the cluster. **This will result in all data sources being recollected**, which may +take a significant amount of time. :::note To force re-distribution when necessary, you can use the Re-Collect command available diff --git a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/ndcserverandclient.md b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/ndcserverandclient.md index 3ee9d57fb9..c7e12f3a35 100644 --- a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/ndcserverandclient.md +++ b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/ndcserverandclient.md @@ -29,7 +29,7 @@ Remember that for production environments, your NDC Server and database server m [Requirements to Install Netwrix Data Classification](/docs/dataclassification/5.7/introduction/requirements/overview.md). The virtual appliance configuration is insufficient for production and is not recommended for that purpose. -To balance processing load while collecting indexing and classifying data in large-size and extra-large +To balance processing load while collecting/indexing/classifying data in large-size and extra-large environments (i.e. 16m+ objects to process), it is strongly recommended to deploy multiple NDC Servers and configure them as a **Distributed Query Server**. [See Configuring NDC Servers Cluster and Load Balancing with DQS Mode for more information.](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md) diff --git a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/recoveringencryptionkeyindqsenvironment.md b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/recoveringencryptionkeyindqsenvironment.md index aa873d2cdb..35001de9d6 100644 --- a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/recoveringencryptionkeyindqsenvironment.md +++ b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/recoveringencryptionkeyindqsenvironment.md @@ -1,5 +1,5 @@ --- -title: "Recovering the Encryption Key in secondary NDC instances" +title: "Recovering the Encryption Key in Secondary NDC Instances" description: "Recovering the NDC encryption key in a distributed environment" sidebar_position: 10 --- @@ -7,14 +7,16 @@ sidebar_position: 10 # Recovering the Encryption Key in Secondary NDC Instances :::note -This article applies to version 5.7.10 and later. +This article applies to version 5.7.11 and later. ::: In a distributed NDC environment, if the encryption key has been removed from the registry on a secondary instance, the key can be recovered by retrieving it from the primary instance and storing it securely on the secondary instance. When this occurs, a health error will be displayed on the NDC stats screen and the services will halt. -The primary instance will self-recover on startup of the collector, so long as the encryption key is stored in the database. If the database key is also no longer present but the key still exists on at least one secondary instance, the services on the primary instance will halt. If this occurs, contact Netwrix support for remediation. +The primary instance will self-recover on startup of the collector, so long as the encryption key is stored in the database. + +If the database key is also no longer present but the key still exists on at least one secondary instance, the services on the primary instance will halt. If this occurs, contact Netwrix support for remediation. ## Recovering the Encryption Key diff --git a/docs/dataclassification/5.7/introduction/initialconfiguration/healthalert.md b/docs/dataclassification/5.7/introduction/initialconfiguration/healthalert.md index e7e0b382ad..19c8babca5 100644 --- a/docs/dataclassification/5.7/introduction/initialconfiguration/healthalert.md +++ b/docs/dataclassification/5.7/introduction/initialconfiguration/healthalert.md @@ -16,7 +16,6 @@ Complete the following fields: | Setting | Description | | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Would you like to configure Health Reporting? | Select Setup now if you want to receive health alerts. You can do it later in the communication settings area. [See System Health for more information.](/docs/dataclassification/5.7/dashboards.md) | -| Who should the email be sent from? | Select a user registered in Netwrix Data Classification administrative web console in the field or go to the Specific recipients below and specify one or more email addresses outside your organization. | +| Who should the email be sent from? | Select a user registered in the Netwrix Data Classification administrative web console. Alternatively, use Specific recipients to add one or more external email addresses. | | What sort of immediate alerts should be sent? | Select the appropriate alert level for the emails you wish to receive: do not receive any alerts at all, only receive alerts for errors, or get emails for both errors and warnings. [See System Health for more information.](/docs/dataclassification/5.7/dashboards.md) | | Should a daily health summary be sent? | Select whether you want to receive daily summary on the current health status of NDC. | - | diff --git a/docs/dataclassification/5.7/introduction/initialconfiguration/processingsettings.md b/docs/dataclassification/5.7/introduction/initialconfiguration/processingsettings.md index c574ace2e5..79d4341c8b 100644 --- a/docs/dataclassification/5.7/introduction/initialconfiguration/processingsettings.md +++ b/docs/dataclassification/5.7/introduction/initialconfiguration/processingsettings.md @@ -16,7 +16,7 @@ Review the following for additional information: | ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Text Extraction | | | Should OCR be used on image files? | Optical Characters Recognition is a technology used to extract text from images. Enable OCR if the content being collected contains a large number of scanned documents (for example). Performing OCR on documents can significantly reduce indexing performance. **IMPORTANT!** OCR requires the Visual C++ Redistributable for Visual Studio 2015. Visit the Microsoft [website](http://microsoft.com/en-gb/download/details.aspx?id=48145) to download it. | -| Should images embedded in documents be processed? | Enable this option to perform OCR text extraction on images contained within documents | +| Should images embedded in documents be processed? | Enable this option to perform OCR text extraction on images contained within documents. | | Should the collection process optimise text storage by re-using text offsets? | Enable this option to use text offsets. | | Classification Configuration | | | Should default clues be automatically created? | Enable if you want a default clue to be created automatically when registering a taxonomy from SharePoint or creating a classification term within the NDC UI. The created clue will either be a standard clue matching the term name, or a metadata clue, depending on the configuration specified at the taxonomy level settings. [See Classification Rules (Clues) for more information.](/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/clues.md) | diff --git a/docs/dataclassification/5.7/introduction/initialconfiguration/security.md b/docs/dataclassification/5.7/introduction/initialconfiguration/security.md index 3d15b00f55..7c66c5dfb3 100644 --- a/docs/dataclassification/5.7/introduction/initialconfiguration/security.md +++ b/docs/dataclassification/5.7/introduction/initialconfiguration/security.md @@ -11,14 +11,14 @@ On this step, you are prompted to choose how access to the administrative web co ![initial_config_users](/images/dataclassification/5.7/install/initialconfiguration/initial_config_users.webp) - Enable User Management - (Recommended) This enables control over access to different sections - of the administrative web console on a user by user basis. Users can be set as super users, granting + of the administrative web console on a user by user basis. Users can be set as Super Users, granting full access, or can have their access granularly controlled using the Users settings page. :::note Netwrix strongly recommends enabling this option. ::: - When selected, you will be prompted to add super users. Type the name of any super user you wish to add and click + on - the right. USers with restricted access to NDC will need to be added via the Users configuration page at a later point. + When selected, you will be prompted to add Super Users. Type the name of any Super User you wish to add and click + on + the right. Users with restricted access to NDC will need to be added via the Users configuration page at a later point. - Allow access for all users – select to allow any user access administrative web console. diff --git a/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md b/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md index 61158f4066..b2e20511eb 100644 --- a/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md +++ b/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md @@ -48,5 +48,5 @@ right-clicking, and selecting Properties. :::note Netwrix recommends that you do not change the recovery model to avoid excessive log file - growth. + growth. ::: diff --git a/docs/dataclassification/5.7/introduction/install/overview.md b/docs/dataclassification/5.7/introduction/install/overview.md index f727f1f186..811736b632 100644 --- a/docs/dataclassification/5.7/introduction/install/overview.md +++ b/docs/dataclassification/5.7/introduction/install/overview.md @@ -25,7 +25,7 @@ sidebar_position: 40 | Password | Provide the account password. | | Database Name | Enter the name of the NDC database. Netwrix recommends using NDC as the database name. | - If the database does not yet exist, you'll need to click Create SQL Database before moving to the next step - this will automatically create the NDC database with the given name and default configuration. + If the database does not yet exist, you will need to click Create SQL Database before moving to the next step - this will automatically create the NDC database with the given name and default configuration. :::note The database is created automatically in basic configuration mode. For recommended @@ -35,11 +35,11 @@ sidebar_position: 40 7. If you are installing a secondary NDC instance to an [NDC Distributed Query Server](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md), you will be shown the DQS registration step. Complete the following steps: - a. Confirm that the Primary NDC Server URL displayed matches the QS Path of the primary NDC instance (the first entry in the DQS table in the administrative web console) and click Connect to connect the installer to the primary instance. - b. When the connection succeeds, an Authentication code will be generated and displayed in the Authentication Code textbox. Click Register - this will copy the Authentication code to the clipboard and open the administration console DQS configuration page in a browser window. - c. Click Register/Resync. The authentication code should automatically be inserted into the input box, paste the code if it hasn't been then click Submit. - d. Copy the verification code displayed and input it into the Verification code input box in the installer, then click Join. - e. Once the NDC instance has been successfully joined to the DQS configuration, you can click Next to move to the next installation step. + 1. Confirm that the Primary NDC Server URL displayed matches the QS Path of the primary NDC instance (the first entry in the DQS table in the administrative web console) and click Connect to connect the installer to the primary instance. + 1. When the connection succeeds, an Authentication code will be generated and displayed in the Authentication Code field. Click Register - this will copy the Authentication code to the clipboard and open the administration console DQS configuration page in a browser window. + 1. Click Register/Resync. The authentication code should automatically be inserted into the input box. If the field has not been autofilled, paste it manually, then click Submit. + 1. Copy the verification code displayed and input it into the Verification code input box in the installer, then click Join. + 1. Once the NDC instance has been successfully joined to the DQS configuration, you can click Next to move to the next installation step. 8. On the Licensing step, add your license. You can add the license as follows: diff --git a/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md b/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md index 376405fcc4..ba2bd58378 100644 --- a/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md +++ b/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md @@ -68,7 +68,7 @@ use the NDC script-based [file scanning tool](https://www.netwrix.com/download/p **Exchange Mailboxes** -If you plan on using NDC to crawl an on-premise Exchange server, you need to know the following: +If you plan on using NDC to crawl an on-premises Exchange server, you need to know the following: - Number of Mailboxes - Mailbox retention policy (for how long users keep their emails before they are archived) diff --git a/docs/dataclassification/5.7/introduction/upgrade.md b/docs/dataclassification/5.7/introduction/upgrade.md index 6905360b3d..18eec54ee4 100644 --- a/docs/dataclassification/5.7/introduction/upgrade.md +++ b/docs/dataclassification/5.7/introduction/upgrade.md @@ -48,17 +48,19 @@ to version 5.5, then perform a second upgrade to version 5.7. ## Upgrading a DQS environment -When upgrading an NDC environment which utilises the **Distributed Query Server** functionality, the primary server -should be upgraded first before upgrading the secondary instance(s). +When upgrading an NDC environment which utilises the **Distributed Query Server** functionality to 5.7.10 or later, +the primary server should be upgraded first before upgrading the secondary instance(s). Secondary instances will +attempt to resynchronise with the primary instance during the upgrade process, which will fail if the primary +instance has not been upgraded. -If you are upgrading to 5.7.10 or later from an earlier version of 5.7, if possible you should -run the installer as the NDC service account. If this is not done, you will need to perform a DQS +When upgrading to 5.7.10 or later from an earlier version of 5.7, you should +run the installer as the NDC service account if possible. If this is not done, you will need to perform a DQS resynchronisation when upgrading each secondary DQS instance. For further details on this process, see the [DQS Instructions](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md) page. ## After the Upgrade -During the seamless upgrade from previous versions, Netwrix Data Classification preserves its +During the upgrade from previous versions, Netwrix Data Classification preserves its configuration, so you will be able to classify your data right after finishing the upgrade. However, there are several steps you may need to take after upgrading. diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/communicationsettings.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/communicationsettings.md index 05166fd73a..28e9d83b45 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/communicationsettings.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/communicationsettings.md @@ -18,7 +18,7 @@ configuring email groups and health service notifications. Review the following Email servers can be configured to enable external communication. This can be used to send report subscriptions and health errors to users automatically. -Servers can be amended post-configuration by selecting Edit, and new SMTP servers can be added by +Servers can be modified after initial configuration by selecting Edit, and new SMTP servers can be added by selecting Add Email Server Configuration. ![configemailservers](/images/dataclassification/5.7/configuration/configemailservers.webp) diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md index 44c3687e39..8b93297ae8 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md @@ -21,7 +21,7 @@ Most options have an associated information popup (the “**i**” symbol next t | **General settings** | | | | Report Source Filter Mode | Use to add an additional filter for either Source Groups (default) or Source(s) | | | Disable Security Trimming | Select this option if you want to ensure that search results retrieved by API or the Taxonomies area will be unfiltered (ignoring the user name of the administrative user). | Disables the application of security trimming from search results (taxonomy browse/search). | -| Auto-Expunge Deleted Pages | When this is enabled, deleted documents will be automatically expunged 7 days after the last collection attempt. | Note that documents that are deleted manually or by the source file watchers may be deleted in fewer than 7 days depending on the last collection date. | +| Auto-Expunge Deleted Documents | When this is enabled, deleted documents will be automatically expunged 7 days after the last collection attempt. | Note that documents that are deleted manually or by the source file watchers may be deleted in fewer than 7 days depending on the last collection date. | | **Advanced settings** | | | | Instance name | Name of the NDC Server instance | | | Administration URL | URL of the web-based management console. Default URL is _http://localhost/conceptQS_. | If necessary, specify another Netwrix standalone server or cluster server instead of local host. You can use server name or IP address. | diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/system.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/system.md index e00b99c6dc..85c777197a 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/system.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/system.md @@ -18,8 +18,8 @@ This configuration tab contains the settings related to system health, operation | Log Level | Defines logging level that should be persisted to the log targets. Supported levels:
  • **Errors**
  • **Errors & Warnings**
  • **Errors Warnings & Info**
  • **Verbose**
| Each level includes all logs from higher levels. | | Tracing | Used to control which components of the system persist logs to the log targets. | Will apply to selected components (none by default) | | Log Targets | Select where the log should be written: to a csv file, to Windows Event Log, or both. | | -| File Log Location | If you selected to write logs to file, the csv log files will be stored at this location path. | Default is _C:\ProgramData\Netwrix Data Classification\Logs_. This cannot be manually changed. | -| File Log Retention Period | Number of days (since the last use) that file logs should be kept for before deletion. | To keep all logs (without automatic deletion), specify _0_ . | +| File Log Location | If you selected to write logs to file, the CSV log files will be stored at this location. | The file log location is _C:\ProgramData\Netwrix Data Classification\Logs_. This cannot be manually changed. | +| File Log Retention Period | Number of days that file logs should be kept for before deletion (after last write). | To keep all logs (without automatic deletion), specify _0_ . | | Send anonymous usage statistics? | Disabled by default. When enabled, the program will send a small amount of information of how the product is being used — to improve the functionality of the product and future offerings. | Personal information/ company data will not be sent. | | **Advanced settings** | | | | Max Database Size | Specifies the max size (in GB) the SQL database will grow to. | When this value is reached, Collector and Indexer components will be suspended. Default is _0_ (no limit). | diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/texthandling.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/texthandling.md index 46c53be00e..00af7f3862 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/texthandling.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/texthandling.md @@ -80,8 +80,8 @@ clue – or a search term. [](#)OCR Language Mapping The OCR language mapping configuration screen can be used if you wish to OCR non-English images via -Tesseract. File paths (including parts of paths) can be mapped to specific Tesseract language packs. -The Page Segmentation Mode used by the Tika OCR can also be overridden here for a given file path. +Tesseract and Apache Tika. File paths (including parts of paths) can be mapped to specific Tesseract language packs. +The Page Segmentation Mode used by the Apache Tika OCR engine can also be overridden here for a given file path. ![configocrlanguagemapping](/images/dataclassification/5.7/configuration/configocrlanguagemapping.webp) diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/users/securendc.md b/docs/dataclassification/5.7/systemconfigurationoverview/users/securendc.md index e6d1c2be66..4c80f44d4f 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/users/securendc.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/users/securendc.md @@ -65,7 +65,7 @@ the full text at rest. You can enable this mode by: 1. Access the Administration Console; 2. Select Config from the top navigation bar; 3. On the Collector tab, enable the Encrypt Text (Text.cse) option (this is an advanced setting - -select the spanner icon in the bottom left to display it); +select the wrench icon in the bottom left to display it); 4. Select Save. The other index files cannot be reverse engineered to retrieve the full document text - however, do diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md b/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md index 0d165b8985..3d622f590c 100644 --- a/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md +++ b/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md @@ -25,7 +25,7 @@ follows: **Step 2 –** Check that the Authentication settings are correct in IIS for Windows Authentication: -The conceptQS web application should have these authentication methods enabled: +The NDC web application should have these authentication methods enabled: - Anonymous Authentication - Windows Authentication @@ -34,7 +34,7 @@ All other authentication methods should be disabled. ![iis_thumb_0_0](/images/dataclassification/5.7/security/iis_thumb_0_0.webp) -**Step 3 –** If you wish to allow anonymous access to the conceptQS, edit the conceptQS web.config +**Step 3 –** If you wish to allow anonymous access to NDC, edit the conceptQS web.config file and delete (or comment out) three lines: