Ignite: Hackers Would Like You To Put In Long Hours
summary
Evidence links long shifts to higher error rates so treat tired ops raise hazard rate as a real threat model: small slips like misencrypted keys or an error oracle cascade into big failures. Concrete mitigations include split shifts and swapping weekend days to allow recovery and operational designs that tolerate staff absence, for example build switches to tolerate outages and collect tech-specific incident data so scheduling fixes actually reduce incidents rather than just sounding nice.
AI-written summary · about
chapters (15)
- 0:00Ryan Prior
- 0:29EVERY INDUSTRY HAS HAZARDS
- 0:59LONG HOURS INCREASE HAZARD RATE
- 1:29TECH LENDS ITSELF TO HAZARDS
- 1:44ARE TECH WORKERS UNIQUELY RELIABLE?
- 2:14THAN AIRLINE PILOTS?
- 2:29PUT TIRED OPS IN YOUR THREAT MODEL
- 2:44THREAT MITIGATION: ELIMINATE OVERWORK
- 2:59MULTIPLE MODELS OF MITIGATION
- 3:14MITIGATION: SPLIT SHIFTS THROUGHOUT THE DAY
- 3:44RESCHEDULING WORK TO TAKE NEEDED REST
- 3:59DESIGN YOUR TECH WITH SWITCHES TO TOLERATE OUTAGES
- 4:14OTHER INDUSTRIES STRUGGLE WITH THIS TOO
- 4:29REMEMBER THE MANY GOOD REASONS TO AVOID OVERWORK
- 4:44ALIGN SECURITY PRACTICES WITH YOUR VALUES
related talks
40mBurnout—The Greatest Threat to Your Organization’s Security
40mIncident Response – How to Give the Advantage to the Hackers!
41mMy Invisible Adversary: Burnout
21mhow to reconcile high-performance hosting and innovation projects with IT security
34mSecDevSecOpsSec
05mOut of the Basement...
44mFireside chat
39mLocknote: Conclusions and Key Takeaways from Day 2