14.2. Using the Red Hat Advanced Cluster Security for Kubernetes add-on
You can use the Red Hat Advanced Cluster Security for Kubernetes add-on to forward the vulnerability detection and compliance related data from the Red Hat Advanced Cluster Security for Kubernetes to Splunk.
Generate an API token with read permission for all resources in Red Hat Advanced Cluster Security for Kubernetes and then use that token to install and configure the add-on.
14.2.1. Installing and configuring the Splunk add-on 링크 복사링크가 클립보드에 복사되었습니다!
You can install the Red Hat Advanced Cluster Security for Kubernetes add-on from your Splunk instance.
To maintain backward compatibility with the StackRox Kubernetes Security Platform add-on, the source_type and input_type parameters for configured inputs are still called stackrox_compliance, stackrox_violations, and stackrox_vulnerability_management.
Prerequisites
-
You must have an API token with
readpermission for all resources of Red Hat Advanced Cluster Security for Kubernetes. You can assign the Analyst system role to grant this level of access. The Analyst role has read permissions for all resources.
Procedure
- Download the Red Hat Advanced Cluster Security for Kubernetes add-on from Splunkbase.
- Go to the Splunk home page on your Splunk instance.
-
Go to Apps
Manage Apps. - Select Install app from file.
- In the Upload app pop-up box, select Choose File and select the Red Hat Advanced Cluster Security for Kubernetes add-on file.
- Click Upload.
- Click Restart Splunk, and confirm to restart.
- After Splunk restarts, select Red Hat Advanced Cluster Security for Kubernetes from the Apps menu.
Go to Configuration and then click Add-on Settings.
-
For Central Endpoint, enter the IP address or the name of your Central instance. For example,
central.custom:443. - Enter the API token you have generated for the add-on.
- Click Save.
-
For Central Endpoint, enter the IP address or the name of your Central instance. For example,
- Go to Inputs.
Click Create New Input, and select one of the following:
- ACS Compliance to pull the compliance data.
- ACS Violations to pull the violations data.
- ACS Vulnerability Management to pull the vulnerabilities data.
- Enter a Name for the input.
- Select an Interval to pull data from Red Hat Advanced Cluster Security for Kubernetes. For example, every 14400 seconds.
- Select the Splunk Index to which you want to send the data.
- For Central Endpoint, enter the IP address or the name of your Central instance.
- Enter the API token you have generated for the add-on.
- Click Add.
Verification
To verify the the Red Hat Advanced Cluster Security for Kubernetes add-on installation, query the received data.
-
In your Splunk instance, go to Search and type
index=* sourcetype="stackrox-*"as the query. - Press Enter.
-
In your Splunk instance, go to Search and type
Verify that your configured sources are displayed in the search results.
14.2.2. Update the StackRox Kubernetes Security Platform add-on 링크 복사링크가 클립보드에 복사되었습니다!
If you are using the StackRox Kubernetes Security Platform add-on, you must upgrade to the new Red Hat Advanced Cluster Security for Kubernetes add-on.
You can see the update notification on the Splunk homepage under the list of apps on the left. Alternatively, you can also go to the Apps
Prerequisites
-
You must have an API token with
readpermission for all resources of Red Hat Advanced Cluster Security for Kubernetes. You can assign the Analyst system role to grant this level of access. The Analyst role has read permissions for all the resources.
Procedure
- Click Update on the update notification.
- Select the checkbox for accepting the terms and conditions, and then click Accept and Continue to install the update.
- After the installation, select Red Hat Advanced Cluster Security for Kubernetes from the Apps menu.
Go to Configuration and then click Add-on Settings.
- Enter the API token you have generated for the add-on.
- Click Save.
14.2.3. Troubleshoot the Splunk add-on 링크 복사링크가 클립보드에 복사되었습니다!
If you stop receiving events from the Red Hat Advanced Cluster Security for Kubernetes add-on, check the Splunk add-on debug logs for errors.
Splunk creates a debug log file for every configured input in the /opt/splunk/var/log/splunk directory. Find the file named stackrox_<input>_<uid>.log, for example, stackrox_compliance_29a3e14798aa2363d.log and look for issues.