Hacking Google - Lessons learned running and growing an internal red team
summary
An internal red team recounts using malicious USB plasma-globe implants to gain initial access to engineers working on Google Glass, then escalating over months to request an unreleased prototype before being caught during pickup; that failed endgame still yields tangible outcomes: shared real-time activity logs with detection teams, formal Rules of Engagement and timestamped activity locks, and an open‑source Python daemon for USB keystroke injection protection that hardens defenses beyond the company.
AI-written summary · about
chapters (14)
- 0:00Google Glass attack with plasma globes
- 5:43Building an internal red team
- 8:13What this talk will cover today
- 9:19Red team purpose and scope
- 12:52Red teams improve detection
- 16:49Red teaming challenges
- 18:54Trust via realistic simulations
- 19:18Storytelling in security reports
- 23:34Collaboration for red team success
- 27:20Key partnerships for red teams
- 30:29Rules of engagement and safety
- 32:16Healthy red team culture
- 35:43Preventing red team burnout
- 37:28Conclusion
related talks
54mHacked in hours: Red team assessments unveiling vulnerabilities
44mLive Hacking Cloud Architectures
34mHijacking Google’s CI/CD Through Prompt Injection:The New Era of AI-Based Exploits
32mWhat We Can Learn from Google’s Fight with Phishing
30mInside the Mind of a Hacker: How a Light Bulb Almost Stopped Christmas
30mGoogle Give Me Vulnz
40mThe Mechanisms That Enable Misuse and What We Can Do About It
39mBye-Bye DIY: Frictionless Security Operations with Google