Lessons Learned Implementing Meaningful Access Controls...
summary
Intercom spends nine months reducing internal access to customer data, cutting over 70% reduction in who can see critical data by baselining SSH certs (immediate ~20% drop), splitting admin UI into scoped admin controllers for non‑critical vs critical views, adding static analysis checks for new tools, three grant classes (all/critical/individual), self‑service break-glass requests logged to Slack, daily HR snapshots for provisioning, and an impersonation flow that limits views to the consenting user.
AI-written summary · about
chapters (17)
- 0:00Introduction and background
- 1:51Why access controls are delayed
- 5:24Incidents and policy planning
- 6:30Data classification standard
- 8:57Identifying key user groups
- 10:00Quantifying access with dashboards
- 11:04Engineering team access reduction
- 12:33Customer support tool access
- 14:19Separating critical and non-critical data
- 16:26Granular access grant categories
- 17:30Fail-open testing and rollout
- 18:56Break-glass self-service access
- 20:01Impersonation tool and consent
- 21:27Scoped data access for debugging
- 23:13Automated access provisioning
- 23:57Future customer-controlled consent
- 24:41Results and key takeaways
related talks
25mTracking Meaningful Security Product Metrics
23mAccess is the New Breach: Observability Must Start with Identity
22mThe Hidden Access Paths to Smaugs Cavern
23mScalable security: how to win friends and not burn...
21mSecuring a Security Company
26mCloud Security Lessons
57mKeep your nose out of it. Denying yourself access to production
14mThe Problem Isn’t Access, It’s Actions