Engineering, market analysis, and product writing from the team building backup and disaster recovery for the identity layer. Substance over slogans.
A companion to the Okta Admin Console for the minutes when you're on call and nowhere near a laptop. Suspend a user, clear sessions, activate a network zone, and read your recovery posture from your phone, with two independent gates on every change that the server enforces rather than the app. Running a full restore stays on the desktop on purpose, and here is the reasoning behind that line.
Voice phishing used to mean a convincing stranger on the phone. Now the caller can look and sound like the executive you report to, built from footage that executive published themselves. One engineering firm lost twenty five million dollars to a video call where everyone but the victim was a deepfake. The defenses that actually work are procedural, and so is the question you have to answer afterward.
Vishing is phishing that arrives as a phone call. Okta has been warning customers about a campaign that uses one to walk employees through a fake passkey enrollment while the attacker quietly registers their own. Most of the guidance being written about it is prevention guidance. The harder question lands after you have kicked the attacker out.
Every layer of your stack has point-in-time recovery except the one that gates access to all of it. Customers have asked identity vendors for config backup and restore for years and gotten silence. And AI will not close the gap, because recovery is a state problem, not an intelligence problem.
Okta runs the identity platform, and they run it well. Your configuration inside it is still yours. That split is not a gap in the product, it is how every serious cloud platform works, and it is the part I spent eight years watching people discover at the worst possible moment.
OpenAI's pre-release models escaped a testing sandbox, went hunting for credentials, and pulled data from Hugging Face's production database in thousands of automated actions. The entry point was a software bug. The pivot was credentials. Here is why machine-speed attacks change the math on identity recovery.
Butterfly now backs up, restores, and diffs Microsoft Entra ID and Google Workspace with the same preview-first discipline we ship for Okta. Five identity providers, one recovery contract. Here is exactly what is live, and what still stays Okta-first.
Okta recovery is where Butterfly started. The roadmap is broader: bringing the same backup, dry-run restore, and drift detection to Google Workspace, Microsoft Entra ID, and Workato. Here is what is live today, and where we are headed, stated plainly.
Teams are already using AI for identity admin workflows. That's smart, and faster, but one bad command can change an entire login path in seconds. Butterfly Security gives every admin a restore plan, not just a shiny UI.
Anthropic disabled Claude Fable 5 and Mythos 5 worldwide to comply with a US Commerce Department directive. 24 hours from launch to lights-out. The story isn't about AI safety. It's about how fast identity-mediated services can disappear.
Butterfly Security is generally available. Point-in-time backups, dry-run restore previews, signed audit evidence, and warm-standby continuity for Okta, Okta Workflows, and Auth0.
Your identity provider guarantees uptime, not your configurations. Understanding the shared responsibility model for Okta and Auth0 is the first step to real disaster recovery.
New posts ship as the recovery layer evolves. Check back, or follow Mick on LinkedIn for the next one.