Tool AT-W12REV. 2026-A
End-of-support check: do your programs and devices still get updates?
Windows Server 2016 gets security updates only until 12 January 2027, and Office 2021 has had none since 13 October 2026. Whether a product is still supported is decided solely by the manufacturer's date. Put together what you have running: the check sorts the list by urgency and gives each product this date, the days remaining and the next step.
- over 120 products and versions
- Data stays in your browser
- Dates checked 13.11.2026
01 / INVENTORY
Check your list
For a single Windows PC it is quicker with the Windows 10 check: it detects the version itself and tells you whether the computer can run Windows 11.
Inventory · security updates per product
The check matches your list to the dates the manufacturers publish. It cannot see your devices: which version is really running is shown on the device itself. Dates checked on 13 November 2026.
Runs in your browser. Nothing is sent or stored.
02 / BACKGROUND
What “end of support” means
A program does not stop working on the day support ends. Windows still starts, and Office opens your files as it did the day before. What goes away are the security updates: vulnerabilities that become known afterwards are no longer fixed by the manufacturer. Microsoft releases its updates on the second Tuesday of each month, so almost every end date falls on a Patch Tuesday.
Mainstream, Extended, ESU
For Windows Server, SQL Server, Exchange and the boxed versions of Office, Microsoft applies a fixed period. First come at least five years of mainstream support with bug fixes and security updates. For many products, extended support follows: security updates only, at no extra charge. For some products Microsoft then sells an extension, Extended Security Updates (ESU), each for one year. For Windows Server 2016 it runs until 8 January 2030, according to Microsoft.
As “Updates until” the check always shows the end of the free part, that is, of extended support. An ESU is shown alongside as a possible way out, because it costs money and only buys time.
Ongoing maintenance instead of a date
Microsoft 365, Exchange Server SE and Windows 11 have no fixed end. You are supported as long as you pay for the licence and install the updates. With Windows 11 you can see this in the versions: each has its own deadline, 24 months for Home and Pro, 36 for Enterprise and Education. Only the yearly feature update pushes the end back. A Windows 11 PC on which Windows Update has been stuck for months may therefore already be red.
Apple, Android, PHP and FRITZ!Box
Apple does not give end dates. In past practice the current version gets all security updates, and for macOS the two previous versions get some of them. Apple itself says that older versions do not receive fixes for all known vulnerabilities. For Apple, the check therefore shows no date but the state of the update list. For Pixel phones from the Pixel 8 onwards, Google promises seven years, counted from the start of sales in the USA. Samsung publishes only which models currently receive monthly or quarterly updates. The PHP project gives a fixed end for each version at the turn of the year, and FRITZ! (formerly AVM) lists a date for each model until which updates will appear at the least.
03 / DATES
The key dates
The same data as in the check, as a table for reference. “New features until” is the end of mainstream support, “Security updates until” the last day with free fixes. As of 13 November 2026, each date checked against the manufacturer's page.
| Product | New features until | Security updates until | Extension, note |
|---|---|---|---|
| Windows 7 | — | 14.01.2020 | |
| Windows 8.1 | — | 10.01.2023 | |
| Windows 10 (Home, Pro) without ESU | — | 14.10.2025 | with ESU, home use until 12.10.2027, in business at most until 10.10.2028 |
| Windows 10 with ESU, home use | — | 12.10.2027 | Only as long as you sign in with your Microsoft account at least every 60 days. |
| Windows 10 with ESU, business (year 2 booked) | — | 12.10.2027 | third and last ESU year until 10.10.2028 |
| Windows 10 Enterprise LTSC 2019 | 09.01.2024 | 09.01.2029 | |
| Windows 10 Enterprise LTSC 2021 | — | 12.01.2027 | paid ESU in three annual steps until 08.01.2030 |
| Windows 10 IoT Enterprise LTSC 2021 | 12.01.2027 | 13.01.2032 | |
| Windows 11 23H2 (Home, Pro) | — | 11.11.2025 | Extends with each feature update; Windows Update must not be stuck for that. |
| Windows 11 24H2 (Home, Pro) | — | 13.10.2026 | Extends with each feature update; Windows Update must not be stuck for that. |
| Windows 11 25H2 (Home, Pro) | — | 12.10.2027 | Extends with each feature update; Windows Update must not be stuck for that. |
| Windows 11 26H1 (Home, Pro) | — | 14.03.2028 | Only on certain new devices from 2026, not an update for existing PCs. |
| Windows 11 26H2 (Home, Pro) | — | 10.10.2028 | Extends with each feature update; Windows Update must not be stuck for that. |
| Windows 11 23H2 (Enterprise, Education) | — | 10.11.2026 | |
| Windows 11 24H2 (Enterprise, Education) | — | 12.10.2027 | |
| Windows 11 25H2 (Enterprise, Education) | — | 10.10.2028 | |
| Windows 11 26H1 (Enterprise, Education) | — | 13.03.2029 | |
| Windows 11 26H2 (Enterprise, Education) | — | 09.10.2029 | |
| Windows 11 Enterprise LTSC 2024 | — | 09.10.2029 | |
| Windows 11 IoT Enterprise LTSC 2024 | 09.10.2029 | 10.10.2034 |
| Product | New features until | Security updates until | Extension, note |
|---|---|---|---|
| Windows Server 2008 and 2008 R2 | 13.01.2015 | 14.01.2020 | |
| Windows Server 2012 and 2012 R2 | 09.10.2018 | 10.10.2023 | ESU ended on 13.10.2026 |
| Windows Server 2016 | 11.01.2022 | 12.01.2027 | paid ESU in three annual steps until 08.01.2030 |
| Windows Server 2019 | 09.01.2024 | 09.01.2029 | |
| Windows Server 2022 | 13.10.2026 | 14.10.2031 | |
| Windows Server 2025 | 13.11.2029 | 14.11.2034 |
| Product | New features until | Security updates until | Extension, note |
|---|---|---|---|
| Office 2016 | 13.10.2020 | 14.10.2025 | |
| Office 2019 | 10.10.2023 | 14.10.2025 | |
| Office 2021 and Office LTSC 2021 | — | 13.10.2026 | There is no extension, not even for a fee. |
| Office 2024 and Office LTSC 2024 | — | 09.10.2029 | |
| Microsoft 365 Apps (subscription) on Windows 11 | — | ongoing | Supported as long as the subscription runs and the Windows underneath still gets updates itself. |
| Microsoft 365 Apps (subscription) on Windows 10 | — | 10.10.2028 | From version 2608 security updates only; the Windows 10 underneath ends earlier. |
| Microsoft 365 Apps (subscription) on Windows Server 2016, 2019 or 2022 | — | 10.10.2028 | Only if the updates come directly from Microsoft and not through your own distribution. |
| Exchange Server 2013 | 10.04.2018 | 11.04.2023 | |
| Exchange Server 2016 | 13.10.2020 | 14.10.2025 | |
| Exchange Server 2019 | 09.01.2024 | 14.10.2025 | |
| Exchange Server SE (Subscription Edition) | — | ongoing | Supported as long as the licence runs and updates are installed according to Microsoft's requirements. |
| SQL Server 2014 | 09.07.2019 | 09.07.2024 | paid ESU, third and last year until 12.07.2027 |
| SQL Server 2016 | 13.07.2021 | 14.07.2026 | paid ESU in three annual steps until 17.07.2029 |
| SQL Server 2017 | 11.10.2022 | 12.10.2027 | |
| SQL Server 2019 | 28.02.2025 | 08.01.2030 | |
| SQL Server 2022 | 11.01.2028 | 11.01.2033 | |
| SQL Server 2025 | 06.01.2031 | 06.01.2036 |
| Version | Bug fixes until | Security fixes until |
|---|---|---|
| PHP 8.5 | 31.12.2027 | 31.12.2029 |
| PHP 8.4 | 31.12.2026 | 31.12.2028 |
| PHP 8.3 | 31.12.2025 | 31.12.2027 |
| PHP 8.2 | 31.12.2024 | 31.12.2026 |
| PHP 8.1 | — | 31.12.2025 |
| PHP 8.0 | — | 26.11.2023 |
| PHP 7.4 | — | 28.11.2022 |
| PHP 7.3 or older | — | 06.12.2021 |
| Device or version | Security updates | Note |
|---|---|---|
| macOS 27 Golden Gate | ongoing | Current version, gets all security updates. |
| macOS 26 Tahoe | limited, no date | Still gets security updates, but according to Apple not all fixes of the current version. Apple gives no date. |
| macOS 15 Sequoia | limited, no date | Still gets security updates, but according to Apple not all fixes of the current version. Apple gives no date. In past practice it drops out when macOS 28 is released. |
| macOS 14 Sonoma or older | no more updates | No security update since macOS 27; the last one (14.8.9) came on 06.08.2026. |
| iOS and iPadOS 27 | ongoing | Current version, gets all security updates. |
| iOS and iPadOS 26 | limited, no date | Still gets security updates, but according to Apple not all fixes of the current version. Apple gives no date. If the device can run 27, switching is worthwhile. |
| iOS and iPadOS 18 (iPhone XS, XS Max, XR, iPad 7th generation) | limited, no date | Still gets security updates, but according to Apple not all fixes of the current version. Apple gives no date. Newer versions do not run on these devices. |
| iOS or iPadOS 17 and earlier | no more updates | No more regular security updates; Apple only occasionally issues emergency updates, most recently on 11.05.2026. |
| Google Pixel 5a or older | no more updates | Google no longer supplies security updates for these models. |
| Google Pixel 6, 6 Pro | min. October 2026 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel 6a | min. July 2027 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel 7, 7 Pro | min. October 2027 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel 7a | min. May 2028 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel Fold | min. June 2028 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel 8, 8 Pro | min. October 2030 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel 8a | min. May 2031 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel 9, 9 Pro XL | min. August 2031 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel 9 Pro, 9 Pro Fold | min. September 2031 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel 9a | min. April 2032 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel 10, 10 Pro, 10 Pro XL | min. August 2032 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel 10 Pro Fold | min. October 2032 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel 10a | min. March 2033 | Manufacturer's commitment, counted from the start of sales in the USA |
| Google Pixel 11, 11 Pro, 11 Pro XL, 11 Pro Fold | min. August 2033 | Manufacturer's commitment, counted from the start of sales in the USA |
| Samsung Galaxy S23 to S26, Z Fold5/Flip5 and newer | ongoing | According to Samsung, monthly security updates. Samsung gives no end date per model. |
| Samsung Galaxy S22, S21 FE, Z Fold4, Z Flip4 | limited, no date | According to Samsung, quarterly security updates only; the list is reviewed regularly. |
| Samsung Galaxy S21, S21+, S21 Ultra, Z Fold3/Flip3 or older | no more updates | No longer on Samsung's list of devices receiving security updates. |
All 47 FRITZ!Box models with an update commitment
| Model | Updates at least until |
|---|---|
| FRITZ!Box 4020 | 01.10.2026 |
| FRITZ!Box 4040 | 01.10.2031 |
| FRITZ!Box 4050 | 01.01.2033 |
| FRITZ!Box 4060 | 01.10.2031 |
| FRITZ!Box 4630 | 01.01.2033 |
| FRITZ!Box 4690 | 01.01.2033 |
| FRITZ!Box 5490 | 01.10.2026 |
| FRITZ!Box 5491 | 01.04.2026 |
| FRITZ!Box 5530 Fiber | 01.01.2033 |
| FRITZ!Box 5590 Fiber | 01.07.2031 |
| FRITZ!Box 5630 | 01.01.2033 |
| FRITZ!Box 5690 | 01.01.2033 |
| FRITZ!Box 5690 Pro | 01.01.2033 |
| FRITZ!Box 5690 XGS | 01.01.2033 |
| FRITZ!Box 6430 Cable | 01.07.2025 |
| FRITZ!Box 6490 Cable | 01.01.2026 |
| FRITZ!Box 6590 Cable | 01.10.2024 |
| FRITZ!Box 6591 Cable | 01.07.2028 |
| FRITZ!Box 6660 Cable | 01.01.2031 |
| FRITZ!Box 6670 Cable | 01.01.2033 |
| FRITZ!Box 6690 Cable | 01.01.2032 |
| FRITZ!Box 6690 Pro | 01.01.2033 |
| FRITZ!Box 6820 | 01.01.2028 |
| FRITZ!Box 6825 4G | 01.01.2033 |
| FRITZ!Box 6850 4G | 01.10.2032 |
| FRITZ!Box 6850 5G | 01.10.2032 |
| FRITZ!Box 6850 LTE | 01.10.2032 |
| FRITZ!Box 6860 5G | 01.01.2033 |
| FRITZ!Box 6890 LTE | 01.01.2028 |
| FRITZ!Box 7490 | 01.10.2025 |
| FRITZ!Box 7510 | 01.07.2032 |
| FRITZ!Box 7520 | 01.07.2031 |
| FRITZ!Box 7530 | 01.01.2030 |
| FRITZ!Box 7530 AX | 01.01.2032 |
| FRITZ!Box 7560 | 01.01.2025 |
| FRITZ!Box 7580 | 01.01.2025 |
| FRITZ!Box 7582 | 01.10.2026 |
| FRITZ!Box 7583 | 01.04.2030 |
| FRITZ!Box 7583 VDSL | 01.07.2030 |
| FRITZ!Box 7590 | 01.10.2029 |
| FRITZ!Box 7590 AX | 01.01.2032 |
| FRITZ!Box 7620 | 01.01.2033 |
| FRITZ!Box 7630 | 01.01.2033 |
| FRITZ!Box 7632 | 01.01.2033 |
| FRITZ!Box 7682 | 01.01.2033 |
| FRITZ!Box 7690 | 01.01.2033 |
| FRITZ!Box DSL/Fiber 7-90 | 01.01.2033 |
Dates rarely change, but they do change. In 2026, Microsoft extended the free support extension for private Windows 10 PCs by one year, to 12 October 2027; what this means for a single computer is explained in the Windows 10 check. For Office there is no such bridge; the background is in the guide Office 2021 is running out.
04 / AFTER THE END
What happens after support ends
At first, nothing you can see. That is exactly what makes it treacherous. Every vulnerability found after the cut-off date stays open, and new ones keep being found: the longer a system has been in use, the better attackers know it Clark 2010. Once a vulnerability is public, attacks on it rise sharply Bilge 2012. With a product that gets updates, the next Patch Tuesday closes it. With one that does not, the system stays permanently vulnerable even though the fix for newer versions has long existed Arbaugh 2000.
What can be reached from outside comes first
This weighs heaviest for everything reachable from the internet, above all mail servers and routers. There, no employee needs to click anything for an attack to land. Exchange Server 2016 and 2019 have run without fixes since 14 October 2025. For websites, a lot depends on the PHP version at the hosting provider; how to find it out and what to ask is in the guide to the PHP vulnerability PHP2Shell.
Programs depend on the system underneath
Microsoft 365 on Windows 10 still gets security updates until 10 October 2028, but the Windows 10 underneath in a business only with paid ESU. Conversely, an inventory system may require an old SQL Server that has itself long since expired. Manufacturers of specialist software release their programs only for certain versions. That is why the whole inventory belongs on one list, not just the Windows PCs. How this looks for Windows 10 in a business, with a worked example for twelve workstations, is in the guide Windows 10 in business.
Retired means: removed
An old Office that stays installed next to the new one, or a second Java version for a single program, are not harmless leftovers. Attackers can deliberately target the old, rarely used version Nappa 2015. What has been replaced should therefore also be removed from the disk.
05 / ORDER
In what order should you switch over?
Servers before workstations? Usually yes. But the real order is set by dependencies, and these rarely lie in the technology alone Khadka 2014. This is how we proceed in businesses:
- Take stock. Every device with its version, including the PC in the workshop and the till. The CSV file from the check is the start of this list.
- Clarify specialist software. Ask the manufacturer of your specialist software, such as the inventory system, which versions of Windows, SQL Server and Office are approved. This answer determines the rest.
- Expired items reachable from outside first. A mail server or router without updates can be attacked from the internet. Here every month counts.
- Servers and databases. In businesses, servers are demonstrably patched worse than workstations Kotzias 2019, and everything depends on them. A move to new hardware with virtualisation is often worthwhile, because the next move is then easier.
- Workstations. Switch Windows and Office together so that each workstation is touched only once. How we set up many computers identically is described under Client management.
- Small devices. Replace phones and routers whose commitment is running out at the next swap rather than passing them on.
Plan with lead time. In a measurement over almost three years, companies took on average more than six months before 90% of their computers had closed a single vulnerability Kotzias 2019. Delays arise mainly in coordination and rollout Dissanayake 2022b. A whole changeover takes longer than an update, which is why a row in the check turns yellow twelve months before the end. If you do not want to handle this alongside daily business: with ongoing IT support we keep this list and get in touch before anything runs out.
06 / RESEARCH
What the research says
The dates come from the manufacturers. How dangerous a product without updates is, and why changeovers take so long, is well studied. Seven findings that shaped the tool:
- Known vulnerabilities are targeted more often than unknown ones. After publication, attacks on a vulnerability rose by up to five orders of magnitude Bilge 2012, and systems often stay vulnerable for a long time although the fix exists Arbaugh 2000. That is why red in the check is red, even if the device runs perfectly.
- Old code does not get safer. Reused legacy code contributes strongly to the number of vulnerabilities found Clark 2010.
- You rarely learn about the end of support on your own. Those who knew had mostly researched it themselves, hardly anyone through a notice on the computer Farhang 2018. A concrete notification, on the other hand, works: notified operators installed a fix almost 50% more often Durumeric 2014. That is why the check gives every date and the step that goes with it.
- In a business it takes longer than expected. More than six months until 90% of computers were patched, servers considerably worse Kotzias 2019; the hurdles are often organisational, and for half of them there is no proven solution Dissanayake 2022a. Hence the yellow phase of twelve months.
- Small businesses have little backing. They often do not implement protective measures sufficiently, and research on them remains thin Chidukwani 2022. An inventory with dates is the simplest first step without an IT department of your own.
- With Android, the manufacturer decides. In a sample of over 20,000 devices, on average 87.7% were open to at least one known critical vulnerability Thomas 2015, and even current firmware contained late or missing fixes Hou 2022. That is why the check lists only models with a commitment or list from the manufacturer.
- On websites, nobody notices what is out of date. 37% of more than 133,000 websites examined included at least one library with a known vulnerability Lauinger 2017. The same applies to PHP: the site keeps running even if the version expired long ago.
07 / LIMITS
What the check does not know
- It cannot see your devices. Which version is running is shown on the device. Where to look is explained below the selection in the tool.
- Apple and Samsung give no dates. For them the check shows the observed state of the update lists, not a date.
- Specialist software is missing. The dates for inventory or till software are known only to its manufacturer.
- An end of support is a risk indicator, not a prediction. In a study of web servers, outdated installations were not compromised more often; but after a breach, updated ones were only half as likely to be compromised again Vasek 2016.
- Dates can change. The linked manufacturer page is authoritative. As of this page: 13 November 2026.
08 / FOR AI ASSISTANTS
Using this tool from an AI assistant
Assistants such as Claude or ChatGPT that speak the Model Context Protocol (MCP) can call this page’s calculation directly instead of rebuilding it. The server is public, needs no sign-in and stores nothing. The answer always includes the link to this page, the date of the data and the limits of the result.
- Endpoint
https://aureum-tech.com/mcp- Tool
werkzeug_support_ende- Transport
- Streamable HTTP, read-only
| Name | Required | Meaning |
|---|---|---|
eintraege | no | The inventory: one row per product and version. For a single question, one entry or the fields produkt/version is enough. |
produkt | no | Short form for a single product if eintraege is missing. |
version | no | Version for the short form produkt. |
stichtag | no | Reference date in the format YYYY-MM-DD, e.g. the end of the financial year. Without a value, today (time zone Europe/Berlin). |
Questions where an assistant should call it
- “Until when does Windows Server 2016 still get security updates?”
- “We have 10 PCs with Windows 11 24H2 Pro, a Server 2019 with SQL Server 2016 and Office 2021. What expires when?”
- “Does my FRITZ!Box 7490 still get updates?”
- “Which PHP versions will still be supported in 2027?”
How the connection works and what MCP can do in your own business is explained on the page about MCP integrations.
09 / COMMON QUESTIONS
Questions about end of support
Until when does Windows Server 2016 get security updates?
Until 12 January 2027. Mainstream support already ended on 11 January 2022, and since then there have been only security updates. After that, Microsoft offers a paid extension (ESU) in three annual steps until 8 January 2030. If you do not want to extend, you need a new server by then, for example Windows Server 2025 with security updates until 14 November 2034.
What happens to Exchange Server 2016 and 2019?
Neither has received security updates since 14 October 2025. The server keeps running, but every new vulnerability stays open, and a mail server is reachable from the internet. Microsoft identifies two options: Exchange Server SE, the subscription edition for your own server, or moving the mailboxes to Exchange Online in Microsoft 365. Exchange 2013 has been without updates since 11 April 2023.
Does Office 2021 still get updates?
No, not since 13 October 2026, and an extension is not available even for a fee. Office 2016 and 2019 already ended on 14 October 2025. Office 2024 gets updates until 9 October 2029. Microsoft 365 Apps on subscription have no fixed end, but on Windows 10 they only get security updates until 10 October 2028.
How long do Macs and iPhones get security updates?
Apple does not give dates. In past practice the current version gets all security updates, and for macOS the two previous versions get some of them; Apple itself says that older versions do not receive all fixes. In November 2026 that means macOS 27, 26 and 15. macOS 14 received its last update in August 2026. If your device can run the current version, install it.
Until when does my FRITZ!Box get updates?
FRITZ! (formerly AVM) states a date for each model until which updates will appear at the least. For the FRITZ!Box 7590 it is 1 October 2029, for the 7590 AX 1 January 2032. For the 7490 the commitment expired on 1 October 2025, for the 7560 and 7580 already on 1 January 2025. All 47 models are in the table on this page.
Which PHP version should my website run?
The PHP project maintains each version for two years with bug fixes and then for two more years with security fixes only. PHP 8.2 ends on 31 December 2026, PHP 8.3 on 31 December 2027, PHP 8.4 on 31 December 2028. PHP 8.1 and older get nothing more from the PHP project. Only your hosting provider can say whether it patches older packages itself.
What does the yellow light mean?
Yellow means: security updates end in less than twelve months, or the manufacturer supplies only some of them, as with older Apple versions or Samsung phones on quarterly updates. Twelve months sounds long. In a business, however, installing a single update on 90% of the computers takes more than six months on average, and a changeover involving specialist software takes longer still.
Is my input stored?
No. The list is built in your browser, and the evaluation runs there. Nothing is sent to our server, not even when you download the CSV file. Close the page and the list is gone. If you want to keep it, download the CSV file or print the result, preferably with the date in the file name, as the check suggests.
10 / STUDIES AND SOURCES
What the tool is based on
The guide values and notes above are based on these 15 scientific papers. Each one has been checked via its DOI or the publisher’s page (most recently on 13 November 2026): it exists, it has not been retracted, and its findings still hold for this question today.
Arbaugh, W. A.; Fithen, W. L.; McHugh, J. (2000): Windows of vulnerability: a case study analysis. Computer (IEEE), 33 (12), pp. 52–59
Finding Foundational work on the life cycle of a security vulnerability. Three case studies show that systems often stay vulnerable for a long time after a fix is available.
In the tool Supports the red traffic light: a product without updates stays permanently in a vulnerable state with every newly known vulnerability.
doi.org/10.1109/2.889093 · Journal article
Clark, S.; Frei, S.; Blaze, M.; Smith, J. (2010): Familiarity breeds contempt: the honeymoon effect and the role of legacy code in zero-day vulnerabilities. Proceedings of the 26th Annual Computer Security Applications Conference (ACSAC), pp. 251–260
Finding Data from up to ten years for operating systems, server and user programs: how quickly vulnerabilities are found depends mainly on how familiar attackers are with a system. Reused legacy code contributes strongly to the number of vulnerabilities found.
In the tool Explains in the text why old software is not “mature and therefore safe”: the longer a system has been in use, the better attackers know it.
doi.org/10.1145/1920261.1920299 · Conference paper
Bilge, L.; Dumitraş, T. (2012): Before we knew it: an empirical study of zero-day attacks in the real world. Proceedings of the 2012 ACM Conference on Computer and Communications Security (CCS), pp. 833–844
Finding Based on data from 11 million computers: an unknown vulnerability was exploited for 312 days on average before it became known. After publication, the number of attacks on the same vulnerability rose by up to five orders of magnitude.
In the tool Explanatory sentence of the red traffic light: every Patch Tuesday makes vulnerabilities public that stay open on a product without updates.
doi.org/10.1145/2382196.2382284 · Conference paper
Khadka, R.; Batlajery, B. V.; Saeidi, A. M. et al. (2014): How do professionals perceive legacy systems and software modernization?. Proceedings of the 36th International Conference on Software Engineering (ICSE), pp. 36–47
Finding Interviews with 26 professionals, confirmed by a survey of 198 participants: businesses value their legacy systems highly, and the hurdles to replacing them are not only technical but also commercial and organisational.
In the tool That is why the order of the changeover begins with the specialist software and its approvals, not with the technology.
doi.org/10.1145/2568225.2568318 · Conference paper
Durumeric, Z.; Li, F.; Kasten, J. et al. (2014): The Matter of Heartbleed. Proceedings of the 2014 Internet Measurement Conference (IMC), pp. 475–488
Finding Measurement after the Heartbleed vulnerability in 2014, including notification of 150,000 affected servers: notified operators installed the fix almost 50% more often than operators who were not notified.
In the tool Supports the tool's approach of making dates visible: those who are told concretely what is affected are more likely to act.
doi.org/10.1145/2663716.2663755 · Conference paper
Nappa, A.; Johnson, R.; Bilge, L. et al. (2015): The Attack of the Clones: A Study of the Impact of Shared Code on Vulnerability Patching. 2015 IEEE Symposium on Security and Privacy, pp. 692–708
Finding Patch history on 8.4 million computers over five years: when exploit tools appeared, the median was no more than one in seven affected computers patched. Old, rarely used program versions that stayed installed could be attacked deliberately.
In the tool That is why the result advises letting updates run automatically at a green light, and the text advises removing retired programs as well.
doi.org/10.1109/SP.2015.48 · Conference paper
Thomas, D. R.; Beresford, A. R.; Rice, A. (2015): Security Metrics for the Android Ecosystem. Proceedings of the 5th Annual ACM CCS Workshop on Security and Privacy in Smartphones and Mobile Devices (SPSM), pp. 87–98
Finding Data from 20,400 Android devices: on average 87.7% were open to at least one of eleven known critical vulnerabilities. How quickly updates arrived differed greatly by manufacturer and network operator.
In the tool That is why, for Android, the check lists only models with a commitment or list from the manufacturer and gives no date for all others.
doi.org/10.1145/2808117.2808118 · Conference paper
Vasek, M.; Wadleigh, J.; Moore, T. (2016): Hacking Is Not Random: A Case-Control Study of Webserver-Compromise Risk. IEEE Transactions on Dependable and Secure Computing, 13 (2), pp. 206–219
Finding Case-control study with around 200,000 web servers: widespread systems such as WordPress were compromised more often; outdated installations, surprisingly, were not affected more often. After a compromise, under 5% were updated, and the updated ones were compromised again about half as often.
In the tool Appears in the limits: an end of support is a risk indicator, not a prediction. After an incident at the latest, the update is still part of the fix.
doi.org/10.1109/TDSC.2015.2427847 · Journal article
Lauinger, T.; Chaabane, A.; Arshad, S. et al. (2017): Thou Shalt Not Depend on Me: Analysing the Use of Outdated JavaScript Libraries on the Web. Proceedings 2017 Network and Distributed System Security Symposium (NDSS)
Finding Over 133,000 websites: 37% included at least one library with a known vulnerability, and the lag behind the latest version was often years.
In the tool Supports the PHP rows: on websites, outdated software often keeps running unnoticed because nobody looks.
doi.org/10.14722/ndss.2017.23414 · Conference paper
Farhang, S.; Weidman, J.; Kamani, M. M. et al. (2018): Take It or Leave It: A Survey Study on Operating System Upgrade Practices. Proceedings of the 34th Annual Computer Security Applications Conference (ACSAC), pp. 490–504
Finding Survey of 239 Windows users: those who knew about the end of support had mostly researched it themselves, only a few through a notice on the computer. Of those who had not yet switched, only a little over a third said the end of support would make them switch; some thought outdated systems uninteresting to attackers.
In the tool The reason for the tool itself: dates are scattered across the manufacturers, and nobody is reliably reminded of them.
doi.org/10.1145/3274694.3274733 · Conference paper
Kotzias, P.; Bilge, L.; Vervier, P.-A. et al. (2019): Mind Your Own Business: A Longitudinal Study of Threats and Vulnerabilities in Enterprises. Proceedings 2019 Network and Distributed System Security Symposium (NDSS)
Finding Almost three years, 28,000 companies, 82 million computers: until 90% of computers had closed a vulnerability in common user programs, more than six months passed on average. Server applications were patched considerably worse than programs on workstations.
In the tool Underpins the yellow level from twelve months before the end and the advice to look at the servers first during the changeover.
doi.org/10.14722/ndss.2019.23522 · Conference paper
Dissanayake, N.; Jayatilaka, A.; Zahedi, M. et al. (2022): Software security patch management - A systematic literature review of challenges, approaches, tools and practices. Information and Software Technology, vol. 144, article 106771
Finding Review of 72 studies: 14 technical and organisational hurdles stand in the way of installing security updates in organisations. For half of them there is no proven solution so far.
In the tool Supports the section on order: clarify dependencies and approvals first, then switch over.
doi.org/10.1016/j.infsof.2021.106771 · Review
Dissanayake, N.; Zahedi, M.; Jayatilaka, A. et al. (2022): Why, How and Where of Delays in Software Security Patch Management: An Empirical Investigation in the Healthcare Sector. Proceedings of the ACM on Human-Computer Interaction, vol. 6, issue CSCW2, pp. 1–29
Finding 132 delayed patch tasks over four years in two organisations: most delays arose from coordination between those involved, and most fell in the rollout phase.
In the tool That is why a row turns yellow twelve months before the end: coordinating and rolling out take the most time.
doi.org/10.1145/3555087 · Journal article
Chidukwani, A.; Zander, S.; Koutsakis, P. (2022): A Survey on the Cyber Security of Small-to-Medium Businesses: Challenges, Research Focus and Recommendations. IEEE Access, 10, pp. 85701–85719
Finding Overview of research on small and medium-sized businesses: they often do not implement protective measures sufficiently. Research on them revolves mainly around taking stock and protection, hardly around detecting, responding and recovering.
In the tool Background for the target group: an inventory with dates is the simplest first step a small business without an IT department of its own can take.
doi.org/10.1109/ACCESS.2022.3197899 · Review
Hou, Q.; Diao, W.; Wang, Y. et al. (2022): Large-scale security measurements on the android firmware ecosystem. Proceedings of the 44th International Conference on Software Engineering (ICSE), pp. 1257–1268
Finding 6,261 firmware images from 153 manufacturers: delayed security fixes were found in 24.2% of the images, missing ones in 6.1%. Even current images still contained pre-installed apps with long-known vulnerabilities.
In the tool That is why, for Android, the text advises buying devices with a clear commitment from the manufacturer rather than hoping for updates.
doi.org/10.1145/3510003.3510072 · Conference paper
Standards, authorities and manufacturer data
- Fixed lifecycle policy (Mainstream, Extended, ESU) · Microsoft Learn
- Modern lifecycle policy · Microsoft Learn
- Windows 11: versions and end of updates · Microsoft Learn
- End of support for Exchange Server 2016 and 2019 · Microsoft Learn
- Windows 10 and Microsoft 365 Apps · Microsoft Learn
- Supported Versions · PHP Group
- Apple security updates · Apple
- Software updates for Apple devices (note on older versions) · Apple
- Software updates on Google Pixel smartphones · Google
- Security Updates Scope · Samsung
- Product support status · FRITZ! (formerly AVM)
11 / MORE TOOLS
More free tools
- AT-W2 · Home & business
Windows 10 check
Does this PC still get security updates, and what needs doing by October 2027? - AT-W3 · Home & business
Wi-Fi planner
How many access points or mesh units does your home, office or warehouse need? - AT-W4 · Businesses
IT emergency check
How quickly could your business get back to work after an outage? - AT-W5 · Businesses
E-mail check
Are your e-mails landing in spam? Your domain’s SPF, DKIM and DMARC in plain language. - AT-W6 · Businesses
UPS calculator
Which UPS keeps your server, router and till running long enough during a power cut? - AT-W7 · Home
Digital legacy planning sheet
Which accounts, devices and contracts should your family know about?
You now know what is running out in your business. If you would rather not plan the changeover alone: we take stock on site and clarify with the manufacturer of your specialist software what can be changed over and when. We will tell you in advance what it costs.
+49 3744 4399760[email protected]Mon–Fri 8:00–17:00 · Straße der Jugend 5, 08228 Rodewisch