Accenture MDR Quick Start Guide for HPE 3PAR StoreServ
- Dinesh Murugaiyan
This quick start guide will help Accenture MxDR customers configure HPE 3PAR StoreServ 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 in Accenture MDR Portal.
Port Requirements
Table 1-1: Port requirements for LCP communication.
Source | Destination | Port | Description |
HPE 3PAR StoreServ | LCP | 601 (TCP) | Default port
|
Configuring HPE 3PAR StoreServ
Log in to the system using any role.
To view the status of the remote syslog servers, enter the following command:
showsys -dTo send all non-debug events to the syslog server (general mechanism), enter the following command:
setsys RemoteSyslogHost {{<LCP_IP>}[:601]Use a comma to separate multiple server specifications (up to three). When configuring the destination with both the IPv6 address and port, you must enclose the IPv6 address in square brackets.
To send all security-related events to the syslog server for auditing purposes (security mechanism), enter the following command:
setsys RemoteSyslogSecurityHost {{<LCP_IP>}[:601]When configuring the destination with both the IPv6 address and port, you must enclose the IPv6 address in square brackets.
LCP Configuration Parameters
Table 1-2: The HPE 3PAR StoreServ event collector (Syslog -4022) properties to be configured by Accenture are given in the table.
Property | Default Value | Description |
Protocol | TCP | 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 Onboarding team. |
Host Names / IP Addresses | * | Logging device IP address mentioned in the Pre-Installation Questionnaire (PIQ). Note: If the device sends logs using multiple interfaces, contact the Accenture Security Onboarding team. |
Signatures | removed_obj,cli_command,cage_status_changed,new_obj,cli_comm_err | Accenture Security recommended signatures. |
Port Number | 601 | For TCP preferred port is 601 |
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.