splunk partner logo

Splunking Okta, and Okta'ing Splunk! - Part 2

21/06/19 – Author: Jamie Turbill– Certified Splunk & Okta Consultant

Back in February, I previously blogged about how you could very easily integrate single sign-on with Splunk using Okta (Part 1 of Blog). The 2nd part in this series covers how you can gain visibility and expand on the reporting available within Okta using Splunk, with the Splunk Add-on for Okta. If you haven’t read my earlier blog, I highly recommend it if you are looking to add SSO with SAML easily to Splunk.

Okta has a great out-of-the box available for reporting on events within the platform, including usage reports, SSO authentication events, password health and more. However, what if you have a very specific report you need to run? Or, what if you need to correlate the data within Okta with data from your applications/services – e.g. for your security requirements.

Splunk is completely flexible and scalable, allowing you to ingest data from all sources within the Okta platform. Using the Splunk search processing language (SPL) you can turn the raw system log events into dashboards, reports and alerts that you create, and this can be as specific as you like.

So, you’ve got SSO, but how do you report and audit on Okta with Splunk?

In Okta, go to your Okta admin portal and click on Applications > Add Application and simply search for “Splunk”.

Click on “Learn More” for the Splunk Add-on for Okta. This will provide you with a brief description of the Splunk add-on for Okta.
Click on “More details about the Okta / Splunk integration” to be taken to Splunkbase.

Once on Splunkbase, use the “Download” option to download the add-on for Okta, and then install this as appropriate for your Splunk deployment. This add-on is built and supported by Okta.

Okta provides a complete step-by-step documentation for this add-on here, including all prerequisites and information about where this add-on can and should be installed in your Splunk deployment.

I’m going to cover the setup from the simplest deployment type, an all-in-one Splunk instance, but you should refer to this documentation for your own environment and for anything not covered below.

For an all-in-one Splunk instance, you can simply install the application by using the “Upload App” functionality within Splunk Web. In Splunk, from the “Search & Reporting” app, click on “App: Search&Reporting” > “Manage Apps” as shown below:

To upload and install the add-on, click on “Install app from file”, Choose File and select the Add-on you downloaded. Then “Upload”
Splunk will now install the add-on. You will be prompted to restart Splunk after installation, do this by clicking on “Restart Now”.

You now need to obtain an API key from Okta to allow Splunk to collect Okta’s system logs and other information from your Okta tenant. Your Splunk instance collecting this data needs to be able to connect to Okta on HTTPS port 443.

To generate an API key, go to your Okta tenant. From the Okta admin portal and click on Security > API > Tokens > Create Token. Then enter a name for the API token. E.g. “Splunk_Prod”

And then “Create Token”. Copy the token generated (this will be needed later).

Back in Splunk, now go to Configuration > Accounts > Add.

Enter the following

  1. Account Name (this can be named as required)
  2. Okta Domain (enter your full Okta address)
  3. API token (paste in the value that you have copied)

Then click “Add” to save

Once saved, click on “Inputs” > Create New Input

We recommend that you create 1 input for each metric type that can be collected. The metric types are:

  1. Logs – Collects Okta System Log Events
  2. Users – Collects User Information (such as user profile, user activity)
  3. Groups – Collects Group Information (such as group membership, group changes)
  4. Apps – Collects App Information (such as app name, SSO/provisioning configuration, assignments etc)

It is best practice to use a separate index for data collection. Create an index if necessary from Settings > Indexes

Use the following when setting up inputs within the add-on.

Above: Logs
Above: Users
Above: Groups
Above: Apps
Once all added, your inputs list should look similar to the above

That should be all that’s required!

Double check you are receiving data. Run a search for index=okta and see if you are getting results.

The events that are retrieved should be in a JSON format and should represent the events seen within the Okta system log.

You can now use your Okta data to create dashboards, reports and alerts as per your requirements within Splunk!

Some example dashboards are below that you could create with this data:

As you can see from the screenshots above, it’s now easy to get complete end-to-end reporting and monitoring of my Okta platform, extending the functionality of the reports and system log available within Okta. 

This is now in addition to what we covered in part 1 – where we have easy and seamless SSO access to our Splunk environment.

Splunking Okta, and Okta'ing Splunk Part 1

Interested in seeing a demo of Splunk or Okta's potential uses for your Organisation?

Scroll to Top