---
title: "Okta security incident"
description: "What the retained public evidence establishes about the Okta incident, its attack path, impact, and response."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-09-19"
canonical_url: "https://www.ally.security/incidents/okta-security-incident-2022"
markdown_url: "https://www.ally.security/incidents/okta-security-incident-2022.md"
stix_url: "https://www.ally.security/incidents/okta-security-incident-2022/stix.json"
---

# Okta security incident

Lapsus$; compromised subprocessor (Sitel/Sykes) support engineer laptop. Superuser access to Okta's customer support tools for approximately 5 days.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Identity/IT
- **Operational impact:** Superuser access to Okta's customer support tools for approximately 5 days
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

In 2022, Okta experienced an incident in its identity/it environment. The retained source describes the attack path as follows: Lapsus$; compromised subprocessor (Sitel/Sykes) support engineer laptop. [1](#source-1)

The documented consequence was: Superuser access to Okta's customer support tools for approximately 5 days. [1](#source-1)

## Impact

- Documented impact: Superuser access to Okta's customer support tools for approximately 5 days. [1](#source-1)
- No financial loss, ransom amount, recovery cost, or regulatory penalty is established by the reviewed source evidence.

## Timeline

### March 24, 2022 — Documented public update

The [Okta's investigation of the January 2022 compromise](https://www.okta.com/blog/company-and-culture/oktas-investigation-of-the-january-2022-compromise/) records the incident facts used in this briefing. [1](#source-1)

### September 19, 2026 — Briefing updated

This briefing was last reviewed and updated on September 19, 2026.

## Threat Group & Attack Vector

The retained source describes the attack path as follows: Lapsus$; compromised subprocessor (Sitel/Sykes) support engineer laptop. The canonical record does not add intrusion steps beyond those supported by the source. [1](#source-1)

### Actors

- **Lapsus$** — identified in the supported attack description. [1](#source-1)

### TTPs

- No specific MITRE ATT\&CK technique is currently mapped for this case.

## Response

The retained source describes containment action intended to limit further access or disruption. [1](#source-1)
The retained source describes a forensic or specialist investigation of the incident. [1](#source-1)

This account is bounded to [Okta's investigation of the January 2022 compromise](https://www.okta.com/blog/company-and-culture/oktas-investigation-of-the-january-2022-compromise/). Details absent from that evidence are left unresolved rather than inferred. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/okta-security-incident-2022/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Okta's investigation of the January 2022 compromise

official · Okta

<https://www.okta.com/blog/company-and-culture/oktas-investigation-of-the-january-2022-compromise/>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   Okta security incident: The reviewed source documents the okta security incident involving Okta.
2. **Resulted In · 90% confidence · current**  
   Okta security incident: The retained source describes a forensic or specialist investigation of the incident.
3. **Affected Organization · 100% confidence · current**  
   Okta security incident: Okta
4. **Resulted In · 86% confidence · current**  
   Okta security incident: Lapsus$; compromised subprocessor (Sitel/Sykes) support engineer laptop.
5. **Resulted In · 90% confidence · current**  
   Okta security incident: The retained source describes containment action intended to limit further access or disruption.
6. **Resulted In · 88% confidence · current**  
   Okta security incident: Superuser access to Okta's customer support tools for approximately 5 days.
7. **Occurred At · 100% confidence · current**  
   Documented public update: 2022-03-24

</details>