Before starting to add two-factor authentication to Splunk Enterprise, make sure that Duo is compatible with your Splunk install. Log into Splunk's web interface and click the about link in the top right corner.
Splunk Enterprise 6.5 and later on-premises solutions natively include Duo Security MFA. Users of these Splunk versions do not need to download and install the Duo plugin from Duo. Instructions for Splunk 6.5 and later
If you're using Splunk 6.4 or earlier, you'll need to download and install a Duo plugin. Instructions for Splunk versions 6.4 and earlier
Splunk Cloud does not support Duo MFA.
This application communicates with Duo's service on TCP port 443. Firewall configurations that restrict outbound access to Duo's service with rules using destination IP addresses or IP address ranges aren't recommended, since these may change over time to maintain our service's high availability. If your organization requires IP-based rules, please review this Duo KB article.
The security of your Duo application is tied to the security of your secret key (skey). Secure it as you would any sensitive credential. Don't share it with unauthorized individuals or email it to anyone under any circumstances!
The new Universal Prompt provides a simplified and accessible Duo login experience for web-based applications, offering a redesigned visual interface with security and usability enhancements.
|Universal Prompt||Traditional Prompt|
Read the Universal Prompt Update Guide for more information about the update process and the new login experience for users.
Migration to Universal Prompt for your Splunk application is a two-step process:
Splunk needs to update Splunk to support the Universal Prompt, but the update isn't available yet. The "Universal Prompt" section reflects this status as "Waiting on App Provider" with the activation options inaccessible. Please contact Splunk to request Duo Universal Prompt support for Splunk.
In the meantime, you can use Duo with Splunk and the traditional prompt experience.
After Splunk makes the necessary changes available you may need log in to Splunk as an admin to enable Duo Universal Prompt support.
You'll later return to the settings on this page to activate the Universal Prompt for your Splunk users after Splunk releases the update.
Click the See Update Progress link to view the Universal Prompt Update Progress report. This report shows the update availability and migration progress for all your Duo applications in-scope for Universal Prompt support. You can also activate the new prompt experience for multiple supported applications from the report page instead of visiting the individual details pages for each application.
Log into Splunk Enterprise as an admin and navigate to Settings → Users and Authentication → Access Controls.
Click on Authentication Method.
Under "Multifactor Authentication", select Duo Security and then click Configure Duo Security.
Fill out the form with your Duo Splunk application information:
|Integration Key||Your integration key|
|Secret Key||Your secret key|
|API Hostname||Your API hostname (i.e.
|Authentication behavior when Duo Security is unavailable||Choose **Let users login** to allow Splunk logins when Duo Security cloud services are unreachable, or **Do not let users login** to prevent access to Splunk without Duo authentication.|
|Connection Timeout||The maximum limit, in seconds, to complete authentication.|
Splunk automatically generates an Application Secret Key for you. If you'd like to use your own, it should be a mix of letters and numbers at least 40 characters long.
You can generate a random string in Python with:
import os, hashlib print hashlib.sha1(os.urandom(32)).hexdigest()
Click the Save button when done. You can now test your setup
This configuration was tested against versions 4.3.2, 5.0.7, 6.0.1, and 6.1.4. Splunk 6.2-6.4 must be started in "legacy mode" to use the Duo plugin. See instructions for Windows 6.2 , 6.3, or 6.4 and Linux 6.2, 6.3, or 6.4 at Splunk's documentation site).
From the command line, run the install script from within the duo_splunk directory with the following arguments:
$ ./install.sh -i <your_ikey> -s <your_skey> -h <your_host> -d <splunk_location>
||Your integration key
||Your secret key|
||Your API hostname
||The directory where Splunk is installed. Defaults to /opt/splunk if not specified.|
All paths in these instructions are relative to where your top level splunk/ directory is.
Apply the account.py.diff patch to lib/python2.7/site-packages/splunk/appserver/mrsparkle/controllers/account.py
Edit lib/python2.7/site-packages/splunk/appserver/mrsparkle/controllers/account.py to add your Duo account specific API keys (IKEY, SKEY, DUO_HOST, and AKEY).
Copy duoauth.html into share/splunk/search_mrsparkle/templates/account/
Copy duo.web.bundled.min.js into share/splunk/search_mrsparkle/exposed/js/contrib/
Copy duo_web.py into lib/python2.7/site-packages/
$ bin/splunk restart splunkweb
Upon your next login you will be prompted to enroll or authenticate your user using Duo.
Open a new browser and log into Splunk. After you complete primary authentication, the Duo enrollment or login prompt appears.
If you plan to permit use of WebAuthn authentication methods (security keys, U2F tokens, or Touch ID) in the traditional Duo Prompt, Duo recommends configuring allowed hostnames for this application and any others that show the inline Duo Prompt before onboarding your end-users.
The Duo Universal Prompt has built-in protection from unauthorized domains so this setting does not apply.