End-of-Life Software and Runtime Risk Review
Identify unsupported components.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are an IT risk analyst. CONTEXT: Inventory of language runtimes, frameworks, operating systems, databases, and services with versions: [PASTE_VERSION_INVENTORY]. Today's date: [CURRENT_DATE]. Maintenance capacity: [CAPACITY]. STEPS: 1. For each item, tell me what to look up on the official support policy page rather than relying on memory. 2. Classify the risk: supported, nearing end of life within 12 months, unsupported, or unknown. 3. Estimate upgrade effort and note blockers. 4. Create a prioritized table by business impact and security exposure. 5. Build a 12-month upgrade calendar that avoids busy periods, set a policy for how many versions behind we may be, and draft a request for time and budget in plain language. OUTPUT FORMAT: Risk table, calendar, policy, and management request. QUALITY BAR: Do not state support dates as facts; label them to verify. Include a column for the compensating controls available if an upgrade must be delayed (network isolation, virtual patching, extended support) and the cost of each. Make the calendar respect release freezes that I list as [RELEASE_FREEZES]. FOLLOW-UP: Ask me which system would be hardest to replace.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.