Splunk Enterprise - RSA Ready Implementation Guide
Solution Summary
This guide describes Splunk Enterprise integration with RSA (or ID Plus) using SAML 2.0. Use this information to determine which use case and integration type your deployment will employ.Use Case
Splunk Enterprise can be integrated with RSA using My Page SSO. When integrated, users must authenticate with RSA to sign in to Splunk Enterprise.Integration Types
My Page SSO provides Single-Sign-On (SSO) to Splunk Enterprise users leveraging RSA self-service portal My Page. Both SP-initiated SSO and IdP-initiated SSO are supported.Modern Cloud-hosted SSO with My Page replaces the existing SAML SSO support with the IDR.
Supported Features
This section shows all the supported features by integration type and by RSA components. Use this information to determine which integration type and RSA component your deployment will use. The next section in this guide contains the instruction steps for how to integrate RSA with Splunk Enterprise using each integration type.Splunk Enterprise Integration with RSA Cloud Authentication Service
| Authentication Methods | RSA MFA API (REST) | RADIUS | Relying Party | My Page SSO |
| Approve | - | - | - | |
| LDAP Password | - | - | - | |
| SecurID OTP | - | - | - | |
| Authenticate OTP | - | - | - | |
| Device Biometrics | - | - | - | |
| SMS OTP | - | - | - | |
| Voice OTP | - | - | - | |
| FIDO Security Key | - | - | - | |
| QR Code | - | - | - | |
| Emergency Access Code | - | - | - |
Splunk Enterprise Integration with RSA Authentication Manager
| Authentication Methods | RSA MFA API (REST) | RADIUS | Authentication Agent |
|---|---|---|---|
| RSA SecurID | - | - | - |
| On Demand Authentication | - | - | - |
| Risk-Based Authentication | - | - | - |
| Supported | |
| - | Not supported |
| n/t | Not yet tested or documented, but may be possible |
| n/a | Not applicable |
Configuration Summary
This section contains instruction steps that show how to integrate Splunk Enterprise with RSA using all of the integration types.This document is not intended to suggest optimum installations or configurations. It is assumed that the reader has both working knowledge of all products involved, and the ability to perform the tasks outlined in this section. Administrators should have access to the product documentation for all products to install the required components.
All RSA and Splunk Enterprise components must be installed and working prior to the integration.
This section of the guide includes links to the appropriate sections for configuring both sides for each use case.
Integration Configuration
RSA Cloud Authentication Service
RSA Terminology Changes
The following table describes the differences in the terminologies used in the different versions of RSA products and components.| Previous Version | New Version | Examples/Comments |
| Company ID | Organization ID | |
| Account | Credential | |
| Token | OTP Credential | SecurID OTP Credential |
| Tokencode | OTP/Access Code | SecurID OTP, SMS OTP, Voice OTP Emergency Access Code, Disable Access Code |
| Hardware Token | Hardware Authenticator | |
| Device Serial Number | Binding ID | |
| Device | Credential/Authenticator | |
| Device Registration Code | Registration Code | |
| Authenticate App | Authenticator App |
Certification Details
RSA Cloud Authentication ServiceSplunk Enterprise
Known Issues
For Relying Party, Splunk platform shows the following error: “Verification of SAML assertion using the IDP’s certificate provided failed. Error: failed to verify signature with cert”.The Splunk platform needs certificates that have the root, intermediate, and leaf certificates to be successfully configured. (Reference: Splunk Community) The default X.509 certificate that is generated from the Relying Party configuration does not include all three parts and does not have the option to generate a new certificate bundle such as the My Page configuration.
