Swiss BIT Breach: What Happened to the Federal IT Agency's SharePoint Servers

An investigation into how threat actors exploited on-premises SharePoint patch latency to compromise 200 Swiss federal government IT accounts.

Swiss BIT Breach: What Happened to the Federal IT Agency's SharePoint Servers
Photo by Oleg Podlesnykh / Unsplash
📌
Security Roundup Series: Week of August 10, 20265 min read deep dive

Switzerland's Federal Office of Information Technology (BIT)—the primary IT backbone for the Swiss federal government—confirmed that attackers exploited unpatched on-premises SharePoint vulnerabilities to compromise approximately 200 user and technical service accounts.

🏛️
Incident Overview: Target: Federal Office of Information Technology, Systems and Telecommunication (BIT), Switzerland Compromised Assets: ~200 federal government accounts (user & technical service credentials) Vector: Exploitation of on-premises Microsoft SharePoint vulnerabilities during the post-disclosure patch window Investigating Bodies: Swiss Federal Office for Cybersecurity (BACS), BIT, and Microsoft Incident Response

What Happened

On July 28, 2026, BIT automated monitoring detected unusual activity across its internal SharePoint infrastructure. By July 31, forensic analysis confirmed that credentials for roughly 200 accounts had been compromised.

BIT immediately severed internet access to the affected SharePoint environment, applied security updates to close the exploited vectors, and initiated mandatory credential resets across all affected accounts.

Who's Affected

The compromised accounts belonged to BIT personnel and internal service roles responsible for federal IT operations. Swiss authorities stated that the affected server instance was not classified for confidential or top-secret federal data, and initial investigations showed no evidence of secondary data exfiltration beyond the account credentials themselves.

Technical Root Cause: The SharePoint Patch Latency Window

Attackers capitalized on the window between Microsoft's public security patch release and BIT's internal patch deployment cycle. On-premises SharePoint vulnerabilities (particularly deserialization and remote code execution bugs) have repeatedly been weaponized by threat actors within days of public advisory releases.

💡
Why Technical Service Accounts Matter: Service accounts often hold broad cross-system API access and rarely have MFA enabled. Compromising a single SharePoint service account can provide an attacker with pivot credentials into linked Active Directory environments.

Lessons & Actionable Guidance

Enterprise SharePoint Defense Checklist: Compress Patch SLA: Treat on-premises SharePoint security updates as emergency releases rather than standard monthly maintenance. Rotate IIS Machine Keys: Whenever an on-prem SharePoint server is exposed during an exploit window, immediately rotate IIS machine keys to invalidate potential deserialization persistence. Service Account Auditing: Enforce strict conditional access, restrict service account login types, and monitor for anomalous token generation.