Historical disclosure revision 1
Disclosures and evidence
Revision 1 of 2 · Evidence cutoff Sep 13, 2023, 12:00 AM UTC
0 prior statements preserved · 5 statements added. Attributed source statements retain the source’s qualifications.
What the company disclosed
MGM Resorts International stated: ““MGM Resorts recently identified a cybersecurity issue affecting certain of the Company’s systems. Promptly after detecting the issue, we began an investigation with assistance from leading external cybersecurity experts. We also notified law enforcement and are taking steps to protect our systems and data, including shutting down certain systems. Our investigation is ongoing, and we are working diligently to resolve the matter. The Company will continue to implement measures to secure its business operations and take additional steps as appropriate.””
Response
MGM Resorts International stated: ““MGM Resorts recently identified a cybersecurity issue affecting certain of the Company’s systems. Promptly after detecting the issue, we began an investigation with assistance from leading external cybersecurity experts. We also notified law enforcement and are taking steps to protect our systems and data, including shutting down certain systems. Our investigation is ongoing, and we are working diligently to resolve the matter. The Company will continue to implement measures to secure its business operations and take additional steps as appropriate.””
Disclosure timeline
MGM Resorts International stated: “Las Vegas, September 12, 2023 – MGM Resorts International (the “Company” or “MGM Resorts”) today issued the following statement:”
Disclosure evolution
MGM Resorts International stated: “On September 12, 2023, MGM Resorts International (the “Company”) issued a press release regarding a cybersecurity issue involving the Company.”
MGM Resorts International stated: “| 99.1 | | Press Release issued by the Company, dated September 12, 2023.”
Disclosure sources and provenance
- U.S. Securities and Exchange Commission Filed September 13, 2023Report/event date: September 12, 2023Document form: 8-K · Item 7.01 and 9.01Imported retained source · Retrieved Oct 7, 2026, 12:45 PM UTC · Retained Oct 7, 2026, 1:07 PM UTC
- Retained source bytes were imported locally; a byte hash does not prove source authenticity.
- Original historical acquisition time unknown; current helper capture time documented.
- No independent byte comparison with a 2023 snapshot; hash is byte identity, not cryptographic source authenticity.
- U.S. Securities and Exchange Commission Filed September 13, 2023Statement/document date: September 12, 2023Document form: EX-99.1 to 8-K · Item 7.01Imported retained source · Retrieved Oct 7, 2026, 12:45 PM UTC · Retained Oct 7, 2026, 1:07 PM UTC
- Retained source bytes were imported locally; a byte hash does not prove source authenticity.
- Original historical acquisition time unknown; current helper capture time documented.
- No independent byte comparison with a 2023 snapshot; hash is byte identity, not cryptographic source authenticity.
Evidence limitations
- Issuer disclosures establish what was reported, not independent incident verification.