Has Microsoft compromised security one too many times?

Has Microsoft compromised security one too many times?

As Microsoft revealed tidbits of its ‌post-mortem investigation into a Chinese attack against US government agencies via Microsoft, two details stand out: the company violated its own policy and did not store security keys within a Hardware Security Module (HSM) — and the keys were successfully used by attackers even though they had expired years earlier.

This is simply the latest example ⁣of Microsoft quietly cutting corners on cybersecurity and then only telling anyone when it ⁤gets caught.

Tenable CEO Amit Yoran wrote a powerful post on LinkedIn last week and described “a repeated​ pattern of negligent cybersecurity practices…. Microsoft’s lack ⁤of transparency applies to breaches, irresponsible security practices and to vulnerabilities, all of which expose their customers ​to risks they are deliberately kept in the dark about.”

He then referenced his own company’s ‌dealings with Microsoft:

“In March 2023, a member of Tenable’s Research team was investigating‌ Microsoft’s Azure platform and‍ related services.⁢ The researcher discovered an⁣ issue (detailed here) which would enable an unauthenticated attacker ‌to access cross-tenant applications and ‌sensitive data, such as authentication secrets.⁣ To give you an idea of how bad this is, our team very quickly discovered authentication secrets to a bank.⁢ They were so concerned about the seriousness and the ethics of the issue that we immediately notified Microsoft. Did Microsoft quickly fix the issue that could effectively lead to the breach of multiple customers’ networks and services? Of course not. They took more than 90 days to implement a partial fix – and ​only ⁣for‌ new applications loaded in the service. That means ‍that as⁢ of today, the bank I ‍referenced above is still vulnerable, more than 120 days⁣ since we reported the issue, as are all of the other organizations that had launched the service prior to the fix.”

The Tenable example could be dismissed‌ as an isolated incident if ‍I hadn’t recently heard from multiple security researchers about other security holes they discovered ⁣and their talks with Microsoft‌ about the issues. This is a troubling ​pattern.

“Microsoft plays fast and loose when it comes to transparency and their responsibilities in cybersecurity. Their pace ⁢for remediation is not world class,” Yoran ⁢said in an⁤ interview. “Once they⁢ patch, they have a history of not disclosing that‍ there ever was a ​hole. They have a moral responsibility to disclose.”

Back in the 1990s, a common and true adage among enterprise IT execs was the clichéd, “You can never get fired for hiring IBM.” Today, that statement is still true, if you  swap out‍ Microsoft for IBM.

Here’s why that is such a problem. It seems ‍all but certain that the cybersecurity corner-cuttings that happened in the China attack were done by some mid-level manager. That manager was confident that‍ opting for a slight cost reduction (along with a small boost in…

2023-08-07 21:00:03
Post from⁣ www.computerworld.com rnrn

Exit mobile version