You’ve seen the news. The ramifications from the #LastPass breach are manifold–and rumors abound in the news and in #cybersecurity social media forums. But what should we be focusing on, and what should we be learning from this event? 🤔
And #ICYMI, here’s what’s going on:
👉 LastPass recently published a series of breach disclosures illuminating an extended exfiltration, enumeration, and reconnaissance campaign within their environment.
👉 The attack campaign lasted for about 75 days (~2.5 months) and resulted in the exposure of an undisclosed number of customer passwords and sensitive data.
👉 The attacker leveraged valid credentials stolen from one of four senior #DevOps engineers to access a shared cloud-storage environment, which initially made it difficult for investigators to differentiate between threat actor activity and ongoing legitimate activity.
👉 Cloud service provider logging and alerting tools did not surface the attack within an actionable time frame—demonstrating how native tools are not sufficient security tooling. You need comprehensive anomaly detection and endpoint protection from a third party security software vendor to fill the gaps created by rapid innovation in the DevOps world.
🔥 Our hot take? Security practitioners have to take a holistic and proactive approach to security, and not rest on their laurels. They should deeply understand the shared security responsibility model between them and their cloud providers.
So let’s dig in. Bring your questions and your latest updates.