IBM QRadar - RSA Ready Implementation Guide
Solution Summary
This guide describes IBM QRadar integration with RSA ID Plus using SAML 2.0. Use this information to determine which use case and integration type your deployment will employ.Use Case
IBM QRadar can be integrated with RSA using My Page SSO. When integrated, users must authenticate with RSA to sign in to IBM QRadar.
Integration Types
My Page SSO provides Single-Sign-On (SSO) to IBM QRadar users' leveraging RSA self-service portal My Page. IdP-initiated SSO is 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 IBM QRadar using each integration type.IBM QRadar 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 | - | - | - | |
IBM QRadar 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 IBM QRadar 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 IBM QRadar components must be installed and working prior to the integration.
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 ServiceIBM QRadar
Known Issues
Only IdP-initiated SAML SSO flow is supported.When an SP-initiated SAML SSO flow is used, IBM QRadar sends a SAML request that includes the '<saml2p:RequestedAuthnContext Comparison="minimum">' tag. Currently, the 'Comparison="minimum"' is not supported, and IBM does not permit configuration of the 'RequestedAuthnContext' parameter in the SAML request.
As a result, My Page SP-initiated SAML SSO and Relying Party SAML SSO will not function correctly.
For more details, refer to the document: SAML 2.0 Requirements for Service Providers
