Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 2 Next »

This quick start guide will help Accenture MDR customers configure Imperva® Web Application Firewall (WAF) to send logs to the Log Collection Platform (LCP).

The document includes the following topics:

  • Supported Versions

  • Port Requirements

  • Configuring the Imperva WAF

  • 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 - https://mss.accenture.com/PortalNextGen/Reports/Documents

Port Requirements

Table 1-1: Port requirements for LCP communication.

Source

Destination

Port

Description

Imperva WAF 

LCP

514 (UDP) or

601 (TCP)

Default port

 Configuring the Imperva WAF

You must configure the SecureSphere WAF server to send syslog messages in the Common Event Format (CEF) standard when an alert or a system event occurs.

SecureSphere offers the following different events which require the message field to be configured:

  • Custom security event - The SecureSphere server is configured to send syslog messages based on the CEF standard when a custom security event occurs.

  • Network security event - The SecureSphere server is configured to send syslog messages based on the CEF standard when a network security event occurs.

  • Security event - The SecureSphere server is configured to send syslog messages based on the CEF standard when a security event occurs.

  • System event - The SecureSphere server is configured to send syslog messages based on the CEF standard when a system security event occurs.

To configure the Imperva Admin interface, follow the steps below.

  1. Click the Admin tab of SecureSphere.

  2. Go to the System Definitions page.

  3. In the left panel, under the Management Server Settings, click Action Interfaces.

  4. In the right panel, select the following events:

  • Log custom security event to System Log (syslog) using the CEF standard.

  • Log network security event to System Log (syslog) using the CEF standard.

  • Log security event to System Log (syslog) using the CEF standard.

5. Edit the message field for all the above 3 events and add the following.

#Log custom security event to System Log (syslog) using the CEF standard.

#Log network security event to System Log (syslog) using the CEF standard.

#Log security event to System Log (syslog) using the CEF standard.

CEF:0|Imperva Inc.|SecureSphere|${SecureSphereVersion}|#cefEscapeMessage(${Rule.parent.displayName})|#cefEscapeMessage(${Rule.parent.displayName})|${Alert.severity}|act=${Alert.immediateAction}dst=${Event.destInfo.serverIp} dpt=${Event.destInfo.serverPort} duser=#cefEscapeExtension(${Alert.username}) src=${Event.sourceInfo.sourceIp}spt=${Event.sourceInfo.sourcePort} proto=${Event.sourceInfo.ipProtocol}rt=#arcsightDate(${Event.createTime}) cat=Alert cs1=#cefEscapeExtension(${Rule.parent.displayName}) cs1Label=Policy cs2=#cefEscapeExtension(${Alert.serverGroupName}) cs2Label=ServerGroup cs3=#cefEscapeExtension(${Alert.serviceName}) cs3Label=ServiceName cs4=#cefEscapeExtension(${Alert.applicationName}) cs4Label=ApplicationName cs5=#cefEscapeExtension(${Alert.description}) cs5Label=Description cs8=#cefEscapeExtension(${Event.struct.httpRequest.url.method}) cs8Label=HTTPMethod cs9=#cefEscapeExtension(${Event.struct.httpRequest.url.fullPath}) cs9Label=HTTPFullpathcs10=#cefEscapeExtension(${Event.struct.httpRequest.url.queryString}) cs10Label=QueryString cs11=#cefEscapeExtension(${Event.struct.httpResponse.responseCode}) cs11Label=HTTPResponseCode cs12=#cefEscapeExtension(${Event.struct.networkDirection}) cs12Label=NetworkDirection

  

​ 6. Select the System event by enable the below :

  • Log System event to System Log (syslog) using the CEF standard.

7. Edit the message field and add the following.

#Log custom System event to System Log (syslog) using the CEF standard

CEF:0|ImpervaInc.|SecureSphere|${SecureSphereVersion}|${Event.eventType}|#cefEscapeMessage(${Event.message})|${Event.severity.displayName}|suser=#cefEscapeExtension(${Event.username}) rt=#arcsightDate(${Event.createTime}) cat=SystemEvent

8. Click Save.

 To configure Imperva on the Main interface, follow the steps below.

  1. Click the Main tab of SecureSphere.

  2. Go to Policies > Action Sets to create a new action set.

  3. In the left panel, on the Select pane, click +.

  4. In the dialog box for creating a new action set, specify a name and select the event type for which you want to apply the action set (Web Application Level and Web Service Level are supported by the collector).

  5. In the right panel, from Available Action Interfaces select the following events:

  • Server System Log > Log custom security event to System Log (syslog) using the CEF standard.

  • Server System Log > Log network security event to System Log (syslog) using the CEF standard.

  • Server System Log > Log security event to System Log (syslog) using the CEF standard.

  • Server System Log > Log system event to System Log (syslog) using the CEF standard.

6. For each action interface, specify the name and values for Syslog Host <LCP_ip_address>, Log Level, and Facility.

7. Optionally, you can select the Run on Every Event check box.

8. Click Save.

9. To apply the action interface, click the green arrow to move it to the selected interface.

To apply action set to the policies, follow the steps below.

  1. Go to the Policies > Security page.

  2. For all the policies, select the created action set name from the Followed Action list.

LCP Configuration Parameters  

Table 1-2: The Imperva WAF event collector (Syslog-3689) properties to be configured by MDR 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 MSS onboarding team.

IP Address

Imperva WAF 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 MSS onboarding team.

Signatures

SecureSphere

MSS recommended signatures processed by the Imperva WAF event collector.

Port Number

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 MDR onboarding team if this is a requirement.

 

  • No labels