Microsoft Advanced Threat Analytics 1.x · Version Status

Microsoft Advanced Threat Analytics 1.x End of Life Date

Microsoft Advanced Threat Analytics 1.x end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (learn.microsoft.com); the source of each date is on the product page.

⚠ Microsoft Advanced Threat Analytics 1.x is past end of life. This version no longer receives security patches. 277 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 13, 2026
277 days past EOL
Latest Release
1.9.3 (1.9.7576)
Standard release
Release Date
Nov 25, 2015
Microsoft Advanced Threat Analytics 1.x series
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

Microsoft Advanced Threat Analytics 1 was released on November 25, 2015 and support ended on January 13, 2026 — a supported lifespan of 10 years and 2 months. The last patch it will ever receive is 1.9.3 (1.9.7576), published September 14, 2020 — 5 years and 4 months before support ended. It has been without security patches for 9 months.

All Microsoft Advanced Threat Analytics versions
40 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
30/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
Extended Support
Extended Microsoft Advanced Threat Analytics 1.x support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Microsoft Advanced Threat Analytics Versions
VersionLatestEOL DateStatus
→ 1.x 1.9.3 (1.9.7576) Jan 13, 2026 EOL

What does Microsoft Advanced Threat Analytics 1.x end of life mean?

When Microsoft Advanced Threat Analytics 1.x reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Microsoft Advanced Threat Analytics 1.x past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Microsoft Advanced Threat Analytics 1.x reach end of life?
Microsoft Advanced Threat Analytics 1.x reached end of life on January 13, 2026. This version is no longer receiving security patches.
Is Microsoft Advanced Threat Analytics 1.x still supported?
No. Microsoft Advanced Threat Analytics 1.x reached end of life on January 13, 2026 and is no longer receiving security patches.
What should I upgrade to from Microsoft Advanced Threat Analytics 1.x?
Check the Microsoft Advanced Threat Analytics full timeline for currently supported versions.
What are the security risks of running Microsoft Advanced Threat Analytics 1.x past EOL?
When Microsoft Advanced Threat Analytics 1.x reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Microsoft Advanced Threat Analytics should migrate immediately or implement compensating controls.
Data from the vendor's own lifecycle pages (learn.microsoft.com) · Generated at build time · How we source data →