Vulnerability Management
Keep Devices and Software Updated
Check what needs updating and use your existing update tools. Give exposed systems and actively exploited vulnerabilities attention first, with a plan for failed updates.
Content review: 2026-09-22 · Estimated effort: High
Priority and effort are suggestions, not risk scores or deadlines. Check business impact, vendor instructions, licenses and obligations before making changes. Test before wider rollout.
Before you start
Before starting: identify critical services, change approvers, backups, and recovery options. Plan for restarts and business disruption.
Put it into practice
- Use supported automatic updates where appropriate for operating systems, browsers, applications, and network equipment, including non-Windows systems. Retire or isolate unsupported products.
- Compare vendor advisories and CISA KEV entries with your inventory. Consider active exploitation, exposure, privileges, and business impact together; a severity score alone is not organizational risk.
- Assign risk-based deadlines and owners. Federal KEV deadlines are not universal SMB deadlines; check obligations that apply to you.
- Pilot updates on representative systems. For urgent exploitation when patching is unsafe or unavailable, assess vendor mitigations or temporary isolation. Record exceptions and review dates.
- Verify: check installed versions and restart status against the advisory, then confirm business services work. A successful deployment job alone is not proof that a fix took effect.
Use what you have
Tools and templates
“Included” tools require an eligible product or subscription. Options reviewed 2026-09-22; check current vendor terms.
Start without another software subscription
Use supported Windows Update capabilities, vendor update instructions and the free CISA catalog with the patch worksheet.
What to account for: Central deployment tools, extended support and some application updates can cost extra. A free catalog does not scan devices or prove that a patch was installed.
Allow for equipment, storage and staff time. Eligibility details are linked below.
Windows Update client policies
No extra service charge on supported Pro, Education and Enterprise editions
Start with Windows Update and use the documented Group Policy settings where supported to plan a pilot and rollout. Track actual versions and restart status.
Limits: Intune and other management products may require separate licenses. This does not update every third-party app. Confirm OS support and any extended-update entitlement rather than assuming all Windows 10 devices still receive free fixes.
Your information: Windows communicates with Microsoft update services. Management/reporting services may also receive device information when configured.
Official instructions: Windows Update client policies ↗CISA Known Exploited Vulnerabilities catalog
Free public reference
Match listed vulnerabilities against your inventory and vendor advisories before deciding which updates or mitigations apply.
Limits: Not a scanner or a complete vulnerability list. Federal remediation deadlines are not automatically deadlines for your business.
Your information: Read or download the public catalog; you do not need to submit your inventory.
Official instructions: CISA Known Exploited Vulnerabilities catalog ↗Download a working template
Open the Excel or Word file using your existing Microsoft Office license. Replace fictional entries, fill in the blanks and save your own copy. These manual worksheets have no macros, scoring or automatic verification.
- Patch and exception tracker (Excel (.xlsx)) ↓
Track affected systems, vendor advice, exposure, pilot results, installed-version verification and approved exceptions.
Fictional worksheet preview: Patch and exception tracker Asset or service reference Current version Business service test result EXAMPLE-LAPTOP-01 Not verified Not tested Three columns shown. The full worksheet also records vendor advice, recovery planning, installed-version checks and exceptions. Check the installed version and business service after an update.
Fictional worked example
Use these invented entries as a guide when filling in your worksheet. They are not a customer story or lab result. Record what you observe in your own checks.
A team plans an update for an office laptop used by its invoicing application.
Use the Patch and exception tracker template.
What to enter before testing
- Asset or service reference
- EXAMPLE-LAPTOP-02
- Current version
- Record observed version before change
- Pilot and recovery plan reference
- Pending: approved maintenance and recovery plan
- Business service test result
- Not tested
How to verify
Check the actual vendor advisory and applicable supported version. After an authorized pilot, confirm installed version and required restart, then open the invoicing application and run an approved non-production workflow. Record actual evidence, not just an update download.
If the result is unexpected
If installation fails or the workflow breaks, pause wider deployment and follow the approved vendor-supported recovery plan. Track any remaining exposure with an owner and time-bounded exception; a successful pilot does not prove every device is updated.
Keep completed worksheets private. Leave out passwords, recovery keys and confidential messages. This site does not receive your edits, but a cloud editor or synced folder may send them to its provider.
Sources and review approach
These guides use selected NIST CSF 2.0 alignments. They are not official crosswalks or complete framework implementations. We have not tested these steps in your environment.
- NIST CSF 2.0: ID.RA-01: vulnerability identification
- NIST CSF 2.0: PR.PS-02: software maintenance
- https://www.nist.gov/publications/nist-cybersecurity-framework-csf-20 ↗
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog ↗