Uber
We said that last week's breach of Uber's internal systems looked bad and it was. In fact, the details that have since emerged are truly gruesome - but they do provide some great cautionary lessons.
What happened
Uber has been reticent about exactly what happened but it's clear that the attacker accessed much, if not most, of Uber's critical IT infrastructure including its Amazon Web Services, Slack and G Suite accounts, its security dashboards, and its bug bounty platform. Uber says a contractor's account was compromised, probably after one of their devices was infected with malicious software that obtained their credentials. The attacker then purchased the stolen password on the dark web and made repeated attempts to log in to the contractor's account. Each attempt generated a two-factor authentication request and it appears the contractor eventually approved one, probably just to stop the stream of prompts.
The lessons
The fact that Uber went on a hiring spree following the incident might raise questions about the security resources it had in place prior to the attack. After all, this isn't its first major breach (indeed it's accused of trying to cover up a huge incident in 2016). But the key lesson centres on multi-factor authentication (MFA). We are firm believers in the importance of implementing this, while recognising that it's not a magic bullet. Indeed, as it has become more widely used, attackers have become increasingly adept at defeating it. The bottom line is that any form of MFA is better than nothing, but only one specific implementation is resistant to attack. KnowBe4 has a detailed article on the subject and maintains a list of "phishing-resistant" solutions.
Epidemic
We would urge organisations to take this threat seriously. Just this week, news emerged of multiple organisations falling victim to data breaches. They include American Airlines, the makers of Grand Theft Auto, and the financial technology company, Revolut. The group claiming responsibility for the attack on Uber has been linked to similar incidents at Microsoft, Samsung, Cisco and Okta. Above all, it's absolutely essential that everyone understands the risks attached to poor password security.