Deployment Architecture

ForgeRock SSO for Splunk Enterprise but not Splunk ES


We currently have a Splunk deployment consisting of Splunk Enterprise and Splunk ES. We are thinking of incorporating Splunk Enterprise into our corporate enterprise SSO solution (i.e. ForgeRock), but we're receiving some pushback from our Security Team on also incorporating Splunk ES as part of the enterprise SSO solution. For some context, access to ES is restricted to our Security Team while Enterprise is open to our Production Operations and DevOps Teams. Access is segregated based on LDAP groups and roles, so the Prod Ops and DevOps Teams can not access ES since they are not provisioned a Splunk ES role and neither are they part of an LDAP group associated to a Splunk ES group.

I have a couple of questions:

  1. Is it generally considered a "bad practice" to allow SSO access to your SIEM (i.e. Splunk ES)

  2. Is it possible for Splunk to allow ForgeRock SSO access to Splunk Enterprise while retaining non-SSO access (i.e. input your Windows AD credentials) for Splunk ES? I'm assuming this should be case since a different LDAP strategy would be identified for Enterprise and ES?

Labels (1)
0 Karma
Get Updates on the Splunk Community!

Build Scalable Security While Moving to Cloud - Guide From Clayton Homes

 Clayton Homes faced the increased challenge of strengthening their security posture as they went through ...

Mission Control | Explore the latest release of Splunk Mission Control (2.3)

We’re happy to announce the release of Mission Control 2.3 which includes several new and exciting features ...

Cloud Platform | Migrating your Splunk Cloud deployment to Python 3.7

Python 2.7, the last release of Python 2, reached End of Life back on January 1, 2020. As part of our larger ...