diff --git a/.github/workflows/claude-code-review.yml b/.github/workflows/claude-code-review.yml
index be24abaa0e..3ba1391534 100644
--- a/.github/workflows/claude-code-review.yml
+++ b/.github/workflows/claude-code-review.yml
@@ -12,7 +12,7 @@ on:
jobs:
code-review:
- if: github.event.pull_request.head.repo.fork == false
+ if: github.event.pull_request.head.repo.fork == false && github.actor != 'dependabot[bot]'
concurrency:
group: code-review-${{ github.event.pull_request.number }}
cancel-in-progress: true
diff --git a/docs/customer/training/learn-about/pingcastle.md b/docs/customer/training/learn-about/pingcastle.md
index d9436f3bd1..2df06630c8 100644
--- a/docs/customer/training/learn-about/pingcastle.md
+++ b/docs/customer/training/learn-about/pingcastle.md
@@ -6,17 +6,20 @@ keywords: [training, course, pingcastle]
description: "Learn about Netwrix PingCastle through introductory courses"
---
-import { NPCValue, NPCConcepts } from '@site/src/training/pingcastle';
+import { NPCValue, NPCConcepts, NPCIntro } from '@site/src/training/pingcastle';
import { Company, NPC } from '@site/src/training/products';
-Estimated length: 1 hour 5 minutes
+Estimated length: 2 hours 30 minutes
This learning path introduces you to . It contains the following courses:
* 1680 – Valuable Features
* 2680 – Concepts & Architecture
+* 3680 Introduction to
+
+
diff --git a/docs/customer/training/product/pingcastle.md b/docs/customer/training/product/pingcastle.md
index ad2bc81d08..95982c6740 100644
--- a/docs/customer/training/product/pingcastle.md
+++ b/docs/customer/training/product/pingcastle.md
@@ -6,17 +6,20 @@ keywords: [training, course, pingcastle]
description: "Learn to use Netwrix PingCastle through courses"
---
-import { NPCValue, NPCConcepts } from '@site/src/training/pingcastle';
+import { NPCValue, NPCConcepts, NPCIntro } from '@site/src/training/pingcastle';
import { Company, NPC } from '@site/src/training/products';
-Estimated length: 1 hour 5 minutes
+Estimated length: 2 hours 30 minutes
In this learning path, you will learn how to use . It contains the following courses:
* 1680 – Valuable Features
* 2680 – Concepts & Architecture
+* 3680 Introduction to
+
+
diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addbox.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addbox.md
index 03592e67d2..66d0d58b48 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addbox.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addbox.md
@@ -9,12 +9,11 @@ sidebar_position: 10
Use the **Box** source configuration window to set up the crawling and classification operations for
content stored in a Box Enterprise account.
-By default, configuration window displays basic configuration settings only. It is recommended that
-you click the "wrench" icon in the bottom left corner to configure advanced settings.
+By default, the configuration window displays basic configuration settings only. Click the "wrench" icon in the bottom left corner to configure advanced settings.
:::note
To configure advanced settings, your user account may need advanced privileges.
-[See Users and Security Settings for more information.](/docs/dataclassification/5.7/systemconfigurationoverview/users/users.md)
+See [Users and Security Settings](/docs/dataclassification/5.7/systemconfigurationoverview/users/users.md) for details on required privileges.
:::
@@ -25,19 +24,19 @@ 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 item #12 of Step 1). The program then parses this file and fills in the relevant fields 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”. |
| Public Key ID Private Key Private Key Password | Created when generating the trust between your Box account, and the Netwrix Data Classification app – these should be kept secret and secure. |
-| Write Classifications | Identifies whether classifications should be written back to the Box source documents. Classification results can either be written to classification templates or to the generic ‘tags’ property. This is specified using the **Write Configuration** setting of the source. For more information, see [Use Tagging](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/tagging.md) |
+| Write Classifications | Identifies whether classifications should be written back to the Box source documents. Classification results can either be written to classification templates or to the generic ‘tags’ property. This is specified using the **Write Configuration** setting of the source. See [Use Tagging](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/tagging.md) for instructions on configuring tag writeback. |
| Source Group | Select the source group (if any). |
| Pause source on creation | Select if you want to make other configuration changes before collection of the source occurs. |
| **Advanced settings** | |
| Email Address | Specify one or more users (email addresses) for impersonated crawling. - If specified explicitly, the crawling engine will impersonate these users when crawling their content as well as shared content where they are the owners. Enter one or several accounts from those listed in the _Managed Users_ on the '_Users and Groups_' tab of the Box console.
- If not specified explicitly, the program will automatically create and use an admin user account (_NDC Crawling Account_) for crawling. Remember to provide this app user account with sufficient permissions for the content you want to index (i.e. share access). To share content for crawling with this account, use group membership.
|
| Re-Index Period | Specifies how often the source should be checked for changes (period in days). Default is **7** days. |
| Priority | Set priority for this data source to be crawled. |
-| Document Type | Specify a value which can be used to restrict queries when utilizing the Netwrix Data Classification search index. |
+| Document Type | Specify a value to restrict queries when using the Netwrix Data Classification search index. |
See also:
diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md
index ff719ef6a7..c49b6ef597 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/adddropbox.md
@@ -6,11 +6,10 @@ sidebar_position: 20
# Dropbox
-The Dropbox source configuration screen allows you to enable the crawling and classification of
+Use the Dropbox source configuration screen 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.
-[See Configure Dropbox for Crawling for more information.](/docs/dataclassification/5.7/introduction/introduction/dropbox.md)
+**IMPORTANT:** Ensure you created and configured a Dropbox app before adding the source. See [Configure Dropbox for Crawling](/docs/dataclassification/5.7/introduction/introduction/dropbox.md) for app requirements.
@@ -18,10 +17,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: - Disabled – documents' 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.
|
-| Source Group | Netwrix recommends creating a dedicated source group for Dropbox. |
+| 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 team folders you want to crawl. For personal folders, this option isn't required. See the Dropbox [Namespace guide](https://www.dropbox.com/developers/reference/namespace-guide) for details on namespace types and access requirements. |
+| 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 to increase detail and accuracy of results.
|
+| Source Group | Netwrix recommends creating a dedicated source group for Dropbox. If there are no existing Dropbox source groups, 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..a3fb5caa44 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/addsingledatabase.md
@@ -6,21 +6,20 @@ 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.
+Use the Database source configuration screen 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.
-When crawling the data, Unicode table names or unicode primary keys are not supported. Primary keys
+When crawling the data, Unicode table names or unicode primary keys aren't supported. Primary keys
are supported only with Latin alphabet.
-Once connected it is possible to create an intelligent content mapping, crawling certain fields as
-unstructured index text, and other fields as mapped metadata. For more information please see the
-[Database Configuration Wizard](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/databaseconfigwizard.md) section.
+After connecting, you can create an intelligent content mapping, crawling certain fields as
+unstructured index text, and other fields as mapped metadata. See the
+[Database Configuration Wizard](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/databaseconfigwizard.md) section for instructions on configuring field mappings.
-If you wish to make other configuration changes before collection of the source occurs ensure you
-tick the checkbox "_Pause source on creation_".
+If you want to make other configuration changes before collection of the source occurs, select the **Pause source on creation** checkbox.
@@ -28,15 +27,15 @@ Complete the following fields:
| Option | Description |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Connection Type | Select your connection type: MS SQL, MySQL, 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**. - With **Integration** option selected, database will be accessed under the account currently logged on.
- With **SQL** option selected, specify user name and password to be used when accessing the database.
|
-| OCR Processing Mode | Select processing mode for images in the documents: - Disabled – documents' 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 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. |
+| Connection Type | Select your connection type: MS SQL, MySQL, PostgreSQL, or Oracle. |
+| Server | Specify the server name of the database system to be crawled (use "." to indicate the local server). |
+| Database Name | Specify the name of the database that will be crawled. You can configure multiple databases from the same server. |
+| Authentication Method | Select authentication method: **Integrated** or **SQL**. - With **Integrated** option selected, NDC accesses the database 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.
Integrated authentication is only supported for MS SQL databases. |
+| 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 don't 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. |
After the source configuration is completed, you will be prompted to lauch SQL crawling
configuration wizard.
-[See Database Configuration Wizard for more information.](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/databaseconfigwizard.md)
+See [Database Configuration Wizard](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsingledatabase/databaseconfigwizard.md) for instructions on mapping fields and configuring 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..907538d6eb 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsource.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsource.md
@@ -9,7 +9,7 @@ sidebar_position: 10
To start processing your data, you need to add a corresponding content source to the Netwrix Data
Classification scope.
-Follow the steps to add a content source.
+To add a content source:
**Step 1 –** In administrative web console, navigate to **Content** →Sources → General and click
**Add** to launch the Add source wizard.
@@ -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 SQL 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)
@@ -29,13 +30,11 @@ the sources:
- [Outlook Mail Archive](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/outlookmailarchive.md)
- [SharePoint](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/overview_1.md) or [SharePoint Online](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/sharepointonline.md)
-All your content sources will be listed in the **Sources** section.
+The **Sources** section lists all your content sources.
:::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.
-[Users and Security Settings](/docs/dataclassification/5.7/systemconfigurationoverview/users/users.md)
-
+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, accessible by clicking on the username in the top right.
:::
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..b3b68df7c7 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md
@@ -6,22 +6,30 @@ 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.
+The SQL Server source configuration screen lets you enable the crawling and classification of
+content stored in your MS SQL, MySQL, PostgreSQL, and Oracle servers. 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
+After connecting, you can create an intelligent content mapping, crawling certain fields as
unstructured index text, and other fields as mapped metadata.
To crawl SQL server:
1. Go to **Content → Sources** and select **Add**.
2. Select **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).
+3. Specify the server type: [MS SQL Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mssqlserver.md), [MySQL Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mysqlserver.md), [Oracle Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/oracleserver.md), or [PostgreSQL Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md).
-
-4. Select Save.
+4. Complete the following fields:
+
+ | Option | Description |
+ | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+ | Server | Specify the server name of the database system to be crawled (use "." to indicate the local server). |
+ | Authentication Method | Select authentication method: **Integrated** or **SQL**. - With **Integrated** option selected, NDC accesses the database via the NDC Service Account.
- With **SQL** option selected, you specify the user name and password to be used when accessing the database.
Integrated authentication is only supported for MS SQL databases. |
+ | 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 don't 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. |
+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/mssqlserver.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mssqlserver.md
index c3fbd14d7b..745cf977b3 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mssqlserver.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/mssqlserver.md
@@ -6,19 +6,20 @@ sidebar_position: 20
# Add MS SQL Server
-Once you choose to add SQL server source, you opt to add MS SQL 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 an MS SQL server as the source. For more
+information, see [SQL Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md).
To connect to a MS SQL server:
-1. On the **Source Configuration** screen, select **MS SQL**.
+1. On the **Source Configuration** screen, select **SQL Server**, then set **Connection Type** to **MS SQL**.
2. Specify MS SQL server.
-
- 
-
3. Specify Authentication method:
- Integrated
- SQL - specify username and password of the MS SQL server.
+
+
+ 
+
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
new file mode 100644
index 0000000000..1ae8e7968f
--- /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
+
+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 **SQL Server**, then set **Connection Type** to **MySQL**.
+2. Specify MySQL server, username, and password.
+
+ 
+
+
+3. Select Save.
diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/oracleserver.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/oracleserver.md
index 12b84d5cf8..e3d44b6d72 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/oracleserver.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/oracleserver.md
@@ -6,12 +6,12 @@ sidebar_position: 10
# Add Oracle Server Source
-Once you choose to add SQL server source, you opt to add Oracle 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 an Oracle server as the source. For more
+information, see [SQL Server](/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/addsqlserversource.md).
To connect to an Oracle server:
-1. On the **Source Configuration** screen, select **Oracle**.
+1. On the **Source Configuration** screen, select **SQL Server**, then set **Connection Type** to **Oracle**.
2. Specify Oracle server, username, Container DB Service Name, and Oracle password.
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..e40dcc630d
--- /dev/null
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/addsource/addsqlserversource/postgresqlserver.md
@@ -0,0 +1,19 @@
+---
+title: "Add PostgreSQL Server Source"
+description: "Add PostgreSQL Server"
+sidebar_position: 40
+---
+
+# Add PostgreSQL Server
+
+When adding a SQL server source, you can choose to add a PostgreSQL server as the 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**, then set **Connection Type** to **PostgreSQL**.
+2. Specify PostgreSQL server, the Master Database name (commonly `postgres`), username, and password.
+
+ 
+
+3. 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..7d45d8cef9 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/manage/managefilesystem.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/manage/managefilesystem.md
@@ -12,7 +12,7 @@ and how to configure writing classification attributes back to the content files
## Configure Tagging
You can instruct the program to write classification attributes back to processed files. This
-operation is also called "tagging". Tagging is currently supported for the following file types:
+operation is also called "tagging". Tagging is supported for the following file types:
- DOC/DOCX
- PPT/PPTX
@@ -44,7 +44,7 @@ Related content source settings can be configured at a global level (default), o
| **Enabled** | Use this option to enable / disable tagging with attributes included in this taxonomy. | Cleared by default. |
| **Field Name** | Define the attribute name to be used when persisting the classifications (metadata property name). | |
| **Format** | How the classifications should be formatted. | You can create a custom delimited combination of the labels / GUIDs. |
-| **Name/ID** or **Class** | Depending on the format, take the term labels, IDs or a combination of both | The corresponding Delimiter must be a string or array type, with a maximum length of 3. |
+| **Name/ID** or **Class** | Depending on the format, take the term labels, IDs, or a combination of both | The corresponding Delimiter must be a string or array type, with a maximum length of 3. |
| **Prefix/** **Suffix** | Will be appended to the formatted string of classifications. | |
**Example**
@@ -52,20 +52,20 @@ Related content source settings can be configured at a global level (default), o
Assume you selected the _Agriculture_ taxonomy; it has _Farming_ (_ClassID: 11_) and _Produce_
(_ClassID: 32_) properties.
-If you configure tagging as in the screenshot above, the program will write the following
-classifications attributes to the classified documents:
+If you configure tagging as described, the program will write the following
+classification attributes to the classified documents:
- Property Name: _Agriculture_
- Property Value: _[Farming|11;Produce|32]_
**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 want 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 use the global taxonomy writing settings,
+ select the **Use Global Configuration** checkbox at the top of the page. To configure settings for the selected source specifically, ensure
+ this checkbox is unchecked.
+3. Select the taxonomy you want and click **Edit**.
4. In the taxonomy properties, select the **Enabled** checkbox and specify the settings described in
the table above.
@@ -76,7 +76,7 @@ classifications attributes to the classified documents:
**File inclusions** tab contains the list of file types that will be included in the indexing
process. Any file with a file extension not specified in this list will be ignored.
-You can delete, modify, or add the necessary inclusions as explained below.
+You can delete, modify, or add the necessary inclusions as needed.
To specify inclusions, do the following:
@@ -84,10 +84,11 @@ To specify inclusions, do the following:
Included.
2. Select the necessary extensions to be used as including filter when processing files.
3. To modify an extension (for example, add a wildcard), click **Edit**. To add a new one, click
- **Add**.
+ **Add**. The "\*" wildcard can be added to an inclusion filter to match one or more characters.
+ Files without extensions can be included by adding "." as an inclusion filter.
:::note
-Inclusions are case-insensitive. A wildcard (\*) is supported.
+Inclusions are case-insensitive.
:::
@@ -102,7 +103,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:
@@ -123,14 +124,14 @@ Exclusions are case-insensitive.
3. Optionally, enter a test path to verify the settings and click **Test**.
4. If needed, you can use metadata conditions to restrict when an exclusion filter should be
applied. For that, click **Condition** tab and click **Add**. Then select how the exclusion
- conditions will work: it can check if metadata field of the document has any value, is not
+ conditions will work: it can check if metadata field of the document has any value, isn't
specified, or matches a specific metadata value.
| Criteria | Condition |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
- | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, you will then need to specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "does not contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as follows: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ |
+ | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, you will then need to specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "doesn't contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as follows: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ |
| Has any value | Exclude the document if its metadata field has any value. With this criteria selected, specify **Field Name**. |
- | Has no values | Exclude the document if metadata field value is not specified. With this criteria selected, specify **Field Name**. |
+ | Has no values | Exclude the document if metadata field value isn't specified. With this criteria selected, specify **Field Name**. |
5. When finished, click **Add**.
6. Finally, click **Save** and close the window.
diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/sourcegroups/overview.md b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/sourcegroups/overview.md
index 0be4534913..6dcf1349d3 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/introduction/sourcegroups/overview.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/introduction/sourcegroups/overview.md
@@ -7,17 +7,16 @@ sidebar_position: 60
# Source Groups
Source groups provide a way of logically grouping specific sources, perhaps by type, or perhaps by
-an internal business specification. Selecting the option Add to Group on the main sources grid
-screen will present the following pop-up:
+an internal business specification.
-
+A group can either be "mixed", which allows it to contain all source types, or source-specific. For example, you could create a
+source group named "Demo Content", which only supports the addition of SharePoint sources. When you create a source, any existing source
+groups that support that source type will be displayed in a dropdown in the source configuration screen.
-A group can either be "mixed", which allows it to contain all source types, or source specific. In
-the example above a group would be created entitled "Demo Content", which only supports the addition
-of SharePoint sources. If a supporting source group already exists, this can be selected from the
-drop-down list provided. See Dynamic Source Groups for more information.
+Certain source types are treated as source groups. See [Dynamic Source Groups](#dynamic-source-groups) for the available
+group types and configuration options.
-Selecting the cog icon on the main sources grid screen for a source group allows you to amend the
+Select the cog icon on the main sources grid screen for a source group to amend the
group settings:
@@ -29,20 +28,22 @@ Here you can:
- Disable Search Index — When disabled, content will not be processed into the core search index
(classification will occur as normal, although content will be excluded from Browse / Search /
Suggestions).
-- **NOTE:** Credentials will only be supported if the source group is type specific
- Discovery mode — This allows a source to be fully enumerated before any files are processed.
- _(SharePoint only)_ Supply regular expression rules to support automatically assigning sources to
a specific group
- Enable Text Extraction - Allows reading the documents and run classification rules against their
- content. By unticking the check box, the system can fetch only the metadata without crawling the
+ content. By unticking the checkbox, the system can fetch only the metadata without crawling the
entire document. After this you can run a workflow to remove the old data, using **Document Age**
option. Unlike Discovery Mode, you can still run workflows if the workflow is triggered solely by
- metadata. To learn more, go
- to[Step 3. Specify Conditions for Processing](/docs/dataclassification/5.7/contentconfigurationoverview/workflows/manage/addworkflowwizard/step3specifyconditions.md) article.
+ metadata. See [Step 3. Specify Conditions for Processing](/docs/dataclassification/5.7/contentconfigurationoverview/workflows/manage/addworkflowwizard/step3specifyconditions.md) for instructions on configuring metadata-only workflows.
+
+:::note
+Credentials will only be supported if the source group is type-specific.
+:::
Deleting a group will remove all existing items from the group leaving them unassigned. You can also
-remove a specific source(s) from a group by selecting the source group in the grid and then
-selecting Remove from Group for the required source(s). Source groups can also be created and
+remove specific sources from a group by selecting the source group in the grid and then
+selecting Remove from Group for the required sources. Source groups can also be created and
assigned as part of the source creation process.
By going to the Settings of the Source Group, you can:
diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/additionalconfiguration.md b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/additionalconfiguration.md
index c13443fb3d..418fd6be39 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/additionalconfiguration.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/additionalconfiguration.md
@@ -11,8 +11,8 @@ additional information:
| Tab | Description |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Graph | The Graph tab shows a graphical representation of classification intersection points.  In the example above 6721 documents are tagged with "Medium (100kb-1Mb)", 1254 of these documents are also tagged with "HTML". It's also possible to see that there are 3517 documents that are tagged with both "HTML" and "English" (highlighted by the dashed links). |
+| Graph | The Graph tab shows a graphical representation of classification intersection points.  In this example, 6721 documents are tagged with "Medium (100kb-1Mb)", 1254 of these documents are also tagged with "HTML". It's also possible to see that there are 3517 documents that are tagged with both "HTML" and "English" (highlighted by the dashed links). |
| Info | The Info tab displays the term description (aka Scope Notes) for each preferred term. The Description field is often populated automatically when an external taxonomy is imported automatically using the Scope Notes. |
| Logs | All changes made to a term are recorded. The change history may be viewed from the Logs Tab:  |
| User Edits | When auto-classifications are amended in SharePoint the user edits are recorded in the SQL database, these can later be reviewed to identify terms that require review:  |
-| User Suggestions | An optional interface can be enabled to allow users to suggest new terms for the termset hierarchy (http://netwrixdataclassificationserver/conceptQS/Taxonomies/TermSuggest.aspx). Suggestions can trigger automatic notifications to taxonomy administrators, as well as being recorded in the database for later review on the "User Suggestions" tab:  |
+| User Suggestions | An optional interface can be enabled so users can suggest new terms for the termset hierarchy (http://netwrixdataclassificationserver/NDC/Taxonomies/TermSuggest.aspx). Suggestions can trigger automatic notifications to taxonomy administrators, as well as being recorded in the database for later review on the "User Suggestions" tab:  |
diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/builtintaxonomies.md b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/builtintaxonomies.md
index cc224c5968..21af5b1bca 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/builtintaxonomies.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/builtintaxonomies.md
@@ -6,8 +6,7 @@ sidebar_position: 10
# Built-in Taxonomies Overview
-Netwrix Data Classification comes with eight taxonomies with hundreds of classification rules
-out-of-the-box.
+Netwrix Data Classification comes with eight taxonomies with hundreds of built-in classification rules.
The four core taxonomies cover a broad range of sensitive personal, financial, and health-related
information. The remaining four taxonomies derive from the core set. They are tailored to meet the
@@ -21,8 +20,7 @@ This section contains the full list of built-in taxonomies supported by Netwrix
:::note
Netwrix Data Classification users can see only the taxonomies they have permissions to
-use. See the [User Management](/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md) section for more information on
-users' permissions.
+use. See [User Management](/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md) for details on configuring user permissions.
:::
@@ -90,7 +88,7 @@ users' permissions.
##### Payment Card Industry Data Security Standard (PCI DSS)
-Cardholder data (holder name, card number, expiration and security code) for the major payment
+Cardholder data (holder name, card number, expiration, and security code) for the major payment
systems:
- American Express
@@ -103,8 +101,8 @@ systems:
##### Patient Health Information (PHI)
-Medical forms, treatment records, prescription drugs, decease names/codes, allergies, social and
-insurance numbers.
+Medical forms, treatment records, prescription drugs, social and insurance numbers,
+decease names/codes, allergies.
## Derived Taxonomies
@@ -151,15 +149,15 @@ information (GDPR Article 9):
##### Gramm-Leach-Bliley Act (GLBA)
-Combines the Financial Records, PCI DSS and PII (US social security numbers) taxonomies.
+Combines the Financial Records, PCI DSS, and PII (U.S. social security numbers) taxonomies.
##### Health Insurance Portability and Accountability Act (HIPAA)
-Combines the PHI and PII (US social security numbers) taxonomies.
+Combines the PHI and PII (U.S. social security numbers) taxonomies.
##### Credentials
-Includes sensitive credentials data, such as tokens, private or public keys, passwords, generic
+Includes sensitive credentials data, such as tokens, public keys, private keys, passwords, generic
certificates, and others.
##### Cybersecurity Maturity Model Certification (CMMC)
@@ -174,16 +172,16 @@ 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,
+credentials) or non-sensitive (e.g. file size, language).
:::note
-This applies only to customized taxonomies, which you add by yourself. You cannot change
+This applies only to customized taxonomies, which you add by yourself. You can't change
the sensitivity settings for the pre-defined taxonomies.
:::
-Follow the steps to specify sensitive taxonomy.
+To specify a sensitive taxonomy:
**Step 1 –** Add a new taxonomy. See the [Add a Taxonomy](/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/add.md) topic for additional information.
diff --git a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/browse.md b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/browse.md
index 76ccad8d15..562bf8e193 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/browse.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/browse.md
@@ -6,15 +6,19 @@ sidebar_position: 50
# Browse
-To view the documents classified for each term, click on the Browse tab. This will display a list of
+To view the documents classified for each term, click the Browse tab. This will display a list of
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)
+See [Classification Rules (Clues)](/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/clues.md) for details on how clues control classification scoring.
:::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.
+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 aren't taken into account.
:::
+To see how the classification of each document would change based on the current term configuration,
+tick the Show Movements checkbox. When selected, the results will display any change
+in document scoring between the current stored document score and the score it would receive
+against the current classification clues.
The document text will be highlighted based upon the clues configured for the term. Highlighting
will include regular expression matches when configured (Config→Query Server→Enable Regex Browse
@@ -30,7 +34,7 @@ You can use the Browse function to:
- Identify documents that are receiving a score, but are "missing" being classified because they do
not quite reach the terms threshold. For example, changing the mode to "Near Misses `<20%`" for a
- term with a threshold of 50, will find any documents that scored 40 or more, but did not reach the
+ term with a threshold of 50, will find any documents that scored 40 or more, but didn't reach the
threshold.
- Identify low scoring documents that are only just reaching the classification threshold. For
example, changing the mode to "Low Scoring Documents `<20%`" for a term with a threshold of 50
@@ -38,6 +42,12 @@ You can use the Browse function to:
+:::note
+By default, results from sources that have not yet been indexed, or that aren't configured to be indexed, aren't 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
+select to show document movements and include unindexed documents. 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..70e9b87939 100644
--- a/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/search.md
+++ b/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/search.md
@@ -6,7 +6,7 @@ sidebar_position: 40
# Search Documents by Clue
-You can search for documents based on the class clues. For that, click on the name of any single
+You can search for documents based on the class clues. For that, click the name of any single
clue in the clue list in the management console (or even any suggested clue), go to the **Search**
tab and configure search settings.
@@ -18,7 +18,7 @@ tab and configure search settings.
- Clue itself (clue body) - enter the required keyword or phrase in the **Find** field.
:::note
- [See Classification Rules (Clues) for more information.](/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/clues.md)
+ See [Classification Rules (Clues)](/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/clues.md) for details on clue types and configuration.
:::
@@ -27,7 +27,7 @@ tab and configure search settings.
by quickly examining its usage within the corpus. Consider the following:
- The URL filter must end on a folder boundary.
- - Use custom filter to specify a number of complex filters: boolean, datetime and numeric.
+ - Use custom filter to specify a number of complex filters: boolean, datetime, and numeric.
:::note
Full description of all filters can be found in the API Reference Guide.
@@ -35,8 +35,8 @@ 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
- will be shown. Possible scenarios are:
+ document movements. When selected, the results will show any change in scoring of each document since the last time that document was classified.
+ For example:
diff --git a/docs/dataclassification/5.7/dashboards.md b/docs/dataclassification/5.7/dashboards.md
index ae74a18879..aa9e153e24 100644
--- a/docs/dataclassification/5.7/dashboards.md
+++ b/docs/dataclassification/5.7/dashboards.md
@@ -12,20 +12,21 @@ 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.
+You will also be able to view the average processing throughput.
+
+If you have the [Distributed Query Server](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md) functionality enabled, any instances that are missing their copy of the NDC encryption key will also be displayed here. See [Recovering the Encryption Key in Secondary NDC Instances](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/recoveringencryptionkeyindqsenvironment.md) for instructions on remediating missing encryption keys.
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.
+If the values aren't being updated 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,13 +35,16 @@ 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)
+ 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
+Deleted documents are retained as a safeguard against accidental deletion. Click the Expunge option located on the Deleted Automatically and Deleted Manually rows to fully remove those documents from the system. Automatic expunging can be enabled via the [Administration configuration settings](/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md). The Expunge option is only displayed if there are documents to be expunged.
+:::
+
## System Health
@@ -52,20 +56,20 @@ page to display more detailed information.
You will then see the list of reported issues, with the ability to view a detailed description of
the problem and suggested resolution steps.
-It is also possible to configure notifications of system issues, along with daily reports of
+You can also configure notifications of system issues, along with daily reports of
outstanding system issues.
1. Click Dismiss at the bottom.
-2. Select Only dismiss health notifications that are older than one week, if you do not want to be
+2. Select Only dismiss health notifications that are older than one week, if you don't want to be
notified on outdated issues.
3. Select what you want to dismiss – warnings and all security notifications.
## Netwrix Data Classification Service Viewer
-From the Netwrix Data Classification Service Viewer it is possible to view a live stream of the
+The Netwrix Data Classification Service Viewer displays a live stream of the
current work being processed by the NDC services. As the services progress each document, the
display will change. Once all work is complete, "Idle..." will be displayed.
diff --git a/docs/dataclassification/5.7/index.md b/docs/dataclassification/5.7/index.md
index 7759bcf03c..b921209d0f 100644
--- a/docs/dataclassification/5.7/index.md
+++ b/docs/dataclassification/5.7/index.md
@@ -7,7 +7,7 @@ sidebar_position: 1
# Features and Benefits
Netwrix Data Classification is a platform that identifies data that’s important for your
-organization and enables you to reduce risk and unleash the true value of this data.
+organization, helping you reduce risk and unleash the true value of this data.
Powered by unique compound term processing technology, it enriches your enterprise content with
accurate and consistent metadata empowering you to work with data more confidently. By seeing which
@@ -32,10 +32,10 @@ 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.
+The following figure shows the app architecture and components.
@@ -44,16 +44,15 @@ You can view the app architecture and components in the figure below.
-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
- columns for supported document types.
-7. If Remediation Workflows are enabled, the configured workflows are run on documents that meet the
+ pre-built taxonomies (the Netwrix compliance taxonomies) and customer-created taxonomies.
+6. If [Classification Writing](/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/enablewriteclassifications.md) is enabled, the assigned classification labels are written to the custom metadata columns for supported document types.
+7. If [Workflows](/docs/dataclassification/5.7/contentconfigurationoverview/workflows/overview.md) have been defined and are enabled, they are run on documents that meet the
workflow conditions.
## QueryServer
@@ -81,14 +80,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 NDC Collector 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.
@@ -123,22 +121,24 @@ using information contained in the proprietary conceptDatabase.
The current release of Netwrix Data Classification supports SQL Server 2008 R2 or later.
-## 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.
-Note that “text.cse” is not supplied since it will be created automatically when the first documents
+The NDC Index files should be located on the same server as the Netwrix Data
+Classification server because the query and indexing processes can be highly disk-intensive.
+
+:::note
+"text.cse" isn't 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 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](/docs/dataclassification/5.7/dataanalysisoverview/dsar/overview.md).
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..cd2dcf3ed3 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 uses two forms of data storage:
- NDC SQL database — SQL Server database that stores product configuration and metadata for the data
sources.
@@ -15,17 +15,17 @@ Netwrix Data Classification utilizes two data storages:
### NDC SQL database
-Make sure you have NDC Server and **NDC SQL database** deployed on different machines.
+Ensure you have NDC Server and **NDC SQL database** deployed on different machines.
-It is recommended to create the NDC SQL database on a dedicated SQL Server instance.
+Netwrix recommends hosting the NDC SQL database on a dedicated SQL Server instance.
- 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_.
+ Due to built-in limitations of size and capacity, 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 the database and Netwrix Data Classification
servers.
- If configuring database settings via SQL Server Management Studio, you will need to set
@@ -33,16 +33,17 @@ It is recommended to create the NDC SQL database on a dedicated SQL Server inst
- **File growth**: _128 MB_ - recommended value for small to medium environment, _512 MB_ - for
large environment, i.e. if planning to index data sources containing 16, 000, 000+ objects.
- **Maximum File Size** - select _Unlimited_.
-- Make sure that the **Recovery model** for this database is set to _Simple_. Do not change the
- recovery model — to avoid log files growth.
+- Ensure that the **Recovery model** for this database is set to _Simple_. To prevent log files from
+ growing excessively, don't change the recovery model.
### NDC Index
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 general estimate, 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
@@ -56,7 +57,7 @@ environments can be ranged as follows:
| Up to 64, 000, 000 | Large-size environment | |
| More than 64, 000, 000 | Extra-large environment | System architect's assistance is required for deployment planning requires |
-Again, consider that for the large-size and extra-large environments, it is strongly recommended to
-configure a cluster of several NDC Servers and apply DQS mode to these clustered servers. See
+Again, consider that for the large-size and extra-large environments, Netwrix strongly recommends
+configuring a cluster of several NDC Servers and applying DQS mode to these clustered servers. See
[Configuring NDC Servers Cluster and Load Balancing with DQS Mode](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md)
for details.
diff --git a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md
index 7a4f11bb91..123341332f 100644
--- a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md
+++ b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md
@@ -1,62 +1,52 @@
---
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 lets you balance the processing load of data collection,
+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—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 64M objects per cluster of 4 servers.
+- SharePoint — Recommended if processing over 8M objects,
+supports up to 32M 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_ application.
-This functionality is implemented through the _QueryServer_ application installed together with NDC
-Server.
+## Configuring DQS Mode
-## Applying DQS Mode
+DQS mode is configured via the administrative web console and, from version 5.7.10 onwards, the installer.
-DQS mode can be configured via the administrative web console.
+If you want to implement DQS configuration for your NDC deployment, be aware that you can't easily
+undo it. Netwrix strongly recommends taking a full backup of your environment before enabling DQS.
+Also, read the DQS documentation sections thoroughly before you start.
-If you want to implement DQS configuration for your NDC deployment, consider the following:
+Ensure 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.
-- 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.
+DQS mode can only be configured by a user whose account has the **Superuser** role.
-To be able to configure the DQS mode, current account requires a **Superuser** role.
-
-To arrange NDC Servers cluster and apply DQS mode
+### 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 open the DQS addition menu, and input the details for the first secondary NDC server.
@@ -64,37 +54,80 @@ 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
- requires a dedicated machine. Make sure they meet the
+ | Server | The NDC Server name or IP address (name format is case-insensitive). |
+ | 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. |
+
+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. Ensure 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.
-9. On the SQL Database step, provide the name of the SQL Server instance that hosts NDC SQL database
+ [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 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 7 - 10 for each NDC Server to be added.
+
+
+
+### 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. Ensure 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 resynchronize the DQS instances in the
+ background and, if successful, will skip the DQS Synchronization step. You can then skip ahead in these instructions
+ to step 13.
+
+ The DQS Synchronization step will only display for an upgrade if this process fails. Follow the steps below to
+ resynchronize 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 isn't 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. After 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 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
-Ignore the confirmation dialog on the existing schema in the selected SQL database.
+If the authentication code isn't autofilled, click 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.
:::
-
-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.
+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 additional NDC Server to be added, then review the list of servers to ensure all new
+ servers have been successfully added.
-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.
+
+If you were configuring the DQS mode for an existing NDC deployment, you will be prompted to
+re-collect data from the data sources 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
@@ -103,4 +136,4 @@ after clicking **Run Cleaner** button on the **Settings > Core > Collector** tab
To review system health and check your configuration, use the product dashboards.
-[See Operations and Health Dashboards for more information.](/docs/dataclassification/5.7/dashboards.md)
+See [Operations and Health Dashboards](/docs/dataclassification/5.7/dashboards.md) for details on monitoring system status.
diff --git a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/ndcserverandclient.md b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/ndcserverandclient.md
index 34c3f1220f..c609eb839e 100644
--- a/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/ndcserverandclient.md
+++ b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/ndcserverandclient.md
@@ -6,16 +6,17 @@ 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 isn't 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. See
+[Hardware Requirements](/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md) for the recommended NDC Server specifications.
-**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).
+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. See
+[Software Requirements](/docs/dataclassification/5.7/introduction/requirements/softwarerequirements.md) for supported operating systems and prerequisites.
:::note
For evaluation and PoC purposes, Netwrix provides a _virtual appliance_ — a virtual
@@ -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 isn't 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.
-[See Configuring NDC Servers Cluster and Load Balancing with DQS Mode for more information.](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md)
+To balance processing load while collecting, indexing, and classifying data in large-size and extra-large
+environments (i.e. 16m+ objects to process), Netwrix strongly recommends deploying
+multiple NDC Servers in **Distributed Query Server** mode.
+See [Configuring NDC Server Cluster and Load Balancing with DQS Mode](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md) for instructions on setting up a multi-server cluster.
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..81d4030f68
--- /dev/null
+++ b/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/recoveringencryptionkeyindqsenvironment.md
@@ -0,0 +1,30 @@
+---
+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 an NDC instance detects that the encryption key is missing, a health error will be logged and displayed on the NDC Stats dashboard and the services on that instance 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 or accessible 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 assistance with recovering the encryption key from a secondary instance to the primary instance.
+
+## 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. Continue through to the DQS sync step.
+4. Follow the instructions listed in steps 9 through 12 of the [Enabling DQS Mode (5.7.10 and later versions) section of Configuring an NDC Server Cluster and Load Balancing with DQS Mode](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md#enabling-dqs-mode-5710-and-later-versions).
+
+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. It may take a minute for all 3 services to pick up the new key. If the issue persists, contact Netwrix support for assistance with diagnosis and remediation.
diff --git a/docs/dataclassification/5.7/introduction/initialconfiguration/healthalert.md b/docs/dataclassification/5.7/introduction/initialconfiguration/healthalert.md
index a7090cd834..d5a15c07d3 100644
--- a/docs/dataclassification/5.7/introduction/initialconfiguration/healthalert.md
+++ b/docs/dataclassification/5.7/introduction/initialconfiguration/healthalert.md
@@ -6,7 +6,7 @@ sidebar_position: 50
# Configure Health Alerting
-On this step, you will be prompted to email settings for health reporting and select immediate
+On this step, you will be prompted to configure email settings for health reporting and select immediate
health alerts.
@@ -15,7 +15,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. |
+| 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](/docs/dataclassification/5.7/dashboards.md) for details on health monitoring. |
+| 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 want to receive: don't receive any alerts at all, only receive alerts for errors, or get emails for both errors and warnings. See [System Health](/docs/dataclassification/5.7/dashboards.md) for details on alert levels. |
+| Should a daily health summary be sent? | Select whether you want to receive a 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..0505cc502a 100644
--- a/docs/dataclassification/5.7/introduction/initialconfiguration/modes.md
+++ b/docs/dataclassification/5.7/introduction/initialconfiguration/modes.md
@@ -18,21 +18,21 @@ Review the short description below and select mode:
In this mode, the core search index will be disabled, heavily reducing the disk space requirements
for the CSE files and improving overall document throughput for classification. Under this mode
-Search is not available and Browse functionality is not subject to security trimming. Recommended
+Search isn't available and Browse functionality isn't subject to security trimming. Recommended
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. Note
+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, and 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..6b1aaaa453 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)](/docs/dataclassification/5.7/contentconfigurationoverview/taxonomies/clues/clues.md) for details on clue types. |
| 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 at the cost of increasing 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..c0c581a5b3 100644
--- a/docs/dataclassification/5.7/introduction/initialconfiguration/security.md
+++ b/docs/dataclassification/5.7/introduction/initialconfiguration/security.md
@@ -6,19 +6,16 @@ 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.
-- 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 (Strongly 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 for
+ full access, or restrict their access using the Users settings page.
- :::note
- Netwrix recommends enabling this option.
- :::
+ When selected, you will be prompted to add Super Users. Enter the name of any Super User you want to add and click + on
+ the right. Users with restricted access to NDC will need to be added via the Users configuration page after initial configuration is completed.
-
- When selected, you are prompted to add super users. Type the name of the new user and click + on
- the right.
-
-- Allow access for all users – select to allow any user access administrative web console.
+- Allow access for all users – select to allow any user to access the administrative web console. All users connecting to the web
+ interface will have full access, equivalent to a Super User.
diff --git a/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md b/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md
index 2637b035ef..968ce725c2 100644
--- a/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md
+++ b/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md
@@ -6,17 +6,16 @@ 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
-instructions on how to create a new database:
-[Create a Database](https://docs.microsoft.com/en-us/sql/relational-databases/databases/create-a-database).
+function properly. You can create the database manually before the product installation using SQL
+Server Management Studio or any tool that supports T-SQL (for example, sqlcmd). See the Microsoft article
+[Create a Database](https://docs.microsoft.com/en-us/sql/relational-databases/databases/create-a-database) for detailed instructions on creating a new database.
:::note
-For performance purposes, Netwrix strongly recommends to separate NDC and SQL Server
-machine.
+For performance purposes, Netwrix strongly recommends installing NDC and the SQL Server hosting
+the NDC database on separate servers.
:::
@@ -30,22 +29,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 preferred SQL client and connect to the
+SQL Server instance hosting the NDC database. Depending on your security
+setup, you may need to do this on the server itself.
+2. Open the properties window for the NDC database. In SQL Server Management Studio,
+select the database in the explorer tab on the left side of the window,
+right-click, and select Properties.
+3. Select the Files page and set the Initial Size (MB) for the PRIMARY file group to 512MB.
+4. Set the Autogrowth and Max Size for the PRIMARY file group as follows:
| Option | Description |
| ----------------- | -------------------------------------------------- |
- | File Growth | - Recommended—128 MB. - Large environment— 512 MB. |
+ | 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_".
+5. Select the Options page and ensure the Recovery model is set to "_Simple_".
:::note
- Netwrix recommends that you do not change the recovery model to avoid log files
+ Netwrix recommends that you don't 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..57fb7a36d3 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 will host the 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 doesn't yet exist, you will need to click **Create** to create the 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,27 @@ sidebar_position: 40
to [Configure NDC SQL database](/docs/dataclassification/5.7/introduction/install/ndcsqldatabase.md) section.
:::
+ :::note
+ When installing a secondary instance as part of a DQS environment, you may see an extra step here for synchronising the new instance with the primary instance.
+ The instructions for adding instances to a DQS environment can be found in [NDC Distributed Query Server](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md).
+ :::
-7. On the Licensing step, add license. You can add license as follows:
+7. 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.
+8. 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.
9. 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
@@ -58,6 +64,6 @@ 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. After 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..62083d0653 100644
--- a/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md
+++ b/docs/dataclassification/5.7/introduction/requirements/hardwarerequirements.md
@@ -16,37 +16,38 @@ on the corresponding virtualization platform, in particular:
- Microsoft Hyper-V
- Nutanix AHV
-Note that Netwrix Data Classification supports only Windows OS versions listed in the
+:::note
+Netwrix Data Classification supports only Windows OS versions listed in the
[Software Requirements](/docs/dataclassification/5.7/introduction/requirements/softwarerequirements.md) section.
+:::
## Netwrix Data Classification Server
The requirements in this section apply to a single Netwrix Data Classification server.
-To deploy a server cluster, make sure all planned cluster nodes meet the requirements listed below.
+To deploy a server cluster, ensure all planned cluster nodes meet the following requirements.
Consider deploying 1 Netwrix Data Classification Server per approx. 16, 000, 000 objects to process.
See [Deployment Planning](/docs/dataclassification/5.7/introduction/deployment/overview.md) and
-[Configuring NDC Servers Cluster and Load Balancing with DQS Mode](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md) for more information.
+[Configuring NDC Servers Cluster and Load Balancing with DQS Mode](/docs/dataclassification/5.7/introduction/deployment/ndcserverandclient/dqsmode.md) for cluster sizing guidance.
| Hardware Component | 1 Server per 16 M objects |
| ------------------ | ------------------------------ |
| 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 NDC Server instances in a DQS cluster. 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 _10 to 12KB_ 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,39 +66,34 @@ 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-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)
- The average number of emails per Mailbox or total number in all mailboxes.
-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.
+Run the following PowerShell script for the Exchange Management Shell to obtain the number of emails in all mailboxes. The script returns email stats for every mailbox. Use the script
+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 OneDrive**
-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. See the Microsoft article [Microsoft 365 Reports in the admin center](https://learn.microsoft.com/en-us/microsoft-365/admin/activity-reports/activity-reports?view=o365-worldwide) for additional information.
**Databases**
In case your scope includes databases, the following details are required:
-- Database type (MS SQL, Oracle, MySQL)
+- Database type (MS SQL, Oracle, MySQL, PostgreSQL)
- 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
@@ -110,8 +106,7 @@ Provide the total file count and storage usage from the BOX Admin Dashboard
**Plan the Production Deployment**
To size servers for your Netwrix Data Classification setup, use the metrics produced during the
-scoping stage. Apply the total number of files, documents, emails from all data sources to the table
-below to obtain corresponding hardware requirements.
+scoping stage. Apply the total number of files, documents, emails from all data sources to the following table to obtain corresponding hardware requirements.
:::warning
Netwrix Data Classification servers and SQL servers require high-performance SSD drives
diff --git a/docs/dataclassification/5.7/introduction/requirements/supportedcontenttypes.md b/docs/dataclassification/5.7/introduction/requirements/supportedcontenttypes.md
index 512ec284cf..8658a5b07b 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 file types NDC supports by default, 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..439e2470df 100644
--- a/docs/dataclassification/5.7/introduction/upgrade.md
+++ b/docs/dataclassification/5.7/introduction/upgrade.md
@@ -7,53 +7,69 @@ 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 to take advantage of new features and fixes.
## Upgrade Prerequisites
-Before you start the upgrade, it is strongly recommended to take the following steps:
+Before you start the upgrade, Netwrix strongly recommends taking the following steps:
-**Step 1 –** Make sure you have .NET Framework 4.7.2 installed on the computer where Netwrix Data
+**Step 1 –** Ensure you have .NET Framework 4.7.2 installed on the computer where Netwrix Data
Classification resides. If not, download it from Microsoft website:
[Download .NET Framework 4.7.2](https://dotnet.microsoft.com/download/dotnet-framework/net472).
-**Step 2 –** Back up NDC SQL database. It is recommended to do the following:
+**Step 2 –** Back up NDC SQL database. Netwrix recommends the following:
- Start Microsoft SQL Server Management Studio and connect to SQL Server instance hosting this
database.
- In the Object Explorer, right-click the database and select **Tasks** > **Back Up**.
- Wait for the process to complete.
-**Step 3 –** Back up the Index files. It is recommended to do the following:
+**Step 3 –** Back up the Index files. Netwrix recommends the following:
- 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.
+:::note
+For versions of 5.7 before 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.
+You can upgrade directly to Netwrix Data Classification 5.7 only 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.
+setup and follow the wizard steps. When finished, all solution components will be 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 uses the **Distributed Query Server** functionality to 5.7.10 or later,
+the primary server must be upgraded before upgrading the secondary instances. Secondary instances will
+attempt to resynchronize with the primary instance during the upgrade process, which will fail if the primary
+instance has not been upgraded.
+
+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 so that the installer can synchronize the DQS instances automatically.
+If this isn't done, you will need to perform a DQS resynchronization when upgrading each secondary DQS instance. For further details on this process,
+see the [Configuring NDC Servers Cluster and Load Balancing with DQS Mode](/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
-configuration, so you will be able to classify your data right after finishing the upgrade. However,
+During the upgrade from previous versions, Netwrix Data Classification preserves its
+configuration, so you can classify your data right after finishing the upgrade. However,
there are several steps you may need to take after upgrading.
-Follow the steps to update taxonomies manually.
+To update taxonomies manually:
**Step 1 –** In administrative web console, navigate to **Taxonomies** > **Global
-Settings**.Settings.
+Settings**.
**Step 2 –** Click **Update** in the right corner next to each taxonomy.
diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/administration/indexmaintenance/indexmaintenance.md b/docs/dataclassification/5.7/systemconfigurationoverview/administration/indexmaintenance/indexmaintenance.md
index 7ecbc62cab..ad206c31c5 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.
+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..d958dc91be 100644
--- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/communicationsettings.md
+++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/communicationsettings.md
@@ -15,19 +15,18 @@ 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. Use email servers 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 modified after initial configuration by selecting Edit, and new SMTP servers can be added by
selecting Add Email Server Configuration.
-The SMTP details should be entered based on the values provided by your network team. Each
-configuration supports both SSL enabled SMTP servers, and those without SSL enabled.
+The SMTP details should be entered based on the values provided by your network team.
+NDC supports SMTP servers with and without SSL configured. Anonymous SMTP server authentication is also supported.
-It is also possible to supply a test email address which will be used to test the configuration
-settings.
+You can supply a test email address to test the configuration settings
diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/configurendc.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/configurendc.md
index aee93b54c9..01e3a3c6d7 100644
--- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/configurendc.md
+++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/configurendc.md
@@ -6,7 +6,7 @@ sidebar_position: 70
# MIP Labels Configuration
-Netwrix Data Classification for Files and Folders supports MIP labels as Workflow action. Perform
+Netwrix Data Classification supports applying and removing MIP labels as a Workflow action. Perform
the following steps to enable MIP labels:
1. In administrative web console, navigate to System →Config . In the tree view go to System → MIP
@@ -18,12 +18,17 @@ the following steps to enable MIP labels:
| Client ID | Application (client) ID |
| Application Name | Display name |
| Tenant | Directory (tenant) ID |
- | Certificate Thumbprint | Provide certificate thumbprint you copied and stored on this step: [Upload the .CER file to Azure](/docs/dataclassification/5.7/introduction/introduction/configureinfrastructure.md). |
+ | Certificate Thumbprint | The certificate thumbprint you copied and stored on this step: [Upload the .CER file to Azure](/docs/dataclassification/5.7/introduction/introduction/configureinfrastructure.md). |
+ | Azure Cloud | The Azure Cloud instance to connect to. |
:::note
Any labels and policies in API should be migrated / synced with O365 Security &
-Compliance. Review the following Microsoft article for more information:
-[To migrate Azure Information Protection labels](https://docs.microsoft.com/en-us/azure/information-protection/configure-policy-migrate-labels#to-migrate-azure-information-protection-labels)
+Compliance. See the Microsoft article
+[To migrate Azure Information Protection labels](https://docs.microsoft.com/en-us/azure/information-protection/configure-policy-migrate-labels#to-migrate-azure-information-protection-labels) for migration instructions.
+:::
+
+:::note
+Select **Public** for the majority of Azure tenancies, including Government Community Cloud (GCC). Select **U.S. Government** for GCC High and Department of Defense (DoD) tenancies.
:::
diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/administration.md
index 2fb3677ee7..82e6ffc98c 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.
@@ -19,28 +19,28 @@ Nearly each configuration option has an associated “i” which describes the n
| Option | Description | Comment |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **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. | |
+| Report Source Filter Mode | Use to add an additional filter for either Source Groups (default) or Sources | |
| 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 Documents | When this is enabled, documents marked as deleted will be automatically expunged 7 days after the last collection attempt. | Documents marked as deleted manually (i.e. via the NDC UI) or by the source file watchers may be expunged in fewer than 7 days after being marked as deleted, as these processes don't update 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. |
-| AD Groups Lookup Enabled | Allows you to enable/disable the use of AD groups in User Manager. This option is disabled by default. | It is recommended to keep this option disabled unless AD group support is specifically required. To learn more about User Manager in Netwrix Data Classification, see [User Management](/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md) |
+| Administration URL | URL of the web-based management console. The default URL is _http://localhost/NDC_. | If necessary, specify another Netwrix standalone server or cluster server instead of local host. You can use server name or IP address. |
+| AD Groups Lookup Enabled | Use to enable/disable the use of AD groups in User Manager. This option is disabled by default. | Keep this option disabled unless AD group support is specifically required. For details on User Manager in Netwrix Data Classification, see [User Management](/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md) |
## Taxonomies
-These settings allow you to customize configuration of classification taxonomies.
+Use these settings 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 create 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: - The **Term Level** is used if a different working set is required for each class.
- If **Taxonomy Level** is selected then the same working set shall be used for all classes in the taxonomy.
| 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). | |
@@ -51,12 +51,12 @@ These settings allow you to customize configuration of classification taxonomies
## Concept Classifier App
-These settings allow you to customize configuration of Concept Classifier app.
+Use these settings to customize configuration of Concept Classifier app.
| Option | Description | Comment |
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| **General settings** | | |
-| Enable Near Duplicate Detection | The relevance threshold for duplicate detection matching (when using the Duplicates link from the SharePoint ribbon). When set to 100%, this option will utilize an exact match (matching checksum). When set to a lower threshold, a fuzzy match will be attempted to locate near duplicates. | Applies only to the deployment with the SharePoint add-in. |
+| Enable Near Duplicate Detection | The relevance threshold for duplicate detection matching (when using the Duplicates link from the SharePoint ribbon). When set to 100%, this option will use an exact match (matching checksum). When set to a lower threshold, a fuzzy match will be attempted to locate near duplicates. | Applies only to the deployment with the SharePoint add-in. |
| Duplicate Detection Scope | Enables/disables scoping of duplicates detected via the SharePoint add-in interface. When disabled, duplicates wil be identified anywhere in the index. When enabled, duplicates will be scoped to their source group (or if no source group available | Applies only to the deployment with the SharePoint add-in. |
| **Advanced settings** | | |
| Duplicate Detection Archive Indicator | Identifies documents within the View Duplicates display that are tagged with the archive indicator. These identified documents can be optionally filtered from the display. | |
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..73c85f2ff9 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.
:::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.
:::
@@ -31,5 +30,5 @@ You can also use the following option buttons:
- Start Product Tour—Run a product tour taking you around the key areas of the product.
- Run Cleaner—Run built-in tool to automate maintenance operations.
- [See Index Maintenance for more information.](/docs/dataclassification/5.7/systemconfigurationoverview/administration/indexmaintenance/indexmaintenance.md)
+ See [Index Maintenance](/docs/dataclassification/5.7/systemconfigurationoverview/administration/indexmaintenance/indexmaintenance.md) for instructions on using the Index Cleaner tool.
- Reset Cache—Force the QS caches to be reset.
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..cd07020387 100644
--- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/conceptclassifier.md
+++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/conceptclassifier.md
@@ -7,10 +7,10 @@ sidebar_position: 30
# conceptClassifier App Options
This section contains the settings related to conceptClassifier application. As these are advanced
-options, you should click the screwdriver icon at **Settings** in the bottom-right corner to view
+options, you should click the wrench 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.
@@ -24,7 +24,7 @@ The following options can be configured for conceptClassifier app:
| Option | Description | Comment |
| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- |
-| Write Mode | Allows you to configure the update method that will be used by the Classification service to update SharePoint documents. Possible options: - **Alter audit information**
- Simple Update operation
- **Maintain audit information**
- ValidateUpdateListItem operation
- **Maintain audit information with no alerts (O365 only)**
- SystemUpdate operation
| Applies to SharePoint documents. |
+| Write Mode | Use to configure the update method that will be used by the Classification service to update SharePoint documents. Possible options: - **Alter audit information**
- Simple Update operation
- **Maintain audit information**
- ValidateUpdateListItem operation
- **Maintain audit information with no alerts (O365 only)**
- SystemUpdate operation
| Applies to SharePoint documents. |
| Manually Classify Cleared Fields | When enabled, fields will be marked as manually classified if the user clears them. If disabled, auto classification must be manually turned off by the user to stop the field being updated. | |
| Hide Sql (Local) Taxonomy Calculations | When disabled, any classifications/calculations will be hidden from the SharePoint View Classifications display (Classic and Modern UI). | |
| Ignore Manual Classifications From | A semicolon-delimetered list of usernames. Any updates to classification of new documents in SharePoint by these users will be ignored. | |
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..84f09549c9 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.
@@ -23,10 +23,10 @@ has an indication of the values that have been changed from the default setting.
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **General settings** | | |
| Boosted Phrasematch Scoring | Automatically boosts the score of Phrasematch clues when the phrase occurs multiple times in the same document. | |
-| 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. |
+| Boosted Regex Scoring | Automatically boosts the score of Regex clues when the regular expression matches multiple occurrences in the same document. | Selecting this option isn't 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. | |
+| 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, Netwrix recommends 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 values. Use this option if you want to only extract values for clues on nodes that have achieved their threshold for classification. | |
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..acb6d5d57e 100644
--- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/generaloptions.md
+++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/generaloptions.md
@@ -7,16 +7,15 @@ sidebar_position: 10
# General Options
The **General** section contains general classification engine settings, e.g. . By default, only
-standard options are displayed. To view advanced options, click the screwdriver icon at **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.
:::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,15 +24,15 @@ 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: - up to **256** — for 32-bit Windows
- up to **1024** — for 64-bit Windows
| 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: - **Retain if not classified** — leave existing classification in place if no auto-classification has been generated
- **Overwrite** — clear managed metadata fields
| Applies to SharePoint source. |
+| Max Categories | Sets the maximum number of classifications to be allocated to each document: - up to **256** — for 32-bit Windows
- up to **1024** — for 64-bit Windows
| 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: - **Retain if not classified** — leave existing classification in place if no auto-classification has been generated
- **Overwrite** — clear managed metadata fields
| 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) |
+| Classifier Threads | The number of background threads used for classification. Default is **0 (auto)**. | Netwrix recommends leaving this setting on its default value. See the Knowledge Base article [Classifier and Write Thread Tuning](https://kb.netwrix.com/3863) for details on tuning thread counts. |
+| Classifier Write Threads | The number of threads to be used by the Classifier to update source systems during "tagging" operations (i.e. writing classifications back to source systems). | Each thread can be considered a "user" when considering load on the source system. See the Knowledge Base article [Classifier and Write Thread Tuning](https://kb.netwrix.com/3863) for details on tuning write thread counts. |
| **Advanced settings** | | |
|  | | |
| Classifier Enabled | Enables / disables the Classifier core component. By default, it is enabled. | |
-| SharePoint EMM No Classify Mode | Possible values: - **Do not update Deprecated** (default) — use if you do not want to alter the **Deprecated** setting in SharePoint EMM
- **Update Deprecated** — select if you want Deprecated setting to be updated
| |
+| SharePoint EMM No Classify Mode | Possible values: - **Don't update Deprecated** (default) — use if you don't want to alter the **Deprecated** setting in SharePoint EMM
- **Update Deprecated** — select if you want Deprecated setting to be updated
| |
| Subset Trimming Enabled | This setting applies where both primary (single value) and secondary (multi value) fields are added to a document library for the same taxonomy. - **Off** (default) — the highest scoring term will be shown in both primary and secondary fields.
- **On** — the highest scoring term will be shown only in the primary field.
| |
| Subset Trimming Threshold | If **Subset Trimming Enabled** option is ON, this parameter defines the minimum score required to class the highest scoring term as primary. | If no item has a score higher than this threshold, then all terms will show as secondary terms, and the primary term will be empty. |
| Classifier Delay | The sleep time (in milliseconds) between intensive operations, such as storing classification. Default is **1** ms. | |
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..8a0bc9fadb 100644
--- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/monitoredcontent.md
+++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/classifier/monitoredcontent.md
@@ -13,15 +13,14 @@ conditions are met, or with a minimum time period between runs.
:::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.
:::
| Option | Description | Comment |
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
-| Monitored Document Indicator | Content will be marked for automatic re-classification if it is tagged with a particular term. | Click on the tag icon to select the term that should be used to identify monitored content. |
-| Minimum Reclassification Regularity (days) | Defines the minimum period to be used when re-classifying monitored content: from _1_ to _180_ days, default is **1** day. | Content will be marked for reclassification if it was last classified prior to the specified regularity period. |
+| Monitored Document Indicator | Content will be marked for automatic re-classification if it is tagged with a particular term. | Click the tag icon to select the term that should be used to identify monitored content. |
+| Minimum Reclassification Regularity (days) | Defines the minimum period to be used when re-classifying monitored content: from _1_ to _180_ days, default is **1** day. | Content will be marked for reclassification if it was last classified before the specified regularity period. |
To re-classify content that meets specific conditions:
@@ -29,7 +28,7 @@ To re-classify content that meets specific conditions:
particular term.
2. In the **Monitored Content** section of **System Configuration > Core > Classifier** locate
**Monitored Document Indicator**.
-3. Click on the tag icon, and in the **Select Term** dialog specify the term that should be used to
+3. Click the tag icon, and in the **Select Term** dialog specify the term that should be used to
identify monitored content:
4.
When finished, click **Select**, then in the Classifier settings window click **Save**,
@@ -39,5 +38,5 @@ To re-classify content with a minimum time period between runs:
1. In the **Monitored Content** section of **System Configuration > Core > Classifier** settings
window locate **Minimum Reclassification Regularity**.
2. Default reclassification period is 1 day. Use the slider to adjust the value. Content will be
- marked for reclassification if it was last classified prior to the specified period.
+ marked for reclassification if it was last classified before the specified period.
3. Click **Save**.
diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/collector.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/collector.md
index a9a465e1df..9319ca259f 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.
@@ -16,9 +15,9 @@ associated “i” which describes the nature of the setting.
| **General settings** | | |
| Max Document Size | Sets the maximum size of the document to be processed. | Documents exceeding this size will typically be excluded from processing. |
| Collect Metadata of Excluded Items | When enabled, the Netwrix Data Classification services will include the document, but from a metadata standpoint only (no text will be extracted from the file). | Used in combination with the "Max Document Size" value. Inactive by default. |
-| Collector Threads | The number of overall background threads to be utilized by the Collector to access content from the 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). |
-| Collector Domain Threads | The number of threads to be utilized by the Collector to access content from each HTTP domain. (Examples: netwrix.com, google.com, microsoft.com, etc.) The number will be automatically capped by the "Collector Threads" value. | Applies to HTTP source types only. 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). |
-| Collector File Threads | The number of threads used to crawl file system content. | For more information, see [this Knowledge Base article](https://kb.netwrix.com/3863). |
+| Collector Threads | The number of overall background threads to be used by the Collector to access content from the source system. | Each thread can be considered a "user" when considering load on the source system. See the [Knowledge Base article on thread tuning](https://kb.netwrix.com/3863). |
+| Collector Domain Threads | The number of threads to be used by the Collector to access content from each HTTP domain. (Examples: netwrix.com, google.com, microsoft.com, etc.) The number will be automatically capped by the "Collector Threads" value. | Applies to HTTP source types only. Each thread can be considered a "user" when considering load on the source system. See the [Knowledge Base article on thread tuning](https://kb.netwrix.com/3863). |
+| Collector File Threads | The number of threads used to crawl file system content. | See the [Knowledge Base article on thread tuning](https://kb.netwrix.com/3863) for details on adjusting file thread counts. |
| Process Document Images | If enabled, images will be extracted from supported documents (Office XML files and PDFs). These images will be then collected, and any text found will be included (with the document text) for classification. | For this setting to be applied, OCR must also be enabled at a content type level — to ensure that the extracted images are run through the OCR engine. This setting is inactive by default. |
| Maximum Images per Document | Maximum amount of images to process through OCR on a per document basis. | |
| Minimum Image Resolution Width | Minimum resolution (in pixels) of images to process through OCR. | |
@@ -29,8 +28,8 @@ associated “i” which describes the nature of the setting.
| Collector User Agent | Is used by Collector service as part of each web request made when crawling HTTP sources — to identify itself to the crawled systems. | |
| Encrypt Text (text.cse) | Encrypts all data stored in **text.cse** (raw document extracts). | Inactive by default. If data already exists in the index, then to enable encryption on that existing data, you should perform re-collection. For that, click **Run Cleaner** button on the right. |
| Optimize Text Storage | Reduces storage requirements for stored text. | Enabled by default. At each re-crawl or re-index the program tries to detect whether the document text has changed. |
-| Re-use Text Offsets | Reduces storage requirements for stored text by sharing and reusing the stored text. | May slightly increase the SQL demands — in order to process each de-duplication command. |
+| Re-use Text Offsets | Reduces storage requirements for stored text by sharing and reusing the stored text. | May slightly increase the demand on the NDC database while processing each de-duplication command. |
| Collector Delay | The sleep time (in milliseconds) between intensive operations, such as storing crawled text. Default is **1** ms. | |
-| Collector Polling | The sleep time (in seconds) between Collector batches. | Only utilized when the Collector queue is empty. |
+| Collector Polling | The sleep time (in seconds) between Collector batches. | Only used when the Collector queue is empty. |
| iFilter Processing Mode | Specify where the iFilter processing will run. Possible options: **Process as Sub Process** — run in a separate process **Process Internally** — run within Collector process | |
-| Collector Reader Process Pool Size | The number of external processes that will be utilized for iFilter conversion. | Each additional process adds additional load on the Netwrix Data Classification server. We recommend leaving this setting on its default value. For more information, see [this Knowledge Base article](https://kb.netwrix.com/3863). |
+| Collector Reader Process Pool Size | The number of external processes that will be used for iFilter conversion. | Each additional process increases the load on the Netwrix Data Classification server. Netwrix recommends leaving this setting on its default value. See the [Knowledge Base article on thread tuning](https://kb.netwrix.com/3863) for further details. |
diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/coreconfiguration.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/coreconfiguration.md
index 281ac32df1..69684ca3ee 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.
@@ -14,5 +14,5 @@ You can also:
- Start Product Tour—Runs a product tour, taking you around the key areas of the product.
- Run Cleaner—Runs built-in tool to automate maintenance operations.
- [See Index Maintenance for more information.](/docs/dataclassification/5.7/systemconfigurationoverview/administration/indexmaintenance/indexmaintenance.md)
+ See [Index Maintenance](/docs/dataclassification/5.7/systemconfigurationoverview/administration/indexmaintenance/indexmaintenance.md) for instructions on using the Index Cleaner tool.
- Reset Cache—Force the QS caches to be reset.
diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/indexer.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/indexer.md
index 24d1c4c94a..715662ae2e 100644
--- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/indexer.md
+++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/indexer.md
@@ -6,18 +6,17 @@ 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
-screwdriver icon at **Settings** on the right.
+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
+wrench icon at **Settings** on the right.
| Option | Description | Comment |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **General settings** | | |
-| Indexer Threads | The number of background threads used for the indexer's processing. 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) |
+| Indexer Threads | The number of background threads used for the indexer's processing. Default is _0_ (auto). | Netwrix recommends leaving this setting on its default value. See the Knowledge Base article [Classifier and Write Thread Tuning](https://kb.netwrix.com/3863) for details on thread tuning. |
| Near Duplicate Detection Enabled | With this option enabled, the Indexer will attempt a fuzzy match to locate near duplicates within the index (as a background action). These can then be reviewed via the **Near Duplicate Detection** report. | By default, duplicate detection will be based purely on an exact match (matching checksum). |
| **Advanced settings** | | |
| Indexer Delay | The sleep time (in milliseconds) between intensive operations (for example, extracting terms). Default is _1_ millisecond. | |
-| Indexer Polling | The sleep time between Indexer batches. | Only utilised when the indexing queue is empty. |
+| Indexer Polling | The sleep time between Indexer batches. | Only used when the indexing queue is empty. |
| DocumentID`` Mapping | Used to map fields into the search index ID references. Allows for custom queries based on external IDs against the SOAP search API calls. | Theses are ID3 — ID8 |
diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/system.md b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/coreconfiguration/system.md
index 1f0de51bd7..b9da345f7f 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.
@@ -16,14 +15,14 @@ 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: - **Errors**
- **Errors & Warnings**
- **Errors Warnings & Info**
- **Verbose**
| |
-| 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_ |
-| 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. |
+| Log Level | Defines logging level that should be persisted to the log targets. Supported levels: - **Errors**
- **Errors & Warnings**
- **Errors Warnings & Info**
- **Verbose**
| |
+| 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 | The default file log location is shown here. This value can't be modified. | The default location is C:\ProgramData\Netwrix Data Classification\Logs |
+| File Log Retention Period | Number of days a file log is kept after its last write before being deleted. | 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 about 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). |
+| Max Database Size | Specifies the max size (in GB) the SQL database will grow to. | When this value is reached, the 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..56620719cf 100644
--- a/docs/dataclassification/5.7/systemconfigurationoverview/configuration/texthandling.md
+++ b/docs/dataclassification/5.7/systemconfigurationoverview/configuration/texthandling.md
@@ -19,18 +19,18 @@ This section contains information on how to configure text processing. Related o
[](#)Best Bets
-Sometimes an application may wish to push selected documents to the top of a hitlist for specific
+Sometimes an application may want to push selected documents to the top of a hitlist for specific
queries. This may be implemented by specifying Best Bets for specific query text.
-First, enter the search term that you wish to match and then click the Add button.
+First, enter the search term that you want to match and then click the Add button.
-Next, click on the term, and specify one or more URLs that should appear at the top of the hit list.
+Next, click the term, and specify one or more URLs that should appear at the top of the hit list.
[](#)Content Type Extension Mapping
-Sometimes an organization may wish to process certain file types as a different content type. The
+Sometimes an organization may want to process certain file types as a different content type. The
primary use case for this is internal content types that map to a content type already understood /
identified.
@@ -45,12 +45,12 @@ The Content Type Extraction methods describes how documents will be handled by t
services. A number of built-in processing methods are available, where there is no available method
the processing will default to running through standard Microsoft Search iFilter processing.
-The methods can be easily altered by clicking Edit and then selecting the preferred processing
-method. It is also possible to specify that an iFilter should be utilised if the primary method
+You can alter the methods by clicking Edit and then selecting the preferred processing
+method. You can also specify an iFilter as a backup if the primary method
fails to extract text from the document – the backup method will be used if the extraction fails to
find more than 5 characters of text.
-If you have updated the extraction method we recommend re-processing any documents that have already
+If you have updated the extraction method, Netwrix recommends re-processing any documents that have already
been processed to ensure consistency. Selecting Re-index from the grid for the affected content type
will re-process the necessary records.
@@ -62,12 +62,12 @@ The language detection list specifies which languages will be considered for aut
-If a language is excluded then it cannot be used to identify the language of a document and it will
+If a language is excluded then it can't be used to identify the language of a document and it will
be removed from the language options in Taxonomy Manager.
-**TIP:** You can also OCR recognition for non-English images. Refer to the following Netwrix
-knowledge base article for more information:
-[How to enable OCR for non-English images](https://kb.netwrix.com/3519).
+:::tip
+You can also enable OCR recognition for non-English images. See the Netwrix knowledge base article [How to enable OCR for non-English images](https://kb.netwrix.com/3519) for setup instructions.
+:::
[](#)No Stem
@@ -79,14 +79,16 @@ 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 OCR language mapping configuration screen can be used if you want to OCR non-English images using
+Tesseract and the Apache Tika OCR engine. File paths (including parts of paths) can be mapped to specific Tesseract language packs.
+You can also override the OCR processing mode, enable conversion of PDF files to images for improved text extraction, and override
+the Page Segmentation mode used by Tika to identify text.
[](#)Synonyms
-Often it is important to submit a query and have synonyms automatically included. A generic set of
+Often you need to submit a query and have synonyms automatically included. A generic set of
synonyms may be configured by using the Synonyms form.
@@ -98,20 +100,20 @@ for all pages and/or not relevant to the individual page content. If all of the
these HTML pages then this can lead to unwanted search results where a match is made, for example,
to an entry in a standard page navigation area.
-The Text Patterns feature is provided to assist with the cleanup of HTML documents. TextPatterns can
-also be used to index terms that would normally be discarded.
+The Text Patterns feature is provided to assist with the cleanup of HTML documents. Use TextPatterns
+to also index terms that would normally be discarded.
The StartTag and EndTag values are case sensitive strings used to identify the content to be
managed, the content is then managed based on the filter type.
-There are three tag types that can be used to assist in the cleanup:
+You can use three tag types to assist in the cleanup:
-- FILTER—Extracts a subset of the HTML page, prior to extracting the plain text. Only a single
+- FILTER—Extracts a subset of the HTML page, before extracting the plain text. Only a single
section will be extracted for each TextFilter processed.
-- DELETE—Deletes sections of the HTML page, prior to extracting the plain text.
+- DELETE—Deletes sections of the HTML page, before extracting the plain text.
- INDEX TERM (EndTag ignored)—Create index terms that would otherwise not be formed. For example the
term “E.ON” is a useful one for people interested in energy companies. However, this term would
- not normally be created because a full stop normally acts as a term separator. However, if we
- create an INDEX TERM for this pattern then it will be detected and indexed as required.
+ not normally be created because a full stop normally acts as a term separator. However, creating
+ an INDEX TERM for this pattern means it will be detected and indexed as required.
diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/users/passwordmanager.md b/docs/dataclassification/5.7/systemconfigurationoverview/users/passwordmanager.md
index 0acecea1f9..2aec7bd8b8 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
+Use the Password Manager 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.
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
-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.
+either click Edit to change a specific password or click Add Password to add a new password for the
+account. You can't have overlapping date ranges for the defined passwords, and you can't 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..b52cede01f 100644
--- a/docs/dataclassification/5.7/systemconfigurationoverview/users/securendc.md
+++ b/docs/dataclassification/5.7/systemconfigurationoverview/users/securendc.md
@@ -6,19 +6,19 @@ sidebar_position: 10
# Secure Netwrix Data Classification
-The steps described within this article can be used to review the security of your Netwrix Data
+Use the steps described within this article to review the security of your Netwrix Data
Classification deployment and apply any changes you feel necessary to secure the administration of,
and access to, the Classification interfaces.
## Configure Administration Console Access
By default, post installation, all users will be considered Superusers with access to all areas of
-the product. To begin the process of securing the product please follow the below steps:
+the product. To begin the process of securing the product, follow these 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
+4. Your username will be pre-filled and must first be added to ensure that you don't lose access to
the system.
5. You can now add other users / groups as required - either as Superusers, or with access to
specific areas / functions
@@ -42,13 +42,13 @@ the back-end SQL Server database:
- C:\Program Files\Netwrix\Data Classification\Services\ConceptCollectorService
- C:\Program Files\Netwrix\Data Classification\Services\conceptIndexer
- 2. Check the Encrypt Connection box as well as the Trust Server Certificate box if you do not
+ 2. Check the Encrypt Connection box as well as the Trust Server Certificate box if you don't
have a valid certificate loaded for SQL Server.
3. Click Save.
- Transparent Data Encryption (TDE)—Protects your data at rest within SQL Server. Netwrix Data
- Classification supports the use of TDE, it should of course be noted that this does incur a
- performance overhead. TDE should be managed and configured by your database administrator(s).
+ Classification supports the use of TDE; however, this incurs a performance overhead. Your database
+ administrators should manage and configure TDE.
## Secure Search Index (CSE File)
@@ -59,24 +59,23 @@ groupings to this engine:
- All other files—Stores the compound term processing search index, identifying which documents
should be returned for a given query
-Text.cse can be optionally encrypted, this utilises AES/SHA256 to further improve the security of
-the full text at rest. You can enable this mode by:
+Text.cse can be optionally encrypted using AES/SHA256 to further improve the security of the full text at rest. You can enable this 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);
-4. Select Save.
+1. Accessing the Administration Console.
+2. Selecting **Config** from the top navigation bar.
+3. On the Collector tab, enabling the **Encrypt Text** (Text.cse) option (this is an advanced setting -
+select the wrench icon in the bottom left to display it).
+4. Selecting **Save**.
-The remaining 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 other index files can't be reverse-engineered to retrieve the full document text - however, they do
+contain the weightings and terms within the text. Netwrix recommends restricting access to all files at
the file system level as well as considering file system encryption.
## Review Web Service Endpoints
There are several web service endpoints which provide access to various levels of information within
Netwrix Data Classification. If you are exposing the administration interface to the internet then
-you may wish to fully restrict access to these endpoint(s) via your firewall or IIS Configuration
+you may want to fully restrict access to these endpoints via your firewall or IIS Configuration
(potentially removing all external access).
The following paths should be considered as part of this process:
@@ -85,6 +84,6 @@ The following paths should be considered as part of this process:
- \*.asmx
- \*.svc
-It should be noted that when using Netwrix Data Classification for SharePoint Online certain
-endpoints are required, each of these endpoints are located within the folder
+When using Netwrix Data Classification for SharePoint Online, certain
+endpoints are required. Each of these endpoints is located within the folder
"_/ConceptClassifierApp/_".
diff --git a/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md b/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md
index 59f0f7129f..5e33c11d83 100644
--- a/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md
+++ b/docs/dataclassification/5.7/systemconfigurationoverview/users/usermanagement.md
@@ -11,12 +11,12 @@ permissions and manage existing users.
## Authentication Mechanisms
-On first install the QS will be configured for Windows authentication. To setup the QS to use an
-ADFS server please follow the "Installation and Configuration" guide using the section "ADFS". To
-use forms based authentication please disable all other authentication methods in IIS other than:
+On first install, the QS will be configured for Windows authentication. To set up the QS to use an
+ADFS server, follow the "Installation and Configuration" guide using the section "ADFS". To
+use forms based authentication, disable all other authentication methods in IIS other than:
Anonymous and Forms:
-Follow the steps to use authentication forms.
+To use authentication forms:
**Step 1 –** Check that the “authentication mode” setting in conceptQS/web.config file is set as
follows:
@@ -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.
-**Step 3 –** If you wish to allow anonymous access to the conceptQS, edit the conceptQS web.config
+**Step 3 –** If you want to allow anonymous access to NDC, edit the conceptQS web.config
file and delete (or comment out) three lines: