TL;DR: A useful zero-day tabletop tests four things under time pressure: who decides, what evidence each decision needs, which affected devices come first, and how you verify the fix. Run it in 60 minutes with one fictional vulnerability and six timed injects. It builds preparedness and doesn't replace incident response.
Your small IT team can't scope devices, test a mitigation, brief leadership, and answer the phone all at once. In PDQ's State of Sysadmin 2026 report, 69% of sysadmins worry they're a single point of failure for critical knowledge. On a two-person team, that's more than half the department.
That makes preparation crucial: clear roles, escalation, and communication. This kit is a zero-day tabletop exercise small IT team members can run in an hour. An outside facilitator, like your manager or MSP contact, reads the scenario and keeps notes. Bring your patch response plan, inventory access, and a contact list.
What is the scenario and what are the injects?
It's Tuesday, 9:40 a.m. The vendor of Northpage Reader, a fictional PDF reader installed across your fleet, confirms attackers are exploiting a flaw that triggers when a user opens a crafted file. There's no patch and no CVE ID yet.
The facilitator reads each inject on the clock and asks for the evidence. "We'd check the console" doesn't count.
Time | Inject | Evidence to request | Decision to force |
|---|---|---|---|
0:00 | Vendor confirms active exploitation. No patch yet. | Advisory and affected versions | Who leads, and who works the devices? |
0:10 | Your scanner shows nothing. Inventory lists the app on 140 devices, and 25 more haven't checked in for two weeks. | Device list with installed version and last check-in | Do unseen devices count as affected? |
0:20 | Vendor publishes a mitigation that turns off a feature finance uses daily. | Who uses the feature, and a test result | Mitigate everywhere or by exposure? Who approves the disruption? |
0:30 | Twelve remote laptops are offline. One belongs to a traveling executive. | Owner, contact, and last-seen time | Wait, call, restrict access, or log an exception? |
0:40 | The patch ships. Leadership wants an answer in 15 minutes. | Pilot results and deployment status | Pilot size, downtime window, and what you tell leadership |
0:50 | The deployment reports success, but one device still shows the old version. | Timestamped post-deployment inventory or rescan | What counts as verified, and what stays open? |
On day zero, your scanner may have nothing to match against. VulnCheck found that 28.96% of the exploited vulnerabilities it tracked in 2025 showed exploitation evidence on or before the day their CVE was published. So scope from software inventory.
Have a security or incident response expert, like your MSP's, review the scenario before you run it.
What decisions should the team practice?
Each inject maps to a decision your patch response plan should already answer. Where it doesn't, you've found a gap.
Scope. Start with asset scoping from your inventory, and count devices you can't see as affected until evidence says otherwise. An inventory that's 85% complete gives you an 85% answer.
Roles. Name one incident lead who decides and communicates, and one operator who works the devices. Then have the facilitator pull one of you out for 10 minutes mid-exercise. Whatever stalls lives in one person's head.
Patch or mitigation order. Rank by exposure and business impact. Devices that open outside files all day, like finance and the front desk, go first. Start with a small pilot group, using the same safe deployment planning you'd apply to any patch.
Downtime. Decide who can approve a business-hours disruption. In PDQ's State of Sysadmin report, 54% of sysadmins rank a critical outage during business hours among their top concerns, and 49% say the same about management being unaware of risks. Use the exercise to ask leadership for a standing preapproval so that the 0:20 decision takes minutes instead of a meeting.
Unavailable devices. Set a deadline, then restrict access or record an exception with an owner, a reason, and a review date.
Business impact. Draft the leadership update during the exercise: what's affected, what you've done, and what you need from them.
How do you turn the exercise into improvements?
A zero-day response exercise pays off only when it changes something. Hold a 15-minute debrief right away and capture decisions, delays, missing contacts, evidence gaps, and runbook changes.
Score time to evidence instead of right answers. A device list that takes 20 minutes in a calm room takes longer on the real day.
Triage the fixes, then give each an owner and a due date. Fold the changes into your documented vulnerability management policy and response plans, then rerun the vulnerability incident tabletop next quarter with a different application and the roles swapped.
How can PDQ support scoping and remediation?
PDQ can speed up two answers this exercise keeps asking for: which devices are affected and whether the fix landed.
To scope, filter devices by software name and version with dynamic groups, and check each device's last check-in time. To remediate, deploy a package from the Package Library or a custom package to that group. If a device is offline, PDQ queues the deployment and retries when it reconnects. Then confirm the installed version in inventory before you call anything verified.
PDQ vulnerability scanning depends on known vulnerability data, and it doesn't replace incident command, threat intelligence, or security response.
Try PDQ free for 14 days to get software inventory, device groups, remediation options, and deployment results in one place.



