Introduction to counter-abuse technology at Google
summary
Google describes concrete systems: Pixel 6/6 Pro factory images are logged so anyone can verify firmware hashes via Binary Transparency, and a second Binary Transparency rollout signs and logs on-device anti-abuse model updates so devices check provenance before applying them. Messages by Google uses end-to-end encryption for RCS while still applying on-device protections for phishing and scams, and the device skips unverified models and waits for a verifiable update, with plans for multiple logs and external witnesses.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:49What Do Counter Abuse Teams at Google Do
- 3:05End-to-End Encryption
- 4:38Pixel 6 and Pixel 6 Pro
- 5:11Certificate Transparency
- 7:26Google Binary Transparency
- 8:38On-Device Protections
related talks
13mKeynote
40mSecurity, an Enterprise perspective
26mProtecting games and players by fighting abuse and piracy
06mKeeping Google Play Safe: Key privacy and security initiatives and resources
10mProtect your game's integrity on Google Play
39mAndroid App Security Fundamentals
20mKeeping Google Play Safe: Privacy, Security and SDKs
39mO-mg what's new in Android Security?
