About Splunk Secure Gateway
Splunk Secure Gateway is included in Splunk Cloud version 8.1.2103 and higher and Splunk Enterprise version 8.1.0 and higher. To view the Splunk Secure Gateway version that's associated with each Splunk platform version, see the Splunk Secure Gateway release notes.
Splunk Secure Gateway lets users register their mobile devices and admins configure their mobile app deployment for the Connected Experiences apps. Splunk Secure Gateway also serves as the back-end infrastructure for delivering messages over a secure cloud-based bridge. This back-end infrastructure is called Spacebridge. Splunk Secure Gateway is installed on all members of the search head cluster.
To learn more about Spacebridge and the Connected Experiences apps that are compatible with Splunk Secure Gateway, see About the Splunk Secure Gateway security process.
Spacebridge has been certified to meet SOC2, Type 2 and ISO 27001 standards. Splunk Cloud customers who have specifically purchased a HIPAA or PCI-DSS regulated environment may transmit the applicable regulated data to Spacebridge as it is HIPAA and PCI-DSS compliant. Spacebridge may not be used in environments that require the FIPS 140-2 standard for cryptographic modules. See Splunk Secure Gateway and Spacebridge Compliance Standards to learn more.
Splunk Secure Gateway offers the following features:
|Enable the Connected Experiences mobile apps||Splunk Secure Gateway is a required companion app for the following Splunk Connected Experiences mobile apps:
|Register mobile devices||Users can register their mobile devices to securely authenticate to a Splunk platform instance.|
|Configure and troubleshoot your Splunk Connected Experiences mobile deployment||View the Splunk Secure Gateway status dashboard, manage registered devices, and optionally set up a Mobile Device Management (MDM) deployment.|
Migrate from Splunk Cloud Gateway to Splunk Secure Gateway
If you're already using the Connected Experiences apps with Splunk Cloud Gateway, see the following information for transitioning the mobile apps.
See Migrate from Splunk Cloud Gateway to Splunk Secure Gateway for important migration information and how to copy your Splunk Cloud Gateway data over to Splunk Secure Gateway.
Get started with Splunk Secure Gateway
See Get started with Splunk Secure Gateway for the requirements and steps for getting started with Splunk Secure Gateway.
Users must use Splunk Secure Gateway toregister their device to securely connect to a Splunk platform instance and use the Connected Experiences apps. There are multiple ways your users can register their devices:
|Authentication Code||Users enter the authentication code in the mobile app into the Register tab in Splunk Cloud Gateway.|
|Mobile Device Management (MDM)||Use an MDM provider to securely allow users to register their device within the mobile app itself. See About MDM and in-app registration to learn more.|
|Security Assertion Markup Language (SAML) authentication||Use a supported identity provider (IdP) to enable SAML authentication for user login. See How devices authenticate to your Splunk platform with SAML authentication to learn more about how to set up SAML authentication.|
|MDM with SAML authentication||You can use an MDM provider with an IdP. See Set up SAML authentication for Splunk Secure Gateway for more information about using MDM with SAML authentication.|
See Register your mobile device to a Splunk instance for the various ways users can register their device.
Get started with Splunk Secure Gateway
This documentation applies to the following versions of Splunk® Secure Gateway: 2.5.6 Cloud Only, 2.5.7, 2.6.3 Cloud only, 2.7.3 Cloud only, 2.7.4, 2.8.4 Cloud only, 2.9.1 Cloud only, 2.9.3 Cloud only, 2.9.4 Cloud only, 3.0.9, 3.1.2 Cloud only, 3.2.0 Cloud only, 3.3.0 Cloud only
Feedback submitted, thanks!