Protect your game's integrity on Google Play
summary
Describes concrete defenses: use the Play License Verification Library to confirm APKs came from Google Play and the SafetyNet Device Attestation API to detect rooted devices, emulators, or spoofing; Rovio sees 40% fewer untrustworthy-device players after 30 days, and Supercell cuts unauthorized beta sessions from ~90% to under 50% by combining both. Notes a developer-preview automatic integrity protection for client-only games and a Bug Bounty with HackerOne (Google has paid over $250,000) for finding security flaws.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:45How Google Play licencing works
- 2:28How Safety Net attestation works
- 5:30Reduce beta leakage
- 7:38What's next for integrity?
- 8:49Strengthen game security
related talks
26mProtecting games and players by fighting abuse and piracy
39mAndroid App Security Fundamentals
28mProtecting Mobile Games Against Hackers, Crackers & Copycatters
20mKeeping Google Play Safe: Privacy, Security and SDKs
07mIntroducing Play Integrity API developer preview
38mAdvanced Techniques for Protecting Android Apps
47mDefending Your Users
06mKeeping Google Play Safe: Key privacy and security initiatives and resources