After a week of loud security headlines, the useful Monday question is narrow: which of the flaws being exploited right now exist in our environment, and which of our systems can be reached from the internet?
This playbook is a half-day routine for an IT director or small team. It works after any busy news week, not only this one.
Why the KEV catalog sets your order
Patch queues are always longer than the time available. CISA’s Known Exploited Vulnerabilities (KEV) catalog lists vulnerabilities exploited in the wild, and CISA says organizations should use it as an input to their vulnerability management prioritization framework. Entries show a date added and a due date, with an action note to apply mitigations in accordance with vendor instructions.
A flaw on that list is not a theoretical risk. Treat it as ahead of a higher-scored flaw with no known exploitation. The catalog is downloadable as CSV and JSON, so you can compare it against your asset inventory instead of reading entries by hand.
Recent additions show the range. On November 18, 2026, CISA added four entries: Synology DiskStation Manager (DSM), BerriAI LiteLLM, Apache Axis, and Vanderbilt University’s REDCap. On November 17, CISA added one: Perforce Puppet Enterprise. A NAS operating system, an AI gateway, a web services framework, a research data platform, and a configuration management server rarely sit on the same team’s list. That is why a catalog match beats intuition.
Step one: match the catalog to your inventory
- Export your software and device list, including network storage, firewalls, VPN appliances, hypervisors, and line-of-business servers.
- Filter the KEV list to vendors and products you run.
- Note the version for each match, since a catalog entry applies to specific versions.
- Check each vendor’s advisory for fixes or mitigations.
If you cannot produce the inventory in an hour, that is your first finding. Write it down.
Step two: patch by exposure, then by exploitation
Order matches using two questions: is the system reachable from the internet, and is the flaw on KEV? Internet-facing and listed goes first. CISA’s ransomware guide advises prioritizing timely patching of internet-facing servers, especially for known exploited vulnerabilities.
| Priority | Condition | Target action |
|---|---|---|
| 1 | KEV match and reachable from the internet | Patch or mitigate immediately, then verify the version |
| 2 | KEV match, internal only | Patch in the next change window and restrict reach |
| 3 | No KEV match, internet-facing | Patch on normal cycle, confirm exposure is needed |
| 4 | No KEV match, internal | Normal cycle |
If a patch is not available, use the vendor’s mitigation, restrict access, or take the service offline until it is.
Step three: check edge devices and NAS first
Firewalls, VPN gateways, routers, and network storage sit where attackers look first. CISA’s edge device guidance urges organizations to replace end-of-support edge devices, isolate edge devices from critical systems, and periodically audit device configurations for unauthorized changes.
For network storage, confirm the firmware version, whether the admin interface or file-sharing services are reachable from outside, whether default or shared accounts exist, and whether the device holds the only copy of important data. Review administrator accounts and recent configuration changes you cannot explain.
Step four: find internet-exposed admin panels
CISA’s guidance is to remove any internet-exposed management interfaces or use zero trust capabilities. Its ransomware guide adds not to expose services such as remote desktop protocol on the web, and notes that threat actors often gain initial access through exposed and poorly secured remote services.
Scan your public address space from outside, list every open management port, and ask of each one: who needs this, from where, and why is it not behind a VPN or access gateway? Do not forget cloud consoles, backup dashboards, hypervisor interfaces, and developer tools that someone stood up for a project.
Step five: review vendor and provider access
Third parties often hold standing access to your systems. CISA’s guidance for customers of managed service providers recommends that provider accounts not be assigned to internal administrator groups, that MFA be enforced on all provider accounts, and that accounts be disabled promptly when a contract ends, since that step can be overlooked.
Pull a list of vendor accounts, remote support tools, and VPN profiles. Confirm each has an owner, a purpose, and current MFA. Disable what is no longer needed. Our vendor offboarding checklist walks through the full process.
Step six: verify backups, do not assume
CISA’s ransomware guide recommends offline, encrypted backups of critical data and regular testing of backup availability and integrity in a disaster recovery scenario. It also notes that many ransomware variants try to find and delete or encrypt accessible backups.
Check that last night’s job completed, that at least one copy sits where a compromised domain account cannot delete it, and that someone has restored a real file or system recently. Our recovery drill guide shows how to test a whole workflow.
Close the loop
Before the day ends, record what you found, what you changed, what remains open, and an owner and date for each open item. Schedule a short recheck for the end of the week. If you found an unexplained admin account or a device that was exposed and unpatched, treat it as a potential incident, preserve logs, and bring in your incident response process.
Where Z7 fits
Z7 offers cybersecurity services, including managed detection and response, and a security assessment to help you find exposure and reduce risk, and we publish current threat briefs in the Z7 Cyber library. To work through this list with a partner, book a conversation.