Keep your nose out of it. Denying yourself access to production
summary
Production access becomes explicit, auditable and automated: keep a locked super user emergency account with hardware keys, push code and infra via GitHub Actions and bicep/terraform (not manual click‑ops), store secrets in Azure Key Vault, use identities and managed identities instead of passwords, require just‑in‑time elevation via Azure PIM and MFA, audit all JIT requests, and build safe operator scripts for repeated fixes. Real lessons: one accidental SQL update overwrote 365 articles; immutable ledgers in SQL Server 2022 catch tampering.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:30Why restrict access
- 3:38Real world examples
- 6:16Threats and consequences
- 8:40Principles of access
- 10:38Traditional governance
- 13:07Modern access issues
- 15:23Implementing zero trust
- 18:38Super user accounts
- 20:55Automated deployment
- 23:31Code review practices
- 27:06Moving beyond passwords
- 30:47Secrets management
- 33:56Log access control
- 35:39Separating configuration
- 37:11Secure remote access
- 41:04Just-in-time access
- 46:15Specialized tools
- 48:58Immutable ledgers
- 51:32Conclusion and Q&A
related talks
57mKeep your nose out of it. Denying yourself access to production
49mAzure DevOps security - Lessons learned
44mDeveloper Productivity Shouldn’t Breach Security
46mSecrets Management for the Modern Tech. Pro
25mSecuring Your DevOps Transformation
38mSecuring your CI/CD Pipeline
42mAzure DevOps security - Lessons learned
14mHow to Not-Mess-Up Production