INCIDENT YK-17
Production is healthy. Nobody can log in.
A strategic customer is onboarding 34 employees. Every login now loops back to the sign-in screen. The launch call starts in 28 minutes.
This is not a cybersecurity puzzle. It is a short operations simulation: reduce uncertainty, identify the failing dependency, recover safely, and communicate clearly.
Estimated time: 3 minutes. No command line or hidden-source tricks required.
STAGE 1/4
What do you do next?
INCIDENT RESOLVED
You restored access without creating a second incident.
This is how Yishai Kaminsky works: establish scope, separate symptoms from causes, recover safely, and leave the system calmer than he found it.
IT Manager and Systems Engineer with 17+ years across enterprise support, Customer Success engineering, infrastructure, cybersecurity delivery, and practical AI automation.
Looking for IT operations, technical support leadership, Customer Success Engineering, implementation, TAM, or applied AI automation roles.
OPEN A PROFESSIONAL CHANNEL
Want Yishai to know who handled the incident?
You can leave as much or as little context as you like. Name and email are required only if you submit.
Good incident response is not about knowing every answer. It is about asking the next useful question.