Company security usually depends on your ability to come up with a diverse set of passwords and then manage them. Remembering all of them is considered a tad too difficult for most mere mortals, so a number of password storage apps have emerged. But they too have to be secured, and ultimately results in inefficient access and flawed security. Single-sign on (SSO) is still preferred, but to make it effective, companies like Okta have to secure integration across a number of apps.

Okta is a security identity cloud allowing SSO onto apps via a single set of credentials, usually an organization or company. The advantage of Okta is clear. With a company’s access to a given platform already in hand, all that’s needed is set up of a new company email address for new employees to access a tool. Should someone leave that company, the elimination of the email address automatically cuts off access to all the company’s app accounts (and thus secures its information).

Logz.io is available both as an integratable app to Okta, as well for the import of Okta logs. Tracking Okta’s access logs is a quick way to observe its effectiveness. This tutorial will walk through 1) using Okta integration with Logz.io and adding it to Okta’s SSO, and 2) exporting Okta logs to the Logz.io system and a custom Okta dashboard in Kibana.

Okta Rules in Logz.io Cloud SIEM

Tacking problems with SSO means laying out which cases should prompt your immediate attention. Sign-on failures of various kinds—and particularly muli-factor authentication failures—should be ranked in order of importance. This is where a tool like Logz.io’s alerting comes into play.

We’ve created a set of 10 default rules for Okta users in Logz.io Cloud SIEM, ranked by order of severity. The most severe alert triggers itself when multiple failed authentications occur in a short period of time, particularly from several unknown users.

Should this sort of incident occur, you should investigate the event in line with your organization’s security policies, block certain IP addresses, and/or reinforce multi-factor authentication settings in Okta.

Our next highest priority triggers are on failed multi-factor authentication and whenever administrative privileges are granted to a user or to a whole group. Medium-level alerts are set by default for other failed authentication attempts and the change of app sign-on policies. Of course, you can additionally configure alerts for other preferences.

Configure Alerts in Logz.io Cloud SIEM for Okta

Configure Alerts in Logz.io Cloud SIEM for Okta

Okta Integration & Logz.io SSO

First, request SSO access from Logz.io by sending an email to help@logz.io telling us that you want to set up Okta SAML SSO for your Logz.io account. Provide your Logz.io account ID and Logz.io account token and it should be a fast process. Logz.io will send you SAML info to plug into Okta.

Second, in Okta, click Admin. Afterwards, in the Shortcuts panel to the right, click Add Applications. On the left, click Create New App. In the Create a New Application Integration panel and on its Platform list, select Web. Next, click the SAML 2.0 option, and then Create

The “Create SAML Integration” page should then appear.

Next, on the Create SAML Integration page, set your App name to “Logz.io” and hit Next. This will bring you to the Configure SAML tab. In that tab, paste the SAML information you got from Logz.io Support: your single sign-on URL and audience URI (SP Entity ID):

Keep these settings unchanged: Default RelayState, Name ID format, or Application username. Then in the Attribute Statements, set 1) Name to email, 2) Name format to unspecified, and 3) Value to ${user.email}.

After that, configure Okta to send user groups in the Group Attribute Statements section by setting 1) Name to groups, 2) Name format to unspecified, and 3) typing any expression (the field can’t be left blank) for the groups you want having access to Logz.io via Filter.

Group Attribute Settings in Okta (optional)

Group Attribute Settings in Okta (optional)

Send Info to Logz.io Support

On the right side of the page, click Download Okta Certificate. Download the certificate file and zip it. You’ll attach the zip file to your next email to the Support team. Click Next, select I’m an Okta customer adding an internal app, and then click Finish.

Next, you’ll have to grab your endpoint info. Browse to the Sign On tab, and then click View Setup Instructions. Copy the Identity Provider Single Sign-On URL, and paste this in the email that you’ll send to the Support team.

Configure Alerts in Logz.io Cloud SIEM for Okta

Set Up SAML in Okta

Draft a new email to Logz.io Support (help@logz.io), and include these items:

  • Your zipped certificate
  • Your Identity Provider Single Sign-On URL

NOTE: If you want, you can restrict Logz.io access in your organization. By default, all Okta users with Logz.io access can sign in to your Logz.io accounts. You can restrict this access from the Manage users page for each of your accounts. Click Add group, then paste your group’s name from Okta. Do this for each group that should have access to this account.

Once Support has created your Okta + Logz.io connection, you’re done! You can start logging in to Logz.io through your Apps portal.

Ship Okta Logs to Logz.io

To ship Okta logs, deploy a Docker container to collect the logs and forward them to Logz.io. You will need Okta admin privileges to access the right info from the Okta developer console.. 

Get the 1) API token and 2) issuer URI from the Okta developer console. 

1) Navigate to API, then Tokens. Create a token and hold onto it (paste it in your text editor for later).
2) Click the Authorization Servers tab. Copy your Okta subdomain from the Issuer URI column and also paste that in your text editor alongside the API token.

Authorization Servers in Okta

Authorization Servers in Okta

In the example above, you’d have copied “dev-123456”.

Logz.io Docker Image

Next, Download the logzio/logzio-okta image.

docker pull logzio/logzio-okta

Then, run the Docker image.

docker run logzio/logzio-okta

Here is the list of configurables you should set in the image.

--detach \
--restart always \
--name Okta \
--env LOGZIO_TOKEN=<<SHIPPING-TOKEN>> \
--env LOGZIO_LISTENER_HOST=<<LISTENER-HOST>> \
--env OKTA_API_KEY=<<OKTA-API-KEY>> \
--env OKTA_TENANT=<<OKTA-ISSUER-URI>> \
-t logzio/logzio-okta

Give your logs a few minutes to get from your system to ours, and then open Kibana. From there, look at our available Okta prebuilt security rules and dashboard or create one yourself using the visualization tool.