Lessons learned from the Microsoft Cloud breach

In early July, the news broke that threat actors in China used a Microsoft security flaw to execute highly targeted and sophisticated espionage against dozens of entities. Victims included the U.S. Commerce Secretary, several U.S. State Department officials and other organizations not yet publicly named. Officials and researchers alike are concerned that Microsoft products were again used to pull off an intelligence coup, such as during the SolarWinds incident.

In the wake of the breach, the Department of Homeland Security released a report stating that the Cyber Safety Review Board (CSRB) will conduct its next review on the malicious targeting of cloud computing environments. What lessons can be learned from this latest cyber incident? And how might companies protect themselves?

In the wake of the Microsoft breach

Immediately upon learning of the incident in July, the Department considered whether the Microsoft breach would be an appropriate subject of the Board’s next review. The CSRB plans to examine how the government, industry and cloud service providers (CSPs) should seek to strengthen identity management and authentication in the cloud.

The CSRB plans to specifically investigate the recent Microsoft Exchange Online intrusion. Furthermore, the Board will develop actionable recommendations to advance cybersecurity practices for both cloud computing customers and CSPs themselves.

After targeting top U.S. officials’ emails, the espionage operation triggered sharp criticism of Microsoft. The complaints were based on evidence the breach was only detectable if customers paid for a premium logging tier. Microsoft has since announced that customers will have access to expanded logging and storage capability at no additional cost.

Related: Cost of a Data Breach Report

Actors forge authentication tokens

As per a Microsoft Security report, the China-based threat actor, Storm-0558, was behind the attack. Beginning May 15, 2023, Storm-0558 used forged authentication tokens to access user emails from approximately 25 organizations, including government agencies and related consumer accounts, in the public cloud.

According to the security report, Storm-0558 acquired an inactive MSA consumer signing key and used it to forge authentication tokens for Azure AD enterprise and MSA consumers to access OWA and Outlook.com.

Once authenticated through a legitimate client flow leveraging the forged token, the attackers accessed the OWA API to retrieve a token for Exchange Online from the GetAccessTokenForResource API used by OWA.

Storm-0558 then obtained new access tokens by presenting one previously issued from this API due to a design flaw. Since then, Microsoft reported that it has patched the vulnerability.

How to defend against identity threats

As mentioned in the Homeland Security notice, ways to improve identity management and authentication in the cloud will be addressed at the next CSRB review. Could these approaches prevent incidents similar to the Microsoft breach? There’s a good chance they can.

Modern identity management solutions provide deep, AI-powered context for both consumer and workforce identity and access management (IAM). Advanced IAM software uses machine learning and AI to analyze key parameters, such as user, device, activity, environment and behavior.

The end result is a comprehensive, adjustable risk score to determine whether or not to grant access. This enables more accurate, contextual authentication for the workforce, partners, customers and devices.

Regulatory changes ahead

The recent Microsoft incident will only strengthen the White House’s drive to implement more stringent security practices by software manufacturers. CISA Director Jen Easterly has emphasized that the burden of maintaining software security needs to shift. The onus for security maintenance should move to software manufacturers with the funding, expertise and personnel to invest in software security.

What happened to Microsoft continues to reveal that a secure cloud requires the right tools and effort. While software manufacturers must step up, companies should also do their part by implementing solid identity access strategies.

Freelance Technology Writer