Skip to content

Micro Focus ArcSight Logger via Logstash

These instructions provide you with the example integration of Wallarm with the Logstash data collector to further forward events to the ArcSight Logger system.

The most common logging scheme in complex systems consists of the following components:

  • Data collector: accepts logs from several sources and forwards logs to the SIEM system

  • SIEM system or log management systems: used to analyze logs and monitor the system status

Webhook flow

Integration with the Enterprise version of ArcSight ESM

To configure forwarding logs from Logstash to the Enterprise version of ArcSight ESM, it is recommended to configure the Syslog Connector on the ArcSight side and then forward logs from Logstash to the connector port. To get a more detailed description of the connectors, please download the SmartConnector User Guide from the official ArcSight SmartConnector documentation.

Used resources

Wallarm Cloud IP addresses

To provide Wallarm Cloud access to your system, you may need a list of its public IP addresses:

Since the links to the ArcSight Logger and Logstash services are cited as examples, they do not respond.

ArcSight Logger configuration

ArcSight Logger has logs receiver Wallarm Logstash logs configured as follows:

  • Logs are received via UDP (Type = UDP Receiver)

  • Listening port is 514

  • Events are parsed with the syslog parser

  • Other default settings

Configuration of receiver in ArcSight Logger

To get a more detailed description of the receiver configuration, please download the Logger Installation Guide of an appropriate version from the official ArcSight Logger documentation.

Logstash configuration

Since Wallarm sends logs to the Logstash intermediate data collector via webhooks, the Logstash configuration should meet the following requirements:

  • Accept the POST or PUT requests

  • Accept HTTPS requests

  • Have public URL

  • Forward logs to ArcSight Logger, this example uses the syslog plugin to forward logs

Logstash is configured in the logstash-sample.conf file:

  • Incoming webhook processing is configured in the input section:

    • Traffic is sent to port 5044
    • Logstash is configured to accept only HTTPS connections
    • Logstash TLS certificate signed by a publicly trusted CA is located within the file /etc/server.crt
    • Private key for TLS certificate is located within the file /etc/server.key
  • Forwarding logs to ArcSight Logger and log output are configured in the output section:

    • All event logs are forwarded from Logstash to ArcSight Logger at the IP address
    • Logs are forwarded from Logstash to ArcSight Logger in the JSON format according to the Syslog standard
    • Connection with ArcSight Logger is established via UDP
    • Logstash logs are additionally printed on the command line (15th code line). The setting is used to verify that events are logged via Logstash
input {
  http { # input plugin for HTTP and HTTPS traffic
    port => 5044 # port for incoming requests
    ssl => true # HTTPS traffic processing
    ssl_certificate => "/etc/server.crt" # Logstash TLS certificate
    ssl_key => "/etc/server.key" # private key for TLS certificate
output {
  syslog { # output plugin to forward logs from Logstash via Syslog
    host => "" # IP address to forward logs to
    port => "514" # port to forward logs to
    protocol => "udp" # connection protocol
    codec => json # format of forwarded logs
  stdout {} # output plugin to print Logstash logs on the command line

A more detailed description of the configuration files is available in the official Logstash documentation.

Testing Logstash configuration

To check that Logstash logs are created and forwarded to ArcSight Logger, the POST request can be sent to Logstash.

Request example:

curl -X POST '' -H "Content-Type: application/json" -d '{"key1":"value1", "key2":"value2"}'

Logstash logs:
Logstash logs

Event in ArcSight Logger:
ArcSight Logger event

Configuration of Logstash integration

  • Webhooks are sent to

  • Webhooks are sent via POST requests

  • The webhook integration has default advanced settings

  • Webhooks sent to Webhook URLs are all available events: hits, system events, vulnerabilities, scope changes

Webhook integration with Logstash

More details on the Logstash integration configuration

Example testing

To test the configuration, a new user is added in Wallarm Console:

Adding user

Logstash will log the event as follows:

Log about new user in ArcSight Logger from Logstash

The following entry will be displayed in ArcSight Logger events:

New user card in ArcSight Logger from Logstash