Accenture MDR Quick Start Guide for Versa Networks SASE (Secure Access Service Edge)

This quick start guide will help Accenture Security customers configure Versa Networks SASE to send logs to the Log Collection Platform (LCP).

This document includes the following topics:

1 Supported Versions
2 Port Requirements
3 Configuring Versa Networks SASE
4 LCP Configuration Parameters

Supported Versions

A list of supported versions is available in the Accenture MDR Supported Products List document (Accenture_MDR_Supported_Products_List.xlsx) which can be found in Accenture MDR Portal.

Port Requirements

Table 1-1: Port requirements for LCP communication.

Source

Destination

Port

Description

Versa Networks SASE

LCP

514 (UDP) or

601 (TCP)

Default port

Configuring Versa Networks SASE

To configure the Versa Analytics Nodes, follow the steps below.

Note: Administrator is required to configure the remote collectors on each Versa Analytics nodes, to stream the logs to Third party collectors.

Enable Log Forwarding

Log in to the analytics server.
Navigate to CLI using cli command.
Go to configuration mode using configure command and enter load merge terminal, you will see a blank line.
Now you can copy and paste the bellow commands to the terminal.

Note: Change the parameters according

a) Enter LCP IP next to the destination-address

b) Enter the port number (514 or 601 preferred in case of using protocol UDP or TCP respectively) next to the destination-port

c) Enter the protocol (TCP or UDP ) next to transport

Follow below template for reference and configure log collector exporter on analytics node.

[edit log-collector-exporter remote]
templates {
   rt2 {
       type  syslog;
       format cef;
   }
}
collectors {
   rc1 {
       destination-address xxx.xxx.xxx.xxx;
       destination-port   601;
       pending-queue-limit 200;
       transport          tcp;
       template           rt2;
   }

Note: Remote collector will receive the logs based on the policies configured in the log-collector-exporter. We suggest you mention only below log-types in log-collector-exporter:

firewall-log
threat-log

If no log type has specified, it will stream all log-types events. For more information on how to configure log-collector-exporter, please refer versa analytics log collector exporter guide.

Enable Session ID Logging

To receive IP related information in the logs, we need to enable session ID logging.

In Director view:

Select the Configuration tab in the top menu bar.
Navigate to Devices in the horizontal menu bar.
Select a tenant in the left menu bar.
Select a device in the main pane. The view changes to Appliance view.

2. Select the Configuration tab in the top menu bar.

3. Navigate to Others > System > Configuration > Configuration in the left menu bar.

4. In the Parameters pane, click the Edit icon.

5. In the Edit Parameters popup window, select the LEF option and enable Include Session ID logging checkbox under Firewall as shown below.

Note: In Releases 21.1.1 and later, sending the session identification is enabled by default. Make sure to enable this if not already.

6. Click Ok.

LCP Configuration Parameters

Table 1-2: The Versa Networks SASE event collector (Syslog -3937) properties to be configured by MDR are shown in the table.

Property	Default Value	Description
Protocol	UDP	Default protocol for syslog. The LCP can also accept logs in TCP. Note: While TCP offers guaranteed delivery of log packets, it places a larger overhead on the LCP. To balance TCP for reliability over UDP for speed/simplicity, contact the MDR onboarding team.
IP Address	<Device IP address>	Logging device IP address mentioned in the Pre-Installation Questionnaire (PIQ). Note: If the device sends logs using multiple interfaces, contact the Accenture Security MDR onboarding team.
Signatures	\|FlexVNF\|	MDR recommended signatures processed by the Versa Networks SASE collector.
Port Number	514	The default port for syslog. For TCP, the default port is 601. Note: The LCP can be configured to listen on a non-standard port, please advise the MDR onboarding team if this is a requirement.