Aller au contenu principal
Life Security

Rechercher sur le site

Rechercher des pages et des sections.

Android overview

Dernière mise à jour:

Most of what keeps an Android phone safe happens before you install anything. The system isolates apps from each other, checks its own software at startup, and asks before an app reaches your camera or location. How well that works for you depends on one thing more than any setting: whether your phone still gets security updates.

This page explains how Android’s built-in protections work, what they don’t stop, and what changed in 2026 for people who install apps from outside the Play Store. After reading it you’ll be able to check whether your phone is still supported and know which few habits matter most.

We don’t cover privacy-focused alternative systems, tracking by Google’s own services, or specific phone recommendations. Each of those needs its own page.

What Android is, in plain terms

Android is an operating system made by Google and based on the Android Open Source Project, whose code anyone can read. Phones from many makers run versions of it. Google’s own requirements apply to what it calls certified Android devices, which is most phones sold with Play Store access.

That difference matters later. Google’s help pages say some new rules apply only to certified devices and exempt AOSP and non-certified devices (Android Help).

How Android protects you by default

Android’s documentation describes several layers. They work together, so one failing doesn’t give an attacker everything.

  • App sandbox. Android assigns a unique user ID to each app and runs it in its own process, and the system uses that to build a kernel-level sandbox (Android Open Source Project). By default an app can reach only a limited set of system resources and can’t read another app’s private data (AOSP).

  • Permissions. Protected features such as the camera, location, Bluetooth, SMS and network access need permissions that the app declares. Since Android 6.0 you allow or deny them while using the app. Details such as your phone number and hardware or network identifiers are off limits unless the app asks for them and is granted access (AOSP).

  • SELinux. This is mandatory access control that applies to every process, including those running as root (AOSP).

  • Verified boot. Each stage of startup verifies the next one, beginning with a hardware-protected root of trust, and it blocks the phone from rolling back to older versions. Since Android 7.0 it’s strictly enforced to prevent compromised devices from booting (AOSP).

  • Hardware-backed key storage. Android offers a keystore where key material stays in a secure environment (AOSP).

  • Google Play Protect. On your phone, it checks all apps regardless of source, including a daily lightweight scan. It asks you to remove harmful apps, disables or removes the worst ones, and checks apps installed from outside Google Play against known malicious samples and on-device machine learning. In extreme cases it blocks the install (Google for Developers).

  • Private space. A separate profile for sensitive apps, which you lock and unlock independently of the rest of the phone. Its apps start as fresh installs with no data copied from your main profile, and while it’s locked they’re hidden from recents, notifications, settings and other apps. There can be only one per device, and sharing with other apps works only while it’s unlocked. Its documentation ties it to Android 15 (AOSP). It separates apps on one phone. It isn’t a defense against someone who already controls your unlocked phone.

One limit worth knowing: Android requires every app to be signed, but accepts self-signed certificates and doesn’t check them against a certificate authority (AOSP). A valid signature tells you the app hasn’t been altered since the developer signed it. It doesn’t tell you who the developer is.

Updates decide how safe your phone stays

Software has flaws, and fixes only help if they reach your phone. Google publishes an Android Security Bulletin every month. The October 2026 bulletin, published on 5 October and updated on 8 October, lists 25 vulnerabilities, 7 critical and 18 high. The most severe could let a local attacker gain more privileges without any action by the user, and the bulletin doesn’t mention any being actively exploited. It covers Android 14 through 17 (AOSP).

Whether you receive those fixes depends on your phone’s maker. For Pixel phones, Google says the Pixel 8 and every model after it get seven years of OS and security updates counted from its launch on the US Google Store. The Pixel 6 and 7 series and the Pixel Fold get five years, and the Pixel 5a and earlier no longer get any (Google, as of October 2026). We verified only Pixel’s policy. Other makers publish their own, and some phones get far less.

A phone that no longer gets security updates keeps every flaw found after its last patch. Nothing else on this page fully makes up for that.

The 2026 change to installing apps

Google is adding developer verification for apps installed on certified devices. As of October 2026, here’s what Google’s own pages say.

  • Where and when. Enforcement began on 30 September 2026 for apps from participating stores in Brazil, Indonesia, Singapore and Thailand. A global rollout is planned for 2027 (Android Developers).
  • What happens. An app from an unverified developer can’t be installed or updated from those stores. You’ll see a notification and the app won’t install (Android Help).
  • It isn’t a ban. Unregistered apps can still be installed through an advanced flow or with ADB, a developer tool. The advanced flow is a one-time setup with security checks and a one-day wait, which Google says is meant to counter scammers who coach people through turning off protections. You can enable it for 7 days or indefinitely, and unverified apps still show a warning with an “Install Anyway” option (Android Developers).
  • Hobbyists. A free limited distribution account needs no ID and shares apps with up to 20 devices.

What it means for you depends on how you install apps. If you stay with Google Play, you’re unlikely to notice. If you install apps from other sources, expect extra steps, and expect them to reach more countries in 2027. Critics and supporters disagree about whether the trade-off is worth it. Google presents it as protection against scams and malware. We didn’t find an independent assessment of how well it works, so we don’t make a claim.

What Android’s protections don’t cover

  • Permissions you grant. The sandbox stops an app from reading another app’s data. It doesn’t stop an app you’ve given location access from using it.
  • Being talked into it. Google’s own explanation for the sideloading wait is scams where someone coaches you to disable protections. No setting helps if you do that yourself.
  • Old software. Once updates stop, the protections above rest on a system with known, unfixed flaws.
  • A scanner’s blind spots. Play Protect checks against known malicious samples and uses machine learning. No scanner catches everything.

Common myths

“Sideloading is being banned.” Google’s pages describe an advanced flow, ADB, and a hobbyist account. The change adds steps for apps from unverified developers. It doesn’t remove the ability.

“If an app is in the store, it’s safe.” Store checks reduce risk. Permissions and app behavior are still yours to judge.

“My phone is fine because it works.” A phone can run well and still be past its security update period.

What to do

These are ordered by how much they help for the least effort.

  1. Check your update status. Open Settings, then System, then Software update (menus vary by maker). Note the security patch level, then look up your maker’s support period for your model.
  2. If your phone no longer gets security updates, plan to replace it. Until then, keep it for low-risk use and avoid banking and sensitive accounts on it.
  3. Install apps from a store you trust, and deny permissions an app doesn’t need. A flashlight app has no reason to ask for your contacts. Privacy settings are under Settings, then Security and privacy on Android 13 and later, and under Privacy on Android 12 and earlier, though layouts vary by maker (Android Help).
  4. Keep Play Protect on. It adds a scan layer that works on apps from any source.
  5. Stop if someone is guiding you through changing security settings. That’s the pattern Google’s one-day wait is built to interrupt, and legitimate support never asks for it.
  6. If you sideload, learn the advanced flow before you need it. Enable it deliberately, and consider switching it off afterward.

This page is general information, not advice for a specific situation. Also see threat modeling to decide how much of this matters for you.

Sources

Foire aux questions