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
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¶
-
ArcSight Logger 7.1 with the WEB URL
https://192.168.1.73:443
installed on CentOS 7.8 -
Logstash 7.7.0 installed on Debian 11.x (bullseye) and available on
https://logstash.example.domain.com
-
Administrator access to Wallarm Console in EU cloud to configure the Logstash integration
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
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
https://192.168.1.73:514
- 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
- All event logs are forwarded from Logstash to ArcSight Logger at the IP address
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:
Configuration of Logstash integration¶
-
Webhooks are sent to
https://logstash.example.domain.com
-
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
More details on the Logstash integration configuration
Example testing¶
To test the configuration, a new user is added in Wallarm Console:
Logstash will log the event as follows:
The following entry will be displayed in ArcSight Logger events: