Fix misleading automatic-config claim in network device docs

docs/auditor/10.7/configuration/networkdevices/ciscoasa.md

@@ -6,37 +6,27 @@ sidebar_position: 20
 
 # Configure Cisco ASA Devices
 
-Netwrix Auditor relies on native logs for collecting audit data. Therefore, successful change and
-access auditing requires a certain configuration of native audit settings in the audited environment
-and on the Auditor console computer. Configuring your IT infrastructure may also include enabling
-certain built-in Windows services, etc. Proper audit configuration is required to ensure audit data
-integrity, otherwise your change reports may contain warnings, errors or incomplete audit data.
-
-**CAUTION:** Folder associated with Netwrix Auditor must be excluded from antivirus scanning. See
-the
+Netwrix Auditor relies on native syslog events for collecting audit data. Therefore, successful
+change and access auditing requires a certain configuration of native audit settings in the audited
+environment. Proper audit configuration ensures audit data integrity; otherwise, your change reports
+may contain warnings, errors, or incomplete audit data.
+
+**CAUTION:** Exclude the folder associated with Netwrix Auditor from antivirus scanning. See the
 [Antivirus Exclusions for Netwrix Auditor](/docs/kb/auditor/system-administration/security-hardening/antivirus-exclusions-for-netwrix-auditor)
 knowledge base article for additional information.
 
-You can configure your IT Infrastructure for monitoring in one of the following ways:
-
-- Automatically through a monitoring plan – This is a recommended method. If you select to
-  automatically configure audit in the target environment, your current audit settings will be
-  checked on each data collection and adjusted if necessary.
-- Manually – Native audit settings must be adjusted manually to ensure collecting comprehensive and
-  reliable audit data. You can enable Auditor to continually enforce the relevant audit policies or
-  configure them manually:
+Netwrix Auditor can't push configuration changes to network devices, so configure native audit
+settings manually on the Cisco ASA device. When you finish, the device has the following settings:
 
-    - On the Cisco ASA Device:
+- The global configuration mode is enabled.
+- The `logging enable` option is turned on.
+- The `logging host` parameter is set to the host address of the audited Cisco ASA device, and the
+  device uses a UDP port (for example, 514) to send messages.
 
-        - The global configuration mode is selected.
-        - The `logging enable `option is selected on the Cisco ASA device.
-        - The `logging host` parameter is set to the host address of the audited CiscoASA device.
-          And UDP port (for, example 514) is used for sending messages.
+    **NOTE:** Don't select the EMBLEM format logging for the syslog server option.
 
-            **NOTE:** Do not select the EMBLEM format logging for the syslog server option.
-
-        - The `logging timestamp` option enabled.
-        - The `logging trap` option is selected from 1 to 6 inclusive.
+- The `logging timestamp` option is enabled.
+- The `logging trap` option is set from 1 to 6 inclusive.
 
 To configure your Cisco ASA devices, do the following:
 
@@ -53,13 +43,11 @@ To configure your Cisco ASA devices, do the following:
     hostname(config)# logging enable
 
 4. Set the IP address of the computer that hosts Netwrix Auditor Server as the `logging host`
-   parameter. And make sure that the UDP port is used for sending syslog messages (e.g., 514 UDP
+   parameter, and ensure that the device uses a UDP port to send syslog messages (e.g., 514 UDP
    port). For example:
 
     hostname(config)# logging host `<Netwrix Auditor server IP address>`
 
-    Do not select the EMBLEM format logging for the syslog server option.
-
 5. Enable the `logging timestamp` option. For example:
 
     hostname(config)# logging timestamp

docs/auditor/10.7/configuration/networkdevices/ciscoios.md

@@ -6,31 +6,23 @@ sidebar_position: 30
 
 # Configure Cisco IOS Devices
 
-Netwrix Auditor relies on native logs for collecting audit data. Therefore, successful change and
-access auditing requires a certain configuration of native audit settings in the audited environment
-and on the Auditor console computer. Configuring your IT infrastructure may also include enabling
-certain built-in Windows services, etc. Proper audit configuration is required to ensure audit data
-integrity, otherwise your change reports may contain warnings, errors or incomplete audit data.
-
-**CAUTION:** Folder associated with Netwrix Auditor must be excluded from antivirus scanning. See
-the
+Netwrix Auditor relies on native syslog events for collecting audit data. Therefore, successful
+change and access auditing requires a certain configuration of native audit settings in the audited
+environment. Proper audit configuration ensures audit data integrity; otherwise, your change reports
+may contain warnings, errors, or incomplete audit data.
+
+**CAUTION:** Exclude the folder associated with Netwrix Auditor from antivirus scanning. See the
 [Antivirus Exclusions for Netwrix Auditor](/docs/kb/auditor/system-administration/security-hardening/antivirus-exclusions-for-netwrix-auditor)
 knowledge base article for additional information.
 
-You can configure your IT Infrastructure for monitoring in one of the following ways:
-
-- Automatically through a monitoring plan – This is a recommended method. If you select to
-  automatically configure audit in the target environment, your current audit settings will be
-  checked on each data collection and adjusted if necessary.
-- Manually – Native audit settings must be adjusted manually to ensure collecting comprehensive and
-  reliable audit data. You can enable Auditor to continually enforce the relevant audit policies or
-  configure them manually:
+Netwrix Auditor can't push configuration changes to network devices, so configure native audit
+settings manually on the Cisco IOS device. When you finish, the device has the following settings:
 
-    - The global configuration mode is selected.
-    - The `logging timestamp` option enabled.
-    - The `logging trap` option is selected from 1 to 6 inclusive.
-    - The `logging host` parameter is set to the host address where the service is going to be
-      installed. And UDP port (for, example 514) is used for sending messages.
+- The global configuration mode is enabled.
+- The `logging timestamp` option is enabled.
+- The `logging trap` option is set from 1 to 6 inclusive.
+- The `logging host` parameter is set to the host address of the computer that hosts Netwrix
+  Auditor Server, and the device uses a UDP port (for example, 514) to send messages.
 
 To configure your Cisco IOS devices, do the following:
 
@@ -48,8 +40,8 @@ To configure your Cisco IOS devices, do the following:
 
     Router# logging trap 5
 
-5. Set the IP address of the Netwrix Auditor Server as the logging host parameter. And make sure
-   that the UDP port is used for sending syslog messages (e.g., 514 UDP port). For example:
+5. Set the IP address of the Netwrix Auditor Server as the logging host parameter, and ensure that
+   the device uses a UDP port to send syslog messages (e.g., 514 UDP port). For example:
 
     Router# logging 192.168.1.5
 

docs/auditor/10.7/configuration/networkdevices/fortinetfortigate.md

@@ -6,32 +6,21 @@ sidebar_position: 60
 
 # Configure Fortinet FortiGate Devices
 
-Netwrix Auditor relies on native logs for collecting audit data. Therefore, successful change and
-access auditing requires a certain configuration of native audit settings in the audited environment
-and on the Auditor console computer. Configuring your IT infrastructure may also include enabling
-certain built-in Windows services, etc. Proper audit configuration is required to ensure audit data
-integrity, otherwise your change reports may contain warnings, errors or incomplete audit data.
-
-**CAUTION:** Folder associated with Netwrix Auditor must be excluded from antivirus scanning. See
-the
+Netwrix Auditor relies on native syslog events for collecting audit data. Therefore, successful
+change and access auditing requires a certain configuration of native audit settings in the audited
+environment. Proper audit configuration ensures audit data integrity; otherwise, your change reports
+may contain warnings, errors, or incomplete audit data.
+
+**CAUTION:** Exclude the folder associated with Netwrix Auditor from antivirus scanning. See the
 [Antivirus Exclusions for Netwrix Auditor](/docs/kb/auditor/system-administration/security-hardening/antivirus-exclusions-for-netwrix-auditor)
 knowledge base article for additional information.
 
-You can configure your IT Infrastructure for monitoring in one of the following ways:
-
-- Automatically through a monitoring plan – This is a recommended method. If you select to
-  automatically configure audit in the target environment, your current audit settings will be
-  checked on each data collection and adjusted if necessary.
-- Manually – Native audit settings must be adjusted manually to ensure collecting comprehensive and
-  reliable audit data. You can enable Auditor to continually enforce the relevant audit policies or
-  configure them manually:
-
-    - The target Fortinet Fortigate device must be configured via Command Line Interface (CLI) as
-      described below.
+Configure native audit settings manually on the Fortinet FortiGate device to ensure Netwrix
+Auditor collects comprehensive and reliable audit data.
 
 To configure your Fortinet FortiGate devices, enable logging to multiple Syslog servers and
-configure FortiOS to send log messages to remote syslog servers in CEF format. Do one of the
-following:
+configure FortiOS to send log messages to remote syslog servers in Common Event Format (CEF). Do
+one of the following:
 
 - To configure Fortinet FortiGate devices via Command Line Interface
 - To configure Fortinet FortiGate devices through the Fortigate Management Console

docs/auditor/10.7/configuration/networkdevices/juniper.md

@@ -6,51 +6,39 @@ sidebar_position: 80
 
 # Configure Juniper Devices
 
-Netwrix Auditor relies on native logs for collecting audit data. Therefore, successful change and
-access auditing requires a certain configuration of native audit settings in the audited environment
-and on the Auditor console computer. Configuring your IT infrastructure may also include enabling
-certain built-in Windows services, etc. Proper audit configuration is required to ensure audit data
-integrity, otherwise your change reports may contain warnings, errors or incomplete audit data.
-
-**CAUTION:** Folder associated with Netwrix Auditor must be excluded from antivirus scanning. See
-the
+Netwrix Auditor relies on native syslog events for collecting audit data. Therefore, successful
+change and access auditing requires a certain configuration of native audit settings in the audited
+environment. Proper audit configuration ensures audit data integrity; otherwise, your change reports
+may contain warnings, errors, or incomplete audit data.
+
+**CAUTION:** Exclude the folder associated with Netwrix Auditor from antivirus scanning. See the
 [Antivirus Exclusions for Netwrix Auditor](/docs/kb/auditor/system-administration/security-hardening/antivirus-exclusions-for-netwrix-auditor)
 knowledge base article for additional information.
 
-You can configure your IT Infrastructure for monitoring in one of the following ways:
-
-- Automatically through a monitoring plan – This is a recommended method. If you select to
-  automatically configure audit in the target environment, your current audit settings will be
-  checked on each data collection and adjusted if necessary.
-- Manually – Native audit settings must be adjusted manually to ensure collecting comprehensive and
-  reliable audit data. You can enable Auditor to continually enforce the relevant audit policies or
-  configure them manually:
-
-    - The target Juniper device must be configured via JunOS Command Line Interface (CLI) as
-      described below.
+Configure native audit settings manually on the Juniper device to ensure Netwrix Auditor collects
+comprehensive and reliable audit data.
 
-To configure you Juniper devices, do the following:
+To configure your Juniper devices, do the following:
 
-1. Launch the JunOS Command Line Interface (CLI).
+1. Launch the Junos OS command line interface (CLI).
 2. Execute the following commands:
 
     # configure
 
     # set system syslog host `<host address>` any info
 
-    where `<host address>` is the IP address of the computer where Netwrix Auditor Server is
-    installed.
+    where `<host address>` is the IP address of the computer that hosts Netwrix Auditor Server.
 
     # set system syslog host `<host address>` port `<port name>`
 
     where
 
-    `<host address>` is the IP address of the computer where Netwrix Auditor Server is installed
+    `<host address>` is the IP address of the computer that hosts Netwrix Auditor Server
 
     AND
 
-    `<port number>` is the name of the UDP port used to listen to network devices (514 port used by
-    default). [Network Devices](/docs/auditor/10.7/admin/monitoringplans/networkdevices.md)
+    `<port number>` is the name of the UDP port that Netwrix Auditor uses to listen to network
+    devices (port 514 by default). [Network Devices](/docs/auditor/10.7/admin/monitoringplans/networkdevices.md)
 
     # set system syslog time-format `<current year>`
 

docs/auditor/10.7/configuration/networkdevices/paloalto.md

@@ -6,33 +6,20 @@ sidebar_position: 90
 
 # Configure PaloAlto Devices
 
-Netwrix Auditor relies on native logs for collecting audit data. Therefore, successful change and
-access auditing requires a certain configuration of native audit settings in the audited environment
-and on the Auditor console computer. Configuring your IT infrastructure may also include enabling
-certain built-in Windows services, etc. Proper audit configuration is required to ensure audit data
-integrity, otherwise your change reports may contain warnings, errors or incomplete audit data.
-
-**CAUTION:** Folder associated with Netwrix Auditor must be excluded from antivirus scanning. See
-the
+Netwrix Auditor relies on native syslog events for collecting audit data. Therefore, successful
+change and access auditing requires a certain configuration of native audit settings in the audited
+environment. Proper audit configuration ensures audit data integrity; otherwise, your change reports
+may contain warnings, errors, or incomplete audit data.
+
+**CAUTION:** Exclude the folder associated with Netwrix Auditor from antivirus scanning. See the
 [Antivirus Exclusions for Netwrix Auditor](/docs/kb/auditor/system-administration/security-hardening/antivirus-exclusions-for-netwrix-auditor)
 knowledge base article for additional information.
 
-You can configure your IT Infrastructure for monitoring in one of the following ways:
-
-- Automatically through a monitoring plan – This is a recommended method. If you select to
-  automatically configure audit in the target environment, your current audit settings will be
-  checked on each data collection and adjusted if necessary.
-- Manually – Native audit settings must be adjusted manually to ensure collecting comprehensive and
-  reliable audit data. You can enable Auditor to continually enforce the relevant audit policies or
-  configure them manually:
-
-    - Create a Syslog Server profile and syslog forwarding for the target PaloAlto device via Web
-      Interface as described below.
-
-To configure your PaloAlto devices, create a Syslog server profile and assign it to the log settings
-for each log type.
+Configure native audit settings manually on the Palo Alto device via the web interface to ensure
+Netwrix Auditor collects comprehensive and reliable audit data. Create a syslog server profile and
+assign it to the log settings for each log type.
 
-Follow the steps to configure a Syslog server profile.
+## Configure a syslog server profile
 
 **Step 1 –** Connect to your PaloAlto device: launch an Internet browser and enter the IP address of
 the firewall in the URL field (https://`<IP address>`).
@@ -48,23 +35,24 @@ the firewall in the URL field (https://`<IP address>`).
 | Name          | Specify unique name for a syslog server.                                                       |
 | Syslog Server | Provide a server name by entering its FQDN or IPv4 address.                                    |
 | Transport     | Select UDP.                                                                                    |
-| Port          | Provide the name of the UDP port used to listen to network devices (514 port used by default). |
+| Port          | Provide the name of the UDP port that Netwrix Auditor uses to listen to network devices (port 514 by default). |
 | Format        | Select IETF.                                                                                   |
 | Facility      | Netwrix recommends using default values.                                                       |
 
-Follow the steps to configure syslog forwarding.
+## Configure syslog forwarding
 
 **Step 1 –** In the Web Interface, navigate to **Device** > **Log Settings**.
 
 **Step 2 –** For System, Config, and User ID logs, click Add and enter unique name of your syslog
 server.
 
-**Step 3 –** On the syslog panel, click Add and select the syslog profile you created above.
+**Step 3 –** On the syslog panel, click Add and select the syslog server profile you created in
+[Configure a syslog server profile](#configure-a-syslog-server-profile).
 
 **Step 4 –** Click **Commit** and review the logs on the syslog server.
 
-**NOTE:** After configuring the monitoring plan, Netwrix Auditor will listen to the logs forwarded
-by the Palo Alto device.
+**NOTE:** After you configure the monitoring plan, Netwrix Auditor listens to the logs that the
+Palo Alto device forwards.
 
 ## PaloAlto Devices