Controlling Safe Browsing to Protect WebView
summary
Android WebView includes Google Safe Browsing by default on v66 and newer to block phishing, malware, and unwanted software. Apps can call startSafeBrowsing and handle a SafeBrowsingResponse with three possible actions (show an interstitial, navigate back to safety, or proceed), set per‑WebView enablement and a host whitelist, and should use compatibility helpers for behavior around API level 26. Chrome shows a red interstitial only when the WebView fills the root width and at least 70% of height, and SafetyNet Safe Browsing depends on Play Services 8.1+ (so it won’t work on devices without Play Services).
AI-written summary · about
chapters (6)
- 0:00Start
- 5:34Unsafe websites
- 14:07WebViewCompat#startSafeBrowsing
- 16:52WebViewClientCompat#onSafeBrowsingHit
- 22:37WebViewCompat#setSafeBrowsingWhitelist
- 23:35When to use disable/exclusion settings
related talks
34mOvercoming Insecurities in WebViews
42mOvercoming Unsecurities in WebViews
15mModern WebView best practices
39mAndroid and the WebView
40mSo, You Want To Use A WebView? [BAD AUDIO]
22mChrome and Android: Past, Present, Future
34mOvercoming JavaScript Unsecurities in WebViews
39mO-mg what's new in Android Security?
