University of Pennsylvania SSO Breach Exposes 1.2 Million Records

University of Pennsylvania SSO Breach Exposes 1.2 Million Records

First seen 29 Jul 2026, 17:15 UTC BleepingcomputerFeeds.Feedburner 74% similarity 71.0

Article Content

Browse articles
ThreatCluster

In 2025, the University of Pennsylvania suffered a significant data breach due to a compromised single sign-on (SSO) account. Attackers accessed the PennKey SSO, infiltrating internal systems including VPN, Salesforce, Qlik, SAP, and SharePoint. This breach affected 1.2 million individuals, highlighting the risks associated with SSO authentication. While SSO offers benefits like reduced password sprawl, its security relies on robust protection measures. The National Institute of Standards and Technology (NIST) recommends strong password policies, including a minimum of 15 characters for single-factor authentication and 8 characters for multi-factor authentication (MFA). Additionally, MFA should be enforced consistently across all users and access scenarios, with a shift towards more secure methods like FIDO2 security keys. Organizations must also secure identity provider administrator accounts and review permissions to mitigate risks.

Key Points: • The University of Pennsylvania breach compromised 1.2 million records via SSO. • Attackers exploited a PennKey SSO account to access multiple internal systems. • NIST recommends strong password policies and consistent MFA enforcement for SSO security.

ThreatCluster AI How this analysis works

Timeline

2025-01-01
University of Pennsylvania breach occurred
Attackers compromised a PennKey SSO account, leading to unauthorized access to critical systems.
BleepingComputer
2025-01-01
Data theft confirmed
The breach resulted in the theft of personal data belonging to 1.2 million individuals.
BleepingComputer
2026-07-28
Bleeping Computer article published
Bleeping Computer reported on the breach and its implications for SSO security.
BleepingComputer
2026-07-29
Feedburner article published
Feedburner summarized the breach, emphasizing the need for strong SSO security measures.
Feeds.Feedburner

Community

Browse all →