Microsoft explains which cloud security problems are your problem

And reveals that for really bad problems, Microsoft will break Azure to fix it

Microsoft has issued guidelines about Azure security that spell out when a problem is your problem and when a problem is Microsoft's problem.

Two documents explain Redmond's approach to problem-solving. The first is called Shared Responsibilities for Cloud Computing (PDF) and explains how Microsoft divides responsibility for security.

The basic tenets of Redmond's approach are:

  • All on-premises IT is your problem
  • When you use Azure for infrastructure-as-as-service:
    • buildings, servers, networking hardware, and the hypervisor are Microsoft's problem
    • the operating system, network configuration, applications, identity, clients, and data are your problem
  • When you use platform-as-a-service:
    • Network controls become Microsoft's problem
    • the OS, applications, identity, clients and data are still your problem
  • When you use SaaS, everything is Microsoft's problem but data classification, end-point security and user management, all of which remain your problem

Microsoft's also released a new white paper titled Microsoft Azure Security Response in the Cloud (PDF) that explains how the company responds when its cloud has a problem.

The document reveals that Redmond uses the following five steps to patrol Azure's borders:

  • Customer reports via the Customer Support Portal that describe suspicious activity attributed to the Azure infrastructure (as opposed to activity occurring within the customer’s scope of responsibility)
  • Security vulnerabilities are reported to the Microsoft Security Response Center via MSRC works with partners and security researchers around the world to help prevent security incidents and to advance Microsoft product security.
  • Security Blue and Red teams activity. This strategy uses a highly skilled Red team of experts to attack potential weaknesses in Azure and the security response (Blue team) to uncover the Red team’s activity. Both Red and Blue team actions are treated as a means to verify that Azure security response efforts are managing security incidents. Security Red team and Blue team activities are operated under requirements of responsibility to help ensure the protection of Customer Data.
  • Detections of suspicious activities by internal monitoring and diagnostic systems within the Azure service. These alerts could come in the way of signature-based alarms such as antimalware, intrusion detection or via algorithms designed to profile expected activity and alert upon anomalies.
  • Escalations for operators of Azure Services. Microsoft employees are trained to identify and escalate potential security issues.

The rest of the document is a bit less revealing, although the section on mitigation actions does say that Redmond's effort to fix Azure “may result in a temporary outage.”

“Such decisions are not taken lightly,” the document says. “When such an aggressive mitigation occurs, the standard processes for notifying customers of outages and recovery timelines would apply.”

The rest of Redmond's response process is below, in a diagram and table from the document. ®

Microsoft's cloud incident response model

Wheels within wheels within wheels: the Microsoft security spin

Broader topics

Other stories you might like

  • Millions of people's info stolen from MGM Resorts dumped on Telegram for free
    Meanwhile, Twitter coughs up $150m after using account security contact details for advertising

    Miscreants have dumped on Telegram more than 142 million customer records stolen from MGM Resorts, exposing names, postal and email addresses, phone numbers, and dates of birth for any would-be identity thief.

    The vpnMentor research team stumbled upon the files, which totaled 8.7 GB of data, on the messaging platform earlier this week, and noted that they "assume at least 30 million people had some of their data leaked." MGM Resorts, a hotel and casino chain, did not respond to The Register's request for comment.

    The researchers reckon this information is linked to the theft of millions of guest records, which included the details of Twitter's Jack Dorsey and pop star Justin Bieber, from MGM Resorts in 2019 that was subsequently distributed via underground forums.

    Continue reading
  • DuckDuckGo tries to explain why its browsers won't block some Microsoft web trackers
    Meanwhile, Tails 5.0 users told to stop what they're doing over Firefox flaw

    DuckDuckGo promises privacy to users of its Android, iOS browsers, and macOS browsers – yet it allows certain data to flow from third-party websites to Microsoft-owned services.

    Security researcher Zach Edwards recently conducted an audit of DuckDuckGo's mobile browsers and found that, contrary to expectations, they do not block Meta's Workplace domain, for example, from sending information to Microsoft's Bing and LinkedIn domains.

    Specifically, DuckDuckGo's software didn't stop Microsoft's trackers on the Workplace page from blabbing information about the user to Bing and LinkedIn for tailored advertising purposes. Other trackers, such as Google's, are blocked.

    Continue reading
  • Despite 'key' partnership with AWS, Meta taps up Microsoft Azure for AI work
    Someone got Zuck'd

    Meta’s AI business unit set up shop in Microsoft Azure this week and announced a strategic partnership it says will advance PyTorch development on the public cloud.

    The deal [PDF] will see Mark Zuckerberg’s umbrella company deploy machine-learning workloads on thousands of Nvidia GPUs running in Azure. While a win for Microsoft, the partnership calls in to question just how strong Meta’s commitment to Amazon Web Services (AWS) really is.

    Back in those long-gone days of December, Meta named AWS as its “key long-term strategic cloud provider." As part of that, Meta promised that if it bought any companies that used AWS, it would continue to support their use of Amazon's cloud, rather than force them off into its own private datacenters. The pact also included a vow to expand Meta’s consumption of Amazon’s cloud-based compute, storage, database, and security services.

    Continue reading

Biting the hand that feeds IT © 1998–2022