Accenture MDR Quick Start Guide for Symantec Protection Engine NAS (Network Attached Storage)

This quick start guide will help Accenture MDR customers configure Symantec Protection Engine NAS to send logs to the Log collection Platform (LCP).

This document includes the following topics:

 

Supported Versions

A list of supported versions is available in the Accenture MDR Supported Products List document (Accenture_MSS_Supported_Products_List.xlsx) which can be found in Accenture MDR Portal - https://mss.accenture.com/PortalNextGen/Reports/Documents

Port Requirements

Table 1-1: Port requirements for LCP communication.

Source

Destination

Port

Description

Symantec Protection Engine NAS

LCP

514 (UDP)

or

10014 (TCP with TLS)

Default port

 Note: While using the Unix based syslog collector to send logs , the port for Symantec Protection Engine NAS collector should be changed from 514 to any other UDP port to avoid conflict.

Configuring Symantec Protection Engine NAS

Symantec Protection Engine NAS stores the events in log files. Accenture Security recommends NxLog Agent to be used for Symantec Protection Engine NAS log collection.

Log configuration via NxLog Agent in Windows

  1. Log in to Symantec Protection Engine device using Administrator Credentials

  2. Select Monitors from the left Menu Panel

  3. Click on logging under Views

  4. Select the option Warning from the Windows Logging level drop-down menu

  5. Click on Save and Deploy                                                                                                   

To configure the NxLog Agent in Windows you can use any of the below:

Steps to configure Windows NxLog Agent using port 514

  1. Download and Install NxLog agent from location https://nxlog.co/products/nxlog-community-edition/download

  2. Navigate to services.msc and stop the nxlog service

  3. Navigate to C:\Program Files (x86)\nxlog\data and delete configcache.dat

  4. For Windows Agent, go to installed location C:\Program Files (x86)\nxlog\conf 

  5. Rename the attached nxlog.conf file to nxlog.conf and move the file into this folder.

6. Replace LCP_IP_Address with actual LCP IP address in nxlog.conf against Host

7. Now start the nxlog service from services.msc

8. NxLog Agent logs will be available at the location C:\Program Files (x86)\nxlog\data\nxlog.log

Steps to configure Windows NxLog Agent for for TLS TCP Log flow on port 10014

  1. Download and Install NxLog agent from location https://nxlog.co/products/nxlog-community-edition/download

  2. Navigate to services.msc and stop the nxlog service

 Note: Please contact the Accenture Security MSS onboarding team to obtain the certificate.

3. Place the certificate into NAS server which is obtained from the MSS onboarding team at your desired location.

4. Navigate to C:\Program Files (x86)\nxlog\data and delete configcache.dat

5. For Windows Agent, go to installed location C:\Program Files (x86)\nxlog\conf

6. Rename the attached nxlog.conf(WinTLS) file to nxlog.conf and move the file into this folder.

7. Replace LCP_IP_Address with actual LCP IP address in nxlog.conf against Host

8. Provide the CA File location at position 44

9. Now start the nxlog service from services.msc

10. NxLog Agent logs will be available at the location C:\Program Files (x86)\nxlog\data\nxlog.log

Log configuration via NxLog Agent in Unix

  1. SSH the Linux machine where the SPE Server is installed.

  2. Navigate to /opt/SYMCScan/bin/ and open configuration.xml in VI editor

  3. In Logging section, change the Syslog log level to 3

  4. Save the file

<Logging>

                <LogDir value="/opt/SYMCScan/log"/>

                <AlertBindAddress value=""/>

                <LoadExceededAlertInterval value="5"/>

                <LogLocal logfilestokeep="0" loglevel="3"/>

                <LogWindows loglevel="0"/>

                <Syslog loglevel="3"/>

                <LogPopup value="false"/>

                <LogSNMP community="public" loglevel="0" primary="" primaryport="162" secondary="" secondaryport="162"/>

                <LogSMTP domain="" loglevel="0" primary="" secondary="">

5. Restart the Symantec Protection Engine using /etc/init.d/symcscan restart command

To configure the NxLog Agent in Unix , you can use any of the below:

Steps to configure NxLog Agent using port 514

  1. Download and Install NxLog agent from location https://nxlog.co/products/nxlog-community-edition/download

  2. Navigate to the installed location /etc/nxlog.conf and rename the attached nxlog.conf to nxlog.conf and copy into this folder.

3. Replace LCP_IP_Address with actual LCP IP address in nxlog.conf against Host

4. Start the NxLog service using the below command 

           systemctl start nxlog

5. NxLog agent logs can be found at location /var/log/nxlog.log​

Steps to configure NxLog Agent for TLS TCP Log flow on port 10014 (CentOS 7)

Download and Install NxLog agent from location https://nxlog.co/products/nxlog-community-edition/download​

 Note: Please contact the Accenture Security MSS onboarding team to obtain the certificate.

  1. Place the certificate into NAS server which is obtained from the MSS onboarding team at your desired location.

  2. Navigate to the installed location /etc/nxlog.conf and rename attached nxlog.conf to nxlog.conf and copy into this folder

3. Replace LCP_IP_Address with actual LCP IP address in nxlog.conf against Host

4. Change access.log file location on line 24.

5. Add the CAFile location at position 37.

6. Start the nxlog service using the below command

         systemctl start nxlog

7. NxLog agent logs can be found at location /var/log/nxlog.log

LCP Configuration Parameters

Table 1-2: The Symantec Protection Engine NAS  event collector (Syslog - 5005) properties to be configured by MSS are given in the table.

Property

Default Value

Description

Protocol                      

TCP

The default protocol for syslog.

IP Address

Any

Logging device IP address mentioned in the Pre-Installation Questionnaire (PIQ).

Note: If the device sends logs using multiple interfaces, contact the Accenture Security MSS onboarding team.

Port Number    

UDP/514

or

TCP/10014

The default port for TCP. For UDP, the default port is 514.

Note: The LCP can be configured to listen on a non-standard port, please advise the Accenture Security MSS onboarding team if this is a requirement.

Signature

symcscan

MSS recommended signatures processed by the Symantec Protection NAS

Note: For Linux based configuration, the signature will be symcscan . For Windows, the Field should be left blank

 

Legal Notice

Copyright © 2021 Accenture. All rights reserved.

Accenture, the Accenture Logo, and DeepSight Intelligence are trademarks or registered trademarks of Accenture in the U.S. and other countries. Other names may be trademarks of their respective owners.

The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Accenture and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. ACCENTURE SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Accenture as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.