Okta SSF

Material integrates with Okta using the Shared Signals Framework (SSF). This SSF integration enhances security by sending notifications to your Okta instance whenever user risk reports are created or updated in Material.

To set up your integration, complete a few steps in both Material and in Okta.

Before you begin, open a tab in Material and Okta each to work in both concurrently.

How to integrate with Okta SSF

Part One: Create a new Okta Integration in Material

Create an Okta Admin

Always review Okta's documentation directly for up to date instructions.

1. In Okta, create a new Okta admin (e.g. "Material Admin") and assign the required roles based on selected capabilities.

   1. Groups - Group, Help Desk, App, or Read Only Admin
   2. MFA Status - App or Read Only Admin
   3. End-User Verification - Help Desk Admin Log in to your Okta organization as the new admin.
2. From the Security menu, select API then select Tokens.
3. Click Create Token.
4. Name your token (e.g. "Material") and click Create Token.

Copy your API token because you will only see it one time.

Create a new integration in Material

1. From the top toolbar, click Integrations.
2. Click Create Integration.
3. Under Identity, choose Okta SSF.
4. Click Create new integration.

1. Complete the required fields:

   1. Org URL: your complete Okta Org URL (e.g. https://acme.okta.com)
   2. Token: The token you created in step 4.
2. Confirm Shared Signals Framework (SSF) is checked.
3. Click Add Event to choose the event(s) that will trigger your stream.

   

How to choose events

Use the form to build the trigger based on multiple filters.

• The most common event used is Issue Change . It covers most needs.
• Other common filters are:

  • Severities: trigger based on an issue severity change
  • Detection: trigger based on a specific detection
• Choose the option to Include events for messages being added / removed / interacted with in a phishing case if you want to also trigger based on individual message level changes (rather than just issue level changes).

---

• While you can include multiple events in one integration, you can only include one of each event type (i.e. one issue change, etc.) All the filters must match to trigger the event. If you need to trigger webhook using OR logic, create multiple integrations with different event parameters.

• Toggle events off/on at any time in the integration view.
• Once your webhook starts firing, the last time an event triggered is included in the integration view, under Events:

1. Copy the Material Outbound IPs.
2. Save the integration.

In Okta, create an IP Zone

1. Navigate to Security > Networks then click Add Zone to create a new IP Zone.
2. Name the zone and paste the Outbound IPs from Material (step 12) into the Trusted Proxy IPs field. This lets Okta display the correct geographic location during identity verification.
3. Click Save in Okta to save the IP Zone.

Part Two: Set up an OKTA SSF receiver

Create a stream in Okta

1. In Okta, select Security > Device Integrations > Receive shared signals.
2. Click Create Stream.
3. Enter a name for the stream (e.g. "Material SSF Stream")
4. Select Well-known URL:
5. In Well-known URL field, paste: https://<your-material-instance>/.well-known/ssf-configuration/ssf/okta/<your-stream-id>
6. Click Create. This validates Okta is able to communicate with Material. If this is successful it will close the modal.

   1. If an error occurs, the integration likely isn't enabled on the Material side. Return to steps 5-13 and confirm you Saved.
7. Your receiver should now display in Okta:

   

   Your receiver displays in Okta

Wrap-up

Now the event subscription is created and Okta will start receiving User Risk Report Change events from Material for issue change events (create and update). In the Okta System Log, you will see events like this: