End-of-Life Software reports products whose vendor support has ended or is ending.

---

Why it matters

End-of-life software:

• stops receiving security fixes;
• increasingly blocks compliance pass rates;
• may not support modern policy controls;
• becomes a long-term exception burden;
• can remain installed long after the upgrade project closes.

---

Workflow

1. Filter by lifecycle status and support date.
2. Sort by host count.
3. Separate business-critical, optional and residual software.
4. Assign an owner and target version/date.
5. Upgrade or remove through supported tooling.
6. For exceptions, create a dated compliance exception with compensating control.
7. Recheck after the next AMTD refresh.