14장. Integrating with Splunk
If you are using Splunk, you can forward alerts from Red Hat Advanced Cluster Security for Kubernetes to Splunk and view the violations, vulnerability detection, and compliance related data from within Splunk.
Currently, Splunk integration is not supported on IBM Power(ppc64le) and IBM Z(s390x).
Depending on your use case, you can integrate Red Hat Advanced Cluster Security for Kubernetes with Splunk by using the following ways:
By using an HTTP event collector in Splunk:
- Use the event collector option to forward alerts and audit log data.
By using the Red Hat Advanced Cluster Security for Kubernetes add-on:
- Use the add-on to pull the violations, vulnerability detection, and compliance data into Splunk.
You can use one or both of these integration options to integrate the Red Hat Advanced Cluster Security for Kubernetes with Splunk.
14.1. Using the HTTP event collector 링크 복사링크가 클립보드에 복사되었습니다!
You can forward alerts from Red Hat Advanced Cluster Security for Kubernetes to Splunk by using an HTTP event collector.
To integrate Red Hat Advanced Cluster Security for Kubernetes with Splunk by using the HTTP event collector, follow these steps:
- Add a new HTTP event collector in Splunk and get the token value.
- Use the token value to set up notifications in Red Hat Advanced Cluster Security for Kubernetes.
- Identify policies for which you want to send notifications, and update the notification settings for those policies.
14.1.1. Adding an HTTP event collector in Splunk 링크 복사링크가 클립보드에 복사되었습니다!
Add a new HTTP event collector for your Splunk instance, and get the token.
Procedure
-
In your Splunk dashboard, go to Settings
Add Data. - Click Monitor.
- On the Add Data page, click HTTP Event Collector.
- Enter a Name for the event collector and then click Next >.
- Accept the default Input Settings and click Review >.
- Review the event collector properties and click Submit >.
- Copy the Token Value for the event collector. You need this token value to configure integration with Splunk in Red Hat Advanced Cluster Security for Kubernetes.
14.1.1.1. Enabling HTTP event collector 링크 복사링크가 클립보드에 복사되었습니다!
You must enable HTTP event collector tokens before you can receive events.
Procedure
-
In your Splunk dashboard, go to Settings
Data inputs. - Click HTTP Event Collector.
- Click Global Settings.
- In the dialog that opens, click Enabled and then click Save.
14.1.2. Configuring Splunk integration in Red Hat Advanced Cluster Security for Kubernetes 링크 복사링크가 클립보드에 복사되었습니다!
Create a new Splunk integration in Red Hat Advanced Cluster Security for Kubernetes by using the token value.
Procedure
-
In the RHACS portal, go to Platform Configuration
Integrations. - Scroll down to the Notifier Integrations section and select Splunk.
-
Click New Integration (
addicon). - Enter a name for Integration Name.
-
Enter your Splunk URL in the HTTP Event Collector URL field. You must specify the port number if it is not
443for HTTPS or80for HTTP. You must also add the URL path/services/collector/eventat the end of the URL. For example,https://<splunk-server-path>:8088/services/collector/event. Enter your token in the HTTP Event Collector Token field.
참고If you are using Red Hat Advanced Cluster Security for Kubernetes version 3.0.57 or newer, you can specify custom Source Type for Alert events and Source Type for Audit events.
- Select Test to send a test message to verify that the integration with Splunk is working.
- Select Create to generate the configuration.
14.1.3. Configuring policy notifications 링크 복사링크가 클립보드에 복사되었습니다!
Enable alert notifications for system policies.
Procedure
-
In the RHACS portal, go to Platform Configuration
Policy Management. - Select one or more policies for which you want to send alerts.
- Under Bulk actions, select Enable notification.
In the Enable notification window, select the Splunk notifier.
참고If you have not configured any other integrations, the system displays a message that no notifiers are configured.
- Click Enable.
- Red Hat Advanced Cluster Security for Kubernetes sends notifications on an opt-in basis. To receive notifications, you must first assign a notifier to the policy.
- Notifications are only sent once for a given alert. If you have assigned a notifier to a policy, you will not receive a notification unless a violation generates a new alert.
Red Hat Advanced Cluster Security for Kubernetes creates a new alert for the following scenarios:
- A policy violation occurs for the first time in a deployment.
- A runtime-phase policy violation occurs in a deployment after you resolved the previous runtime alert for a policy in that deployment.