Patch Priority.
Six tickets. One small team. What gets fixed first?
Fictional products, assets, IDs, CVSS examples, and illustrative EPSS probabilities. *A fictional KEV-style catalog, not actual CISA listings. Best lanes follow the displayed facts and this game's team policy.
About Patch Priority
Lead a small security team through three patch sprints. Weigh severity, exploitation, exposure, and controls as capacity shrinks. Sort fictional tickets, reduce simulated risk, and share your score.
How it works
- Select a ticket, read its signals, then tap Patch now, Schedule, Mitigate, or Accept. You can revise assignments before closing each sprint. Patch slots shrink from three to two to one.
- A run draws 18 tickets across three sprints from 36 fictional scenarios. Points reward appropriate risk treatment and decision streaks. Risk units and treatment effectiveness are invented game weights, not a real risk calculation.
- After each sprint, review every decision and a short lesson. Play the shared UTC daily queue or a fresh practice queue, save your best on this device, and share a score card.
What you'll learn
- CVSS base measures severity, not organizational risk. EPSS forecasts exploitation activity in the next 30 days, not the chance of compromise for your host.
- Known exploitation and internet exposure usually come before a high severity score on a contained asset. CISA KEV records exploitation evidence; federal remediation directives have a specific scope.
- Compensating controls can buy time but leave residual risk. Verify coverage, assign an owner, and review deferred work or approved acceptance.
- Use exploitation, exposure, mission impact, and feasible remediation together. The game lanes are a training policy, not the SSVC decision tree.
FAQ
Is Patch Priority free?
Yes. No account is needed. It runs in your browser and stores only best scores on your device. There are no live scans or paid API calls.
Are these real vulnerabilities or live EPSS scores?
No. All products, assets, VULN identifiers, severity examples, and probabilities are fictional. The concepts come from FIRST and CISA, linked in References. Game points are not a production risk model.
Can I use a phone or keyboard?
Yes. Tap a ticket, then tap a lane. On desktop, Tab and Enter select tickets; keys 1 through 4 assign lanes only while focus is inside the game. There is no timer.
Keep going
From severity to a response
CVSS base scores describe technical severity, not organizational risk. Both v3.1 and v4.0 use these severity bands: None 0.0, Low 0.1–3.9, Medium 4.0–6.9, High 7.0–8.9, and Critical 9.0–10.0. FIRST CVSS v4.0 and v3.1 define the metric systems.
EPSS estimates the probability of exploitation activity against a published vulnerability in the next 30 days. It does not estimate the probability that your particular system will be compromised. The game uses invented probabilities as teaching examples, not live FIRST predictions. FIRST EPSS
CISA's KEV catalog records vulnerabilities with evidence of exploitation in the wild. An internet-facing, known-exploited service usually deserves urgent attention, subject to mission impact and feasible treatments. BOD 22-01 established remediation requirements for Federal Civilian Executive Branch agencies using CISA's catalog timelines. It was superseded and revoked by BOD 26-04. These federal requirements are not universal deadlines for private organizations. Consult the current directive and catalog for applicable timelines. CISA KEV, BOD 22-01, BOD 26-04
CISA's SSVC guide asks about Exploitation (none, proof of concept, or active), Automatable (can exploitation be automated across targets?), Technical Impact (partial or total control), and Mission and Well-being (combining mission prevalence and public well-being impact). Its outcomes are Track (normal update timelines), Track* (closer monitoring, normal timelines), Attend (supervisory attention and faster remediation), and Act (leadership attention and remediation as soon as possible). The four game lanes are a simplified team policy, not SSVC outcomes or a substitute for its decision tree. CISA SSVC guide
A compensating control can reduce likelihood or impact while leaving residual risk. Verify its coverage, keep an owner for remediation, and reassess when conditions change. Acceptance needs approval and review; it does not fix the flaw. Patching should also be verified. CISA mitigation guide
Continue with the CVE lookup tool, the free vulnerability scanner, or the Security+ course.