Merge pull request #270 from nwx-natew/natew-na-requirements-corrections

NA 10.8 requirements overview document updates/corrections

Author: TheNewCat777

docs/auditor/10.8/requirements/overview.md

@@ -3,7 +3,6 @@ title: "Requirements"
 description: "Requirements"
 sidebar_position: 20
 ---
-
 # Requirements
 
 This topic provides the requirements for the server where Netwrix Auditor will be installed. See the
@@ -25,25 +24,26 @@ product architecture and components interactions are shown in the figure below.
   processing of audit data from the various data sources (audited systems). Data from the sources
   not yet supported out of the box is collected using RESTful Integration API.
 - Netwrix Auditor Client — a component that provides a friendly interface to authorized personnel
-  who can use this console UI to manage the product settings, examine alerts, reports and search
+  who can use this console UI to manage product settings, examine alerts, reports and search
   results. Other users can obtain audit data by email or with 3rd party tools — for example, reports
-  can be provided to the management team via the intranet portal.
+  can be provided to the management team via the intranet portal. The Client may be installed on
+  other hosts using the same installer as the server.
 - Data sources — entities that represent the types of audited systems supported by Netwrix Auditor
   (for example, Active Directory, Exchange Online, NetApp storage system, and so on), or the areas
   you are interested in (Group Policy, User Activity, and others).
-- Long-Term Archive — a file-based repository storage keeps the audit data collected from all your
+- Long-Term Archive — a file-based storage repository that keeps the audit data collected from all your
   data sources or imported using Integration API in a compressed format for a long period of time.
-  Default retention period is 120 months.
+  Default retention period is **120 months**.
 - Audit databases — these are Microsoft SQL Server databases used as operational storage. This type
   of data storage allows you to browse recent data, run search queries, generate reports and
   alerts.
   Typically, data collected from the certain data source (for example, Exchange Server) is stored to
   the dedicated Audit database and the long-term archive. So, you can configure as many databases as
   the data sources you want to process. Default retention period for data stored in the Audit
-  database is 180 days
+  database is **180 days**.
 
 **NOTE:** When auditing Active Directory domains, Exchange servers, expired passwords, and inactive
-users, the data sent by the product can be encrypted using Signing and Sealing. See the following
+users, the data sent by the product can be encrypted using [Signing and Sealing](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/enable-ldap-signing-in-windows-server). See the following
 Netwrix knowledge base article for additional information on how to secure Netwrix Auditor:
 [Best Practices for Securing Netwrix Auditor](https://helpcenter.netwrix.com/bundle/z-kb-articles-salesforce/page/kA00g000000H9SPCA0.html).
 
@@ -52,18 +52,17 @@ Netwrix knowledge base article for additional information on how to secure Netwr
 The general workflow stages are as follows:
 
 - Authorized administrators prepare IT infrastructure and data sources they are going to audit, as
-  recommended in Netwrix Auditor documentation and industry best practices; they use Netwrix Auditor
+  recommended in Netwrix Auditor documentation and industry best practices; they use the Netwrix Auditor
   Client (management UI) to set up automated data processing.
 - Netwrix Auditor collects audit data from the specified data source (application, server, storage
   system, and so on).
 
-    - To provide a coherent picture of changes that occurred in the audited systems, the product can
-      consolidate data from multiple independent sources (event logs, configuration snapshots,
-      change history records, etc.). This capability is implemented with Netwrix Auditor Server and
-      Integration API.
-    - See the [Integration API](/docs/auditor/10.8/api/overview.md) topic for additional information on custom data
-      source processing workflow.
-
+  - To provide a coherent picture of changes that occurred in the audited systems, the product can
+    consolidate data from multiple independent sources (event logs, configuration snapshots,
+    change history records, etc.). This capability is implemented with Netwrix Auditor Server and
+    Integration API.
+  - See the [Integration API](/docs/auditor/10.8/api/overview.md) topic for additional information on custom data
+    source processing workflow.
 - Audit data is stored to the Audit databases and the repository (Long-Term Archive) and preserved
   there according to the corresponding retention settings.
 - Netwrix Auditor analyzes the incoming audit data and alerts appropriate staff about critical