Chromebooks and network motes to enforce security posture from the device to the cloud
summary
Claims a concrete rollout: Chromebooks with HSM and a locked-down Google Enterprise policy, disabling email on the secure device, stop phishing and credential theft while keeping dev work on a separate general-purpose laptop. Uses the Google access verification API, a custom proxy that issues short-lived certs, and a planned wire guard VPN implementation. Deployed ~100 devices, cut risky clicks from ~20% to ~2% in training, VPN integration proves hardest but overall approach works.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:35The Attacks
- 3:27Dedicated Secure Device
- 3:55Better security is possible
- 6:45Outline
- 6:55Scorecard
- 7:18Malware
- 9:51Phishing
- 11:28Credential Theft
- 12:28Secure Zone
- 16:30Put it all together
- 17:15Setup Step 1
- 18:06Setup Step 2
- 20:15Setup Step 3
- 24:08How does Two Laptops Work in Practice?
- 24:56Lessons
- 26:13The End
related talks
41mHow a Secure Enterprise Starts with the Web
40mSecurity, an Enterprise perspective
42mEnterprise Architecture Beyond the Perimeter
03mcybersecurity solutions
29mWebAuthn and security keys - unlocking the key to authentication
41mChrome Security Secret Sauce
06mSponsored Keynote: Why Developer Laptop Security is Key to Securing Your CI/CD Pip...
34mLinux for Chromebooks: Secure Development