performing-endpoint-vulnerability-remediation

name	performing-endpoint-vulnerability-remediation
description	Performs vulnerability remediation on endpoints by prioritizing CVEs based on risk scoring, deploying patches, applying configuration changes, and validating fixes. Use when remediating findings from vulnerability scans, responding to critical CVE advisories, or maintaining endpoint compliance with patch management SLAs. Activates for requests involving vulnerability remediation, CVE patching, endpoint vulnerability management, or security fix deployment.
domain	cybersecurity
subdomain	endpoint-security
tags	["endpoint","vulnerability-management","patching","CVE","remediation","CVSS"]
version	1.0.0
author	mahipal
license	Apache-2.0
nist_csf	["PR.PS-01","PR.PS-02","DE.CM-01","PR.IR-01"]

Performing Endpoint Vulnerability Remediation

When to Use

Use this skill when:

• Remediating vulnerabilities identified by scanners (Nessus, Qualys, Rapid7)
• Responding to zero-day CVE advisories requiring immediate patching
• Maintaining compliance with patch management SLAs (critical within 14 days, high within 30 days)
• Building a prioritized remediation plan from vulnerability scan results

Do not use this skill for vulnerability scanning itself (use scanning tools) or for application-layer vulnerability remediation (use DevSecOps processes).

Common Misconfigurations & Verification

• Reported-but-not-applied: WSUS/SCCM/Intune marking a KB as "deployed" means it was sent, not installed. Confirm on the host with Get-HotFix -Id KBxxxxxxx or wmic qfe; a deployment dashboard alone is not proof.
• Reboot pending: many patches stage but only take effect after reboot, so the host stays vulnerable while showing "patched." Check Get-Item "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending" and the WindowsUpdate RebootRequired key, then verify the reboot actually happened.
• Superseded patches: scanners flag a missing KB that has been replaced by a newer cumulative/rollup. Verify the superseding update is installed rather than chasing the obsolete KB, which will never appear.
• Config remediation drift: registry/GPO/service fixes (SMBv1 off, Spooler disabled, LLMNR off) silently revert via a later GPO refresh, app reinstall, or gpupdate. Re-check the effective setting, not just that you set it once — confirm no conflicting GPO re-enables it.
• Verification: the authoritative close is a re-scan with the original tool (nessuscli/Qualys/InsightVM) targeting the same plugin/QID, confirming the finding no longer fires. For config fixes, validate the live state (Get-SmbServerConfiguration, Get-Service, Get-ItemProperty) on the endpoint, not the deployment console.

Prerequisites

• Vulnerability scan results (Nessus, Qualys, or Rapid7 export in CSV/XML format)
• Patch management platform (WSUS, SCCM, Intune, or third-party like Automox)
• Administrative access to target endpoints or deployment infrastructure
• Change management process for production endpoint patching
• Testing environment for patch validation before production rollout