And now, a live Zoom meeting where @Okta's CISO Ray Bradbury talks about the breach.
"It's an embarrassment for myself and the entire Okta team." He's so incensed that he misuses the reflexive pronoun!
Taking pains to point out that Sitel is an external contractor. "It's not entirely our fault because we outsource dealing with our customers because we don't want to do it ourselves" isn't the strong statement it was workshopped as.
He's giving a timeline breakdown now. I think he's reading from the @Cloudflare blog post.
"Lapsus$, spelled with a dollar sign thusly to signify they're all about 'dat money.' You see, the love of a ransomware gang is very different from that of a square..."
I am informed that he is David Bradbury; Ray wrote a slightly different form of fiction. The management regrets the error.
https://twitter.com/97114171/status/1506647633430921221
"The access a support engineer has is limited." Well that's good, since you just went to some lengths to reassure us that this support engineer is *not your employee.*
"They cannot have godlike access. They cannot access our source code repositories. They cannot publicly shit our pants, which is reserved for our public communications in the wake of this crisis."
"This will only serve to strengthen our commitment to security." You're one password that gives access to everything within a company. If that *can* be strengthened then you've failed, folks.
And with that the Zoom is over, 11 minutes after it started and I want to hire @Okta to run my meetings. Usually we're still talking about our weekends by this point. Yes, I know it's Wednesday.
And with that we go live to Blameless Twitter who will explain why nothing that happened is anyone at Okta's fault, be they engineer, CISO, or corporate comms person.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
