Azure
An implementation error in Microsoft's protective mechanisms worsened the effect of a cyberattack, sparking a worldwide incident.
New details of global mega-outage revealed, with Microsoft blaming disastrous "usage spike" on an implementation error in its own response to a cyberattack.
Tenable research "revealed an attack surface most users of Azure service were probably not accounting for..."
"A requirement to bring unmanaged and unsupported ICS devices under proper governance and control..."
Upstream utility disturbance triggers brief bout of sweating with "a small amount of storage nodes" needing to be recovered manually in the wake of the Azure incident,
"High profitability, a concentrated market structure and limited levels of switching are likely indicators that cloud providers are not facing sufficiently strong competitive constraints."
Following a major security breach involving US federal agencies, Microsoft refuses to provide details on the incident
"The risk is mainly with multi-tenant applications where this misconfiguration could result [in] account and privilege escalation" -- here's what you need to do.
