Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Current »

This quick start guide will help Accenture MDR customers configure Broadcom Symantec Siteminder 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_MDR_Supported_Products_List.xlsx) which can be found at Accenture MDR Portal.

Port Requirements

Table 1-1: Port requirements for LCP communication.

           Source

       Destination

           Port

       Description

Siteminder

LCP

UDP/514

or

TCP/601

Default port

Configuring Siteminder

Device configuration steps:

I. Steps to configure NxLog Agent on Windows for Log flow over TCP or UDP or TLS (Windows)

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

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

  3. Go to folder "C:\Program Files\nxlog\data" and delete "configcache.dat"

  4. For Windows Agent , go to installed location “C:\Program Files\nxlog\conf”. Rename below attached “nxlog(windows).txt” to "nxlog.conf" and replace with “nxlog.conf” file which was already present in this folder.

5. Replace “<LCP_IP>” with actual LCP IP in nxlog.conf

6. Change smaccess.log file location on line 29

7. Now start the nxlog service from services.msc

8. NxLog agent logs will be available at location "C:\Program Files\nxlog\data\nxlog.log"

9. Log flow should work and the logs will be seen on the LCP end for destination port on packet capture.

II. Steps to configure NxLog Agent on RHEL for Log flow over TCP or UDP or TLS (Linux RHEL)

  1. Download and Install NxLog agent from location Download  (There are few dependencies that you need to install and then you can install nxlog on machine. Refer Documentation :: NXLog Documentation )

  2. For Linux Agent , After installation go to installed location “/etc/nxlog/”. Rename attached “nxlog(Linux)1.txt” to "nxlog.conf" and replace with “nxlog.conf” file which was already present in this folder.

3. Replace “<LCP_IP>” with actual LCP IP in nxlog.conf

4. Change smaccess.log file location on line 24

5. Now start the nxlog service using below command
systemctl start nxlog

6. NxLog agent logs will be available at location "/var/log/nxlog.log"

7. Log flow should work and the logs will be seen on the LCP end for destination port on packet capture.

LCP Configuration Parameters

Table 1-2: Broadcom Symantec Siteminder event collector (Syslog - 3986) sensor properties to be configured by MSS are shown in the table.

Property

Default Value

Description

Protocol

UDP

 The default protocol for syslog. The collector 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 Accenture Security MDR onboarding team.

Host Names/IP Addresses 

Siteminder IP

 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.

Signatures

Broadcom-Siteminder

 MDR recommended signatures processed by the Broadcom Symantec Siteminder event collector.

Port Number

514

 The default port number 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 Accenture MDR onboarding team if this is a requirement.

  • No labels

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.