Accenture MDR Quick Start Guide for Trustwave WebDefend®
- Sekar Venkataramani
This quick start guide will help Accenture MDR customers configure Trustwave WebDefend® to send logs to the Log Collection Platform (LCP).
The 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 - https://mss.accenture.com/PortalNextGen/Reports/Documents
Port Requirements
Table 1-1: Port requirements for LCP communication.
Source | Destination | Port | Description |
Trustwave WebDefend | LCP | 514 (UDP) 601 (TCP) | Default port |
Note: TCP is also supported. Due to device restriction, logs may get truncated if they exceed 1024 bytes both over TCP and UDP.
Configuring Trustwave WebDefend
To configure Trustwave WebDefend to send event logs, follow the steps given below.
Note: Only the Web Application Firewall module of Trustwave WebDefend is supported.
Login to the Trustwave WebDefend console.
Go to System Configuration to find the list of sites, right-click the site for which you want to configure logging and then click Properties.
3. Click Alert and go to the logging property in the right pane. Check the Syslog check box and click Settings.
The following window opens.
Note: The Syslog Settings window shown here contains example settings for syslog alerts.
4. Configure the Syslog alert to be sent by modifying the following fields as required.
Table 1-2: The Syslog Alert fields
Syslog Server IP | The IP address of the Syslog Server. |
Syslog Server Port | The Syslog Server port. |
Minimum Severity | The minimum severity of events for which the Syslog alert is sent. |
Protocol | The network protocol used by the Syslog Server. Note that syslog usually uses the UDP protocol. |
Message Content | The content of the Syslog alert message, according to the alert specification. The content can include: Free Text5 Parameters Tags: Information which Trustwave WAF replaces with the actual data from the malicious request. Leave it as default value. Syntax TAGS: Information which Trustwave WAF replaces with actual operator values (greater than or less than) in the relevant message. Leave it as default value. |
Type or Copy/Paste the following content:
TW_webdefend src=<source_ip> site=<site> method=<method> status=<status> entrytype=<entry_type> exittype=<exit_type> result=<res_cat> severity=<severity> country= <source_country> host=<host> event= ”<name>” url=”<url>” query="<query>" req="<request>"
Note: Spaces in the above content are intentional and must be copied or typed as given.
5. Check the Perform automatic configuration test check box to send a test Syslog message to the server. The test message is sent on clicking OK or Apply.
A response message notifies you of Success or Failure.
Note: For masking card numbers details, enable BreachMarks.
To enable BreachMarks, follow the steps below.
Navigate to Policy Manager.
Check the BreachMarks check box.
Check the Masking sensitive data in the reply check box.
LCP Configuration Parameters
Table 1-3: The Trustwave WebDefend event collector (Syslog - 3771) properties to be configured by MDR are shown in the table.
Property | Default Value | Description |
Transport Protocol | UDP | The 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 | Trustwave WebDefend 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 | TW_webdefend | MDR recommended signatures processed by the Trustwave WebDefend event collector. |
Port | 514 | The default port for UDP. For TCP, the default port is 601. Note: The LCP can be configured to listen on a non-standard port, please advise the Accenture Security MDR onboarding team if this is a requirement. |
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.