Chapter 10. Integrating by using the syslog protocol
Syslog is an event logging protocol that applications use to send messages to a central location, such as a SIEM or a syslog collector, for data retention and security investigations. With Red Hat Advanced Cluster Security for Kubernetes, you can send alerts and audit events using the syslog protocol.
- Forwarding events by using the syslog protocol requires the Red Hat Advanced Cluster Security for Kubernetes version 3.0.52 or newer.
- When you use the syslog integration, Red Hat Advanced Cluster Security for Kubernetes forwards both violation alerts that you configure and all audit events.
- Currently, Red Hat Advanced Cluster Security for Kubernetes only supports CEF (Common Event Format).
The following steps represent a high-level workflow for integrating Red Hat Advanced Cluster Security for Kubernetes with a syslog events receiver:
- Set up a syslog events receiver to receive alerts.
- Use the receiver’s address and port number to set up notifications in the Red Hat Advanced Cluster Security for Kubernetes.
After the configuration, Red Hat Advanced Cluster Security for Kubernetes automatically sends all violations and audit events to the configured syslog receiver.
10.1. Configuring syslog integration with Red Hat Advanced Cluster Security for Kubernetes Copy linkLink copied to clipboard!
Create a new syslog integration in Red Hat Advanced Cluster Security for Kubernetes (RHACS).
Procedure
-
In the RHACS portal, click the Platform Configuration
Integrations Notifier tab. - Select Syslog.
- Click New integration.
In the Create integration page, provide the following information:
- Enter a name for your integration.
-
Select the Logging facility value from
local0throughlocal7. - Enter your Receiver host address and Receiver port number.
Enter a value for the Maximum message size.
Enter a value between
0and1048576, which corresponds to the number of bytes used to chunk messages. You can adjust the value by using the up and down arrows in the spin button.If you do not want to chunk messages, enter
0.Select the appropriate Message format:
- If you are creating a new integration, select CEF.
- If you have an existing integration that relies on the old behavior, select CEF (legacy field order).
Select the appropriate checkboxes:
- If you are using TLS, select the Use TLS checkbox.
- If your syslog receiver uses a certificate that is not trusted, select the Disable TLS Certificate Validation (insecure) checkbox.
To add extra fields, click Add new extra field.
For example, if your syslog receiver accepts objects from multiple sources, type
sourceandrhacsin the Key and Value fields.You can filter by using the custom values in your syslog receiver to identify all alerts from RHACS.
- To send a test message to verify that the integration with your generic webhook is working, click Test.
- To create the configuration, click Save.