Demo Center Home > Okta ITP Demo
Send SSF signals to raise the risk profile of targeted accounts and trigger remediation.
Walk through signaling a confirmed exposure to Okta and triggering remediation in real time.
OKTA ITP DEMO by SpyCloud
SpyCloud sends risk signals into Okta Identity Threat Protection over the Shared Signals Framework, so when a workforce identity is confirmed exposed, Okta raises that account’s risk profile and triggers remediation before the exposure can be used for account takeover or session hijacking. Because this data is recaptured from the criminal underground rather than public sources, Okta receives a confirmed exposure signal before that exposure is used against you.
This demo follows one exposure from SpyCloud detection to enforcement in Okta: the SSF signal, the risk profile rising in real time, and your configured response firing, from re-authentication to step-up MFA to Universal Logout.
SpyCloud's Okta Identity Threat Protection integration sends identity exposure signals over the Shared Signals Framework so Okta can raise account risk and stop account takeover and session hijacking in real time.
SpyCloud pulls session cookies, authentication tokens, MFA codes, and credentials.
Register your Okta tenant once as an SSF receiver. No agents, no exports.
SpyCloud matches every new record to your workforce identities.
Your Okta policies decide the response, with no analyst in the loop.
SpyCloud does not dump raw exposure records into Okta. SpyCloud classifies each exposure into a risk level, and your Okta entity risk policy decides the response at each tier. You set the thresholds in SpyCloud Connect.
Low
Okta notifies the user and prompts a password change at next sign-in
Medium
Okta challenges for MFA and revokes sessions from suspicious IPs
High
Okta elevates entity risk and enforces continuous MFA
Critical
Okta revokes active sessions, forces a password reset, and requires step-up authentication
Takeaway: Enforcement happens as the exposure is confirmed, not on the next export.
See which of your Okta users already have exposed session cookies, authentication tokens, MFA codes, and credentials in the criminal underground.
It shows SpyCloud sending a Shared Signals Framework risk signal to Okta Identity Threat Protection when it detects an exposed identity, prompting Okta to raise the account’s risk and trigger a configured remediation such as re-authentication or session termination.
The Shared Signals Framework is an open standard for security tools to exchange risk and session events in near real time. It lets SpyCloud communicate a confirmed identity exposure to Okta as it happens, so remediation is triggered immediately rather than through a periodic export.
A password reset addresses the credential, but an attacker with a stolen, still-valid session can retain access after the reset. By raising the account’s risk in Okta, the signal can trigger session termination and forced re-authentication as well, closing the session-based access that a reset by itself would leave open.
No. SpyCloud sends a risk signal for a confirmed exposure through the Shared Signals Framework, so Okta acts on the accounts it already manages. There is no bulk export or duplicate directory to maintain.
Depending on your policy, Okta can raise the account’s risk and require re-authentication, prompt step-up MFA, or invoke Universal Logout to revoke the user’s sessions across connected apps, which closes session-based access that a password reset alone would leave open.
2027 TOP PREDICTION: Attackers are exploiting the sessions, keys, and vendors you trust. Read on →