Chrome Cuts 7 Billion Unwanted Android Notifications Daily with New Controls and On‑Device ML
What Happened — Chrome rolled out tighter permission controls, abuse‑detection, rate‑limits, and on‑device machine‑learning that together blocked more than 7 billion unwanted Android push notifications each day, many of which were used for phishing or ad‑spam.
Why It Matters for Compliance & Audit Readiness —
- Shows how documented access‑control policies (a SOC 2 Security requirement) can be enforced automatically at scale.
- Generates continuous, automated evidence of abuse‑detection that can be harvested for audit trails and control‑testing.
- Shrinks the attack surface for social‑engineering, reinforcing the effectiveness of security‑awareness training programs.
Who Is Affected — Mobile‑first users of Android, app developers, and enterprises that rely on Chrome for employee browsing.
Recommended Actions — Align your mobile permission policies with Chrome’s model, implement rate‑limiting and abuse‑detection on your own notification services, and refresh security‑awareness training to include notification‑based phishing scenarios. Source: TechRepublic
Technical Notes — Google leveraged on‑device ML to classify notification payloads, applied stricter permission checks, and enforced rate limits to curb abuse. No CVEs were disclosed. Source: TechRepublic