This tracker records what each major phone brand says, on its own policy pages, about how long its phones receive security updates, so that security and identity teams can set device eligibility rules from published vendor wording rather than from retail claims or memory. A phone that no longer receives security updates still holds authenticator apps, passkeys, corporate email tokens, VPN profiles and messaging sessions. Every one of those is a credential or a session that an attacker can reuse if the operating system underneath it carries known, unpatched flaws. Knowing when support ends is therefore an access control question as much as a procurement one.
Status as of 20 Nov 2026. Brands are listed in alphabetical order. This page does not rank brands or recommend one over another. Where we could not retrieve a vendor's own policy page during this update, the brand is shown as not confirmed rather than filled in from secondary sources. Pixel model details are covered in depth on our Android and Pixel Security Update Support page, and this tracker links to it rather than repeating it.
Key takeaways
- Support periods are vendor statements, not guarantees in every case. Read the exact wording: "at least", "up to" and "from first availability" each change what you can rely on.
- Google states seven years of updates for Pixel 8 and later and five years for the Pixel 6 and 7 series and Pixel Fold, counted from when each device first became available on the Google Store in the US.
- Samsung states it is extending security update support for Galaxy devices by up to seven years, with timing that may vary by market, network provider and model, and it sorts devices into monthly and quarterly update lists.
- Apple's security releases page does not state a fixed support period or end date for iPhones. It shows which version branches received updates, not which will in future.
- Fairphone, Motorola, OnePlus and Xiaomi are marked not confirmed in this edition because their policy pages could not be retrieved. Check them directly before relying on any figure.
- Base fleet rules on the observed security patch level and the vendor's published lists, and re-check the tracker on a fixed schedule.
How to read a phone support statement
Phone makers describe support in three different ways, and the differences matter when you turn a statement into a policy.
Start point
A period counted "from when the device first became available" starts at launch, not at the date you bought the phone. A handset bought two years after launch has two fewer years of support left than the headline figure suggests. Google's Pixel wording uses this launch-based start point, tied to first availability on the Google Store in the US. Where a vendor does not say what the start point is, treat the period as uncertain.
Floor or ceiling
"At least" sets a floor. "Up to" sets a ceiling. Samsung's January 2024 statement says "up to 7 years", which describes the maximum some models may get, not a minimum every model will get. A policy that assumes every Galaxy device receives seven years would overstate the protection on models in shorter tiers.
Cadence
Some vendors publish how often updates arrive, for example monthly or quarterly, as well as for how long. Cadence affects exposure: a device on a quarterly cycle can carry a publicly disclosed flaw for longer between fixes than a device on a monthly cycle, even while both are inside their support period.
Operating system versus security updates
Vendors sometimes give different periods for major operating system upgrades and for security patches. For access decisions, the security patch period is the one that matters. A phone can be on an older major version and still be patched, or on a recent version and no longer patched.
Support period table
The table below records each brand's own published position as retrieved for this edition. It lists only what the vendor page says. Brands appear alphabetically.
| Brand | Published support statement | Start point stated | Source checked |
|---|---|---|---|
| Apple | No fixed support period or end date stated on the security releases page. The page lists updates across several iOS branches at once. | Not stated | Apple security releases |
| Fairphone | Not confirmed. The vendor page could not be retrieved for this edition. | Not confirmed | Not retrieved |
| Google (Pixel) | Seven years for Pixel 8 and later; five years for Pixel Fold and the Pixel 6 and 7 series. Pixel 5a and earlier no longer receive Android version or security updates. | First availability on the Google Store in the US | Pixel update support |
| Motorola | Not confirmed. The vendor page could not be retrieved for this edition. | Not confirmed | Not retrieved |
| OnePlus | Not confirmed. The vendor page could not be retrieved for this edition. | Not confirmed | Not retrieved |
| Samsung | Security update support for Galaxy devices extended by up to seven years (stated January 2024). Monthly and quarterly model lists published. Timing may vary by market, network provider and model. | Not stated as a fixed start point on the page checked | Samsung Mobile Security update scope |
| Xiaomi | Not confirmed. The vendor page was not retrieved for this edition. | Not confirmed | Not retrieved |
Apple
Apple's security releases page is the vendor's own record of security updates. It does not state a fixed number of years of support, and it does not publish an end date for any iPhone model. Apple says it "doesn't disclose, discuss, or confirm security issues until an investigation has occurred", and that keeping software up to date "is one of the most important things you can do to maintain your Apple product's security."
The release table shows that Apple ships updates on several version branches in parallel. In the edition we checked, entries dated 9 Nov 2026 included iOS 27.2.1, iOS 26.7.3 and iOS 18.7.12, and older branches such as iOS 16.7.16 and iOS 15.8.8 also appear in the list. Each entry names the devices it covers. That tells you which devices received a fix in the listed period. It does not tell you which will receive the next one.
For policy, this means an Apple device's support status has to be judged from evidence: is the device on a version branch that appears in recent release entries, and does that entry name the device? When a model stops appearing in new entries, treat it as out of support for access decisions, even though no end date was announced.
Fairphone
Not confirmed. We attempted to retrieve Fairphone's own support statement for this edition and could not. We have not filled the gap from press coverage or retail listings. Teams with Fairphone devices in their fleet should read the vendor's current software support page directly, record the exact wording and start point, and apply the same tests described above: start point, floor or ceiling, and cadence. This row will be completed when the vendor page can be checked.
Google Pixel
Google publishes Pixel support periods on its Pixel phone help centre. Pixel 8 and later "will get updates for seven years starting from when the device first became available". Pixel Fold and the Pixel 6 and 7 series "will get updates for five years starting from when the device first became available". The page lists the seven-year group as the Pixel 8, 8 Pro and 8a, the Pixel 9 family and 9a, the Pixel 10 family and 10a, and the Pixel 11 family including the 11 Pro Fold. The five-year group is the Pixel 6, 6 Pro, 6a, the Pixel 7, 7 Pro, 7a and the Pixel Fold. Pixel 5a and earlier no longer receive Android version or security updates.
The page gives support lengths, not calendar end dates. To work out a specific end date, Google points to a linked article listing when each device first became available, and you add the support period to that date. The model-by-model working, Android Security Bulletins and patch level checks are on our Android and Pixel Security Update Support page.
Motorola
Not confirmed. Motorola's software security update page could not be retrieved for this edition, so no support period is recorded here. Motorola devices run Android, so the patch level checks on the Android and Pixel page apply to them, but the support length itself must come from Motorola. Teams should record the vendor's current wording, including whether it is stated per model, per tier or per region.
OnePlus
Not confirmed. We could not retrieve a OnePlus security update policy page for this edition. No figure is given here, and none has been taken from secondary sources. As with the other Android brands, the device's reported security patch level remains the most reliable evidence of whether it is currently patched, and the vendor's own policy is the only acceptable source for how long that will continue.
Samsung
Samsung's mobile security site states that "Samsung releases monthly, quarterly and biannual firmware security updates on selected Samsung devices". It publishes model lists headed "Current Models for Monthly Security Updates" and "Current Models for Quarterly Security Updates", and a separate list of wearable models on quarterly updates. The page we checked did not include a separate biannual model list.
On duration, Samsung states it is "extending our security update support for Samsung Galaxy devices by up to 7 years" as of January 2024. The page does not give a minimum number of years, and it says timing "may vary by market, network provider and/or model." Read together, this means the seven-year figure is a ceiling. The practical evidence for a given device is whether its model appears in a current list, and which list.
For fleet policy, a model's movement from the monthly list to the quarterly list, or off the lists entirely, is the signal to act on. Recording the list a model sits in at each review gives you a trail of when its support changed.
Xiaomi
Not confirmed. Xiaomi's own security update page was not retrieved for this edition. No period is recorded. Xiaomi devices should be held to the same evidence test as every other brand: a published vendor statement for duration, and the device's own patch level for current status.
Turning support periods into access policy
A support period on its own does not protect anything. It becomes a control when it feeds device eligibility rules in mobile device management and in conditional access.
Set an eligibility rule per brand
For each brand in your fleet, write down the evidence you will accept: a published end date, a model list, or a version branch appearing in recent releases. Where a vendor publishes no end date, as with Apple on the page we checked, define the observable test in advance so that an unsupported device is caught by rule rather than by argument.
Check patch level, not model name
A supported model that the user never updates is as exposed as an unsupported one. Device compliance should test the reported security patch level or operating system build against a maximum age, and block or limit access when it falls behind. Our Mobile Device Management Security Guide covers how to enforce this.
Plan for the end before it arrives
Add the end of support date, or the review trigger for brands without one, to the asset record at enrolment. Notify users and budget holders well before the date so that replacement happens before access is cut, not after.
Protect the credentials on the device
When a phone goes out of support, the risk is to the identities it holds. Authenticator seeds, passkeys, refresh tokens for email and collaboration apps, and certificates for Wi-Fi or VPN should all be revoked or moved when the device is retired. Removing the device from management without revoking these leaves live credentials on unpatched hardware.
Common failure patterns
- Reading "up to seven years" as "seven years" and approving every model in a brand for the full period.
- Counting support from the purchase date rather than the vendor's stated start point, which is often first availability.
- Allowing a device because its model is supported while its patch level is months old.
- Relying on retail listings or press coverage for a brand whose own policy page has not been checked.
- Retiring a phone from management without revoking authenticator, passkey and token enrolments on it.
- Reviewing the tracker once at procurement and never again, so model list changes go unnoticed.
Practitioner checklist
- List every phone brand and model in the fleet, including bring-your-own devices that reach corporate data.
- For each brand, record the vendor's exact support wording, its start point and whether it is a floor or a ceiling, with the URL and date checked.
- Mark any brand you cannot source from the vendor as not confirmed, and do not set an end date for it from secondary sources.
- Set a maximum security patch age in device compliance and tie it to conditional access.
- Define the observable test for brands that publish no end date.
- Record end of support or review dates in the asset register at enrolment.
- Revoke authenticator, passkey, certificate and token enrolments when a device is retired or falls out of support.
- Re-check vendor pages at least quarterly and update the status line.
Standards and references
- Apple: Apple security releases
- Google: Learn when you'll get software updates on Google Pixel phones
- Samsung Mobile Security: security update scope and model lists
- NIST: SP 800-124 Rev. 2, Guidelines for Managing the Security of Mobile Devices in the Enterprise
- NIST: SP 800-40 Rev. 4 Guide to Enterprise Patch Management Planning
- legislation.gov.uk: PSTI Security Requirements Regulations 2023, Schedule 1
- EUR-Lex: Regulation (EU) 2024/2847 (Cyber Resilience Act)
Related NHI Mgmt Group resources: Android and Pixel Security Update Support · Mobile Device Management Security Guide · Android Enterprise Security Guide · Operating System End of Life and Extended Support Guide