You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/auditor/10.8/requirements/overview.md
+11-12Lines changed: 11 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,6 @@ title: "Requirements"
3
3
description: "Requirements"
4
4
sidebar_position: 20
5
5
---
6
-
7
6
# Requirements
8
7
9
8
This topic provides the requirements for the server where Netwrix Auditor will be installed. See the
@@ -27,23 +26,24 @@ product architecture and components interactions are shown in the figure below.
27
26
- Netwrix Auditor Client — a component that provides a friendly interface to authorized personnel
28
27
who can use this console UI to manage the product settings, examine alerts, reports and search
29
28
results. Other users can obtain audit data by email or with 3rd party tools — for example, reports
30
-
can be provided to the management team via the intranet portal.
29
+
can be provided to the management team via the intranet portal. The Client may be installed on
30
+
other hosts using the same installer as the server.
31
31
- Data sources — entities that represent the types of audited systems supported by Netwrix Auditor
32
32
(for example, Active Directory, Exchange Online, NetApp storage system, and so on), or the areas
33
33
you are interested in (Group Policy, User Activity, and others).
34
34
- Long-Term Archive — a file-based repository storage keeps the audit data collected from all your
35
35
data sources or imported using Integration API in a compressed format for a long period of time.
36
-
Default retention period is 120 months.
36
+
Default retention period is **120 months**.
37
37
- Audit databases — these are Microsoft SQL Server databases used as operational storage. This type
38
38
of data storage allows you to browse recent data, run search queries, generate reports and
39
39
alerts.
40
40
Typically, data collected from the certain data source (for example, Exchange Server) is stored to
41
41
the dedicated Audit database and the long-term archive. So, you can configure as many databases as
42
42
the data sources you want to process. Default retention period for data stored in the Audit
43
-
database is 180 days
43
+
database is **180 days**.
44
44
45
45
**NOTE:** When auditing Active Directory domains, Exchange servers, expired passwords, and inactive
46
-
users, the data sent by the product can be encrypted using Signing and Sealing. See the following
46
+
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
47
47
Netwrix knowledge base article for additional information on how to secure Netwrix Auditor:
48
48
[Best Practices for Securing Netwrix Auditor](https://helpcenter.netwrix.com/bundle/z-kb-articles-salesforce/page/kA00g000000H9SPCA0.html).
49
49
@@ -57,13 +57,12 @@ The general workflow stages are as follows:
57
57
- Netwrix Auditor collects audit data from the specified data source (application, server, storage
58
58
system, and so on).
59
59
60
-
- To provide a coherent picture of changes that occurred in the audited systems, the product can
61
-
consolidate data from multiple independent sources (event logs, configuration snapshots,
62
-
change history records, etc.). This capability is implemented with Netwrix Auditor Server and
63
-
Integration API.
64
-
- See the [Integration API](/docs/auditor/10.8/api/overview.md) topic for additional information on custom data
65
-
source processing workflow.
66
-
60
+
- To provide a coherent picture of changes that occurred in the audited systems, the product can
61
+
consolidate data from multiple independent sources (event logs, configuration snapshots,
62
+
change history records, etc.). This capability is implemented with Netwrix Auditor Server and
63
+
Integration API.
64
+
- See the [Integration API](/docs/auditor/10.8/api/overview.md) topic for additional information on custom data
65
+
source processing workflow.
67
66
- Audit data is stored to the Audit databases and the repository (Long-Term Archive) and preserved
68
67
there according to the corresponding retention settings.
69
68
- Netwrix Auditor analyzes the incoming audit data and alerts appropriate staff about critical
0 commit comments