Case Study 11 min read· 16 October 2026

MGM Resorts 2023 Cyberattack: An ISO/IEC 27001 Control Teardown

MGM’s 2023 cyberattack: vishing, identity risk, financial disclosures and ISO/IEC 27001 lessons. Explore the free documentation kit.

Aegora Cyber Intelligence

Breach analysis and control lessons

Publication note: This teardown preserves the supplied research and its evidence labels. Historical and regulatory statements reflect that research cutoff, not a fresh verification at publication. Control mappings are illustrative, not findings of ISO/IEC 27001 nonconformity. Kit document names and reference codes in the source are illustrative labels and may differ from the current catalog; documentation alone is not evidence of an operating control.

Evidence boundary. MGM has not published a full technical forensic report. This article therefore separates company/regulator-confirmed facts from media and researcher reporting, and identifies analytical inferences as such. MGM’s ISO/IEC 27001 certification status at the time is not independently verifiable from public sources.

Breach teardown

2. Incident timeline and what happened

MGM Resorts International’s September 2023 incident is a useful case study in a familiar but consequential failure chain: a human support channel became an identity-proofing channel; identity access expanded into privileged control; then business operations were deliberately interrupted to contain the threat.

DateEventEvidence status
8–10 September 2023Security reporting places initial compromise and subsequent attacker activity in this window. Researchers reported that the intruders used voice phishing (vishing), impersonating an employee to MGM’s IT help desk and manipulating a credential/MFA reset.Reported — MGM did not publish a forensic account. Wired’s contemporary account and the later CISA/FBI Scattered Spider advisory describe this operating pattern.
11–12 SeptemberGuests reported failures affecting reservation and digital-key services; MGM announced that a cybersecurity issue was affecting certain U.S. systems. It said it had taken some systems offline while investigating with external experts and law enforcement.Confirmed by MGM. MGM’s 12 September statement.
12 September onwardOperational disruption extended across MGM’s U.S. estate. Contemporary reporting documented inaccessible reservation functions, digital room keys, slot machines/casino systems and ATMs; properties used manual workarounds. MGM later confirmed that its containment measures caused material disruption, particularly in Las Vegas.System-by-system effects are reported in Reuters and contemporaneous coverage; the underlying disruption is confirmed in MGM’s 5 October Form 8-K.
20 September (reported)Media reported that MGM had restored operations after roughly ten days. By 5 October, MGM stated that its domestic operations had returned to normal and “virtually all” guest-facing systems were restored.Restoration date is reported; normal operations/virtually all guest-facing systems are confirmed by the 8-K.
5 OctoberMGM disclosed that an unauthorized third party had obtained certain customer personal information, primarily concerning customers who transacted with MGM before March 2019. It said it had no evidence that passwords, bank-account numbers or payment-card information were obtained.Confirmed by MGM in the 8-K.

Initial access, attribution and ransomware

Public reporting attributed the intrusion to the financially motivated actor commonly tracked as Scattered Spider, UNC3944, 0ktapus/Oktapus and Octo Tempest, working with the ALPHV/BlackCat ransomware ecosystem. MGM’s public filings did not name the actors or confirm the precise initial-access path. The frequently repeated account—an attacker used publicly available employee information, called the help desk, impersonated an employee, then had credentials or MFA re-enrolled—is therefore reported, not MGM-confirmed. It is nonetheless consistent with the tactics documented by CISA and the FBI: help-desk impersonation, password resets, MFA-token transfer, push-fatigue and use of legitimate remote-management tooling. CISA/FBI AA23-320A

Reports further describe takeover of MGM’s Okta and Azure administration environment and subsequent ransomware deployment, including encryption of virtual infrastructure. Treat claims about a specific Okta “super-admin” takeover, MFA fatigue in this exact intrusion, or the number of affected hypervisors as reported technical detail, not a company finding. The operational consequence is not in doubt: MGM itself confirmed it shut down systems as part of containment, and that the disruption was concentrated in September. MGM 8-K

Breach teardown

3. Enforcement actions and regulatory response

MGM-specific disclosure, litigation and oversight

MGM’s 12 September 2023 public statement was followed by a 5 October 2023 Form 8-K, which quantified the operational and financial effect and described the personal information accessed. That filing is the primary public record for what MGM itself confirmed. SEC Form 8-K

Customer litigation followed. In January 2025, the U.S. District Court for the District of Nevada preliminarily approved a $45 million settlement in consolidated litigation concerning both MGM’s 2019 and 2023 data incidents; it is not a clean measure of the 2023 incident alone and must not be treated as one. The settlement administrator describes the two-incident scope and subsequent final-approval process. MGM Data Settlement

Regulatory scrutiny was broader than a single state case. MGM challenged an FTC civil investigative demand in 2024; the FTC later agreed to dismiss the related proceeding without prejudice. Separately, MGM’s later SEC risk disclosures state that it continues to monitor the timing and outcome of investigations by state regulatory authorities relating to the 2023 incident. Public records reviewed for this article do not support naming a particular state attorney general as having brought a completed enforcement action. This is the precise basis for referring to continuing state-regulator/attorney-general inquiry rather than claiming a concluded AG penalty. FTC case materials | MGM annual filing

Broader, related law-enforcement developments

These actions concern the threat ecosystem; they are not findings that MGM was a victim in each matter.

  • On 16 November 2023—not October—the FBI, CISA and partners issued the #StopRansomware advisory AA23-320A, “Scattered Spider.” It catalogs the group’s social-engineering and identity-focused tradecraft and recommends phishing-resistant MFA, isolated tested backups and application controls. CISA advisory
  • On 19 December 2023, DOJ announced disruption of ALPHV/BlackCat infrastructure and the FBI’s decryption capability. The announcement said the FBI had aided more than 500 victims and prevented about $68 million in demanded ransoms at that point. This was a broader operation, not a remediation announcement for MGM. DOJ announcement
  • On 18 September 2025, DOJ announced charges against U.K. national Thalha Jubair, alleged to be associated with Scattered Spider, after his UK arrest two days earlier. The allegations cover a broad cyber-extortion scheme; the announcement does not establish that he conducted MGM’s intrusion. DOJ charging announcement

Finally, do not conflate MGM with Okta’s separate late-2023 compromise of its customer-support system. That incident affected Okta customers and is relevant to the same identity-threat landscape, but it is not evidence that Okta support caused MGM’s breach. Okta’s disclosure

Breach teardown

4. Financial impact analysis

The financial discipline here matters. MGM’s approximately $100 million figure was an estimate of the negative third-quarter impact on Adjusted Property EBITDAR for Las Vegas Strip Resorts and Regional Operations combined—not a confirmed cash loss, revenue loss or total breach cost. MGM said the final scope was still being assessed. Form 8-K

ItemAmountClassification and treatment
One-time incident expenses in Q3 2023 (technology consulting, legal and other advisors)Less than $10 millionConfirmed, but not a precise figure. It establishes a confirmed amount below $10m; it cannot support a precise confirmed-total calculation.
Negative impact to Adjusted Property EBITDARApproximately $100 millionEstimate—excluded from confirmed totals. This is not described by MGM as a settled cost.
Insurance claim / recoveryMGM said cyber insurance “should be sufficient”Expected-but-unconfirmed at the October 2023 disclosure. No recovery is counted here. Later financial statements should be consulted for any separately recognized proceeds.
Las Vegas occupancy, September 202388% vs. 93% in prior-year periodConfirmed operating metric, not a breach-cost line item.
“$59 million in one-time costs”Not verifiedExcluded. MGM’s controlling 5 October 2023 filing says less than $10 million, not $59 million, for Q3 one-time expenses.

The confirmed financial picture from the contemporaneous filing is therefore an incomplete disclosure, not a total-loss estimate: MGM confirmed less than $10 million in specific one-time expenses, while its ~$100 million EBITDAR impact remained an estimate. MGM also said its cyber insurance should be sufficient to cover the financial impact of the operational disruption and associated expenses; that statement is not confirmation of an insurer payment. SEC Form 8-K

MGM’s September Las Vegas occupancy was 88%, compared with 93% in the prior-year period. That correlation is useful operating context, but it should not be converted mechanically into revenue loss or added to other amounts. Likewise, any short-term share-price movement is market context—not a confirmed breach cost—and is excluded from this analysis. SEC Form 8-K

Breach teardown

5. ISO/IEC 27001:2022 control mapping

The mapping below is conditional: MGM has not released a full forensic report. “Reported” rows rely on credible public reporting; “analytical inference” identifies the control most relevant to the observed consequence, not a proven control failure.

Publicly evidenced failure / gapStatusISO/IEC 27001:2022 control mappingWhy it matters and limit
Help-desk impersonation reportedly enabled a password/MFA reset or enrollment.ReportedA.5.16 Identity management; A.5.17 Authentication information; A.8.5 Secure authenticationRequire independent identity verification, controlled recovery and phishing-resistant authentication. Limit: these controls reduce social-engineering success but cannot guarantee a determined attacker will not exploit a human process.
Reported access to an Okta administrative environment created disproportionate control-plane risk.ReportedA.8.2 Privileged access rights; A.5.18 Access rightsSeparate admin accounts, make elevation time-bound, and review identity-provider roles and MFA-device changes. Limit: privileged-access governance cannot prevent every authorized admin action from being abused.
Vishing targeted a human support process.ReportedA.6.3 Information security awareness, education and training; A.6.8 Information security event reportingTrain service-desk staff to stop, verify and escalate anomalous reset requests. Limit: awareness changes decision quality; it does not make identity claims inherently trustworthy.
Ransomware and disruptive containment affected guest-facing operations.Confirmed disruption; reported ransomware attributionA.8.7 Protection against malware; A.8.8 Management of technical vulnerabilitiesUse layered endpoint/server protection, rapid patching and application control. Limit: malware and vulnerability controls lower the likelihood and blast radius; they do not assure prevention of novel or credential-led attacks.
Broad operational effect suggests material dependencies between enterprise identity/IT and property services.Analytical inferenceA.8.20 Network security; A.8.21 Security of network services; A.8.22 Segregation of networksSegment casino, hotel, identity and recovery environments; validate control paths. Limit: segmentation cannot eliminate disruption where critical services intentionally share dependencies.
Attackers reportedly used legitimate administration tools and cloud identity systems.ReportedA.8.15 Logging; A.8.16 Monitoring activitiesCentralize identity, help-desk, endpoint and cloud-admin telemetry; alert on reset/enrollment and privilege anomalies. Limit: logs detect only what is collected, retained and meaningfully investigated.
MGM took systems offline and required staged restoration.ConfirmedA.8.13 Information backup; A.5.29 Information security during disruption; A.5.30 ICT readiness for business continuityMaintain immutable, isolated backups and recovery objectives proven by exercises. Limit: backups and plans cannot guarantee rapid restoration when identity, hypervisors or suppliers are also affected.
Initial access relied on deception and identity intelligence.ReportedA.5.10 Acceptable use; A.5.7 Threat intelligenceDefine safe verification/escalation behavior and use threat intelligence to tune controls to active TTPs. Limit: policy and intelligence inform action; they do not themselves block an attacker.
Containment, customer notification and recovery demanded coordinated decision-making.Confirmed incident response; analytical control mappingA.5.24–A.5.28 Information security incident managementMaintain rehearsed preparation, assessment, response, learning and evidence procedures. Limit: a plan improves speed and consistency but cannot remove legal, operational or evidential uncertainty.
Breach teardown

6. What Blueprint by Aegora’s free kit would have addressed

Blueprint by Aegora GRC is a free ISO/IEC 27001:2022 compliance kit of 109 documents, available by sign-up at aegoragrc.com. It is not a claim that paperwork alone would have prevented MGM’s incident. Its value is to turn controls into repeatable, reviewable operating practice.

  • Vishing resistance: our Information Security Awareness Deck and Awareness Quiz support role-specific rehearsal of impersonation, identity verification and escalation.
  • Help-desk verification and MFA-fatigue resistance: our Access Control Policy/Procedure (AEG-POL-014) and Password Management Policy/Procedure define controlled account recovery, MFA administration, access review and accountable exceptions.
  • Ransomware hygiene: our Antimalware Policy/Procedure, Patch Management Policy/Procedure and Logging and Monitoring Policy/Procedure support preventative hygiene and rapid detection.
  • Segmentation and architecture: our Network Security Policy/Procedure and Network Architecture Diagram make service boundaries, trust zones and exceptions visible to operators and auditors.
  • Recovery under pressure: our Backup & Retention Policy/Procedure, Business Continuity Plan and Business Impact Assessment Register tie recoverability to service priorities and tested recovery objectives.
  • Response and notification: our Incident Management Policy, Incident Response Plan and Incident Response Playbooks establish decision rights, evidence handling, communications and notification workflows.
  • Ongoing governance: the Risk Register and Statement of Applicability preserve the rationale, ownership and treatment status for risks—not just the existence of a policy.
Breach teardown

7. Key takeaways and lessons learned

  1. Make help desks verification-first. A password reset or MFA transfer is an identity-security event, not routine customer service. Require out-of-band proof and a documented escalation path for high-risk accounts.
  2. Use phishing-resistant MFA for privileged and recovery workflows. Push approvals and phone-based recovery remain vulnerable to social engineering; prefer FIDO2/WebAuthn or certificate-backed methods where feasible.
  3. Protect the identity control plane as critical infrastructure. Separate privileged accounts, minimize standing access, alert on device enrollment and recovery changes, and routinely test the identity-provider blast radius.
  4. Segment recovery, not only production. Immutable backups must be isolated from the identity, virtualization and management planes that an attacker may control.
  5. Exercise the business, not merely the SOC. Tabletop a ten-day loss of keys, reservations, payments, casino systems and communications; measure manual workarounds, decision authority and restoration order.
  6. Keep regulator and customer communication evidence-ready. Preserve timestamps, decisions, data-scope assumptions and notification approvals from the first hour. Precise disclosure is safer than confident speculation.
  7. Negotiate insurance with operational scenarios in hand. Test business-interruption definitions, waiting periods, forensic/legal sublimits and proof requirements before an incident; do not count an expected recovery as cash received.
Breach teardown

Sources

Primary sources used: MGM Resorts, 12 September 2023 statement; MGM Resorts Form 8-K, 5 October 2023; CISA/FBI #StopRansomware AA23-320A; DOJ ALPHV/BlackCat disruption announcement; DOJ Scattered Spider charging announcement; MGM Data Settlement; FTC MGM matter; Wired reporting on the attack; Reuters reporting on operational disruption.

Turn the lessons into documented practice

Start with the free ISO/IEC 27001 documentation kit. For implementation support, book a free one-hour consultation.

More articles