Patch management is the systematic process of identifying, testing, deploying, and verifying software updates to remediate vulnerabilities across an organization's IT infrastructure. An effective patc
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Patch management is the systematic process of identifying, testing, deploying, and verifying software updates to remediate vulnerabilities across an organization's IT infrastructure. An effective patc
Patch management is the systematic process of identifying, testing, deploying, and verifying software updates to remediate vulnerabilities across an organization's IT infrastructure. An effective patch management workflow reduces the attack surface while minimizing operational disruption through structured testing, approval gates, and phased rollouts.
When to Use
When deploying or configuring implementing patch management workflow capabilities in your environment
When establishing security controls aligned to compliance requirements
When building or improving security architecture for this domain
When conducting security assessments that require this implementation
Common Misconfigurations & Verification
OS-only patching — third-party apps (Adobe, Java, browsers) left unpatched. Verify the workflow enumerates third-party and firmware updates.
No post-patch verification — verify a remediation scan confirms install, not just the deployment tool's success flag.
No rollback path — verify snapshots/rollback steps exist and were tested before production rings.
Phased rollout skipped — verify ring serialization and soak times are enforced (serial/max_fail_percentage).
Third-Party Patches: Adobe, Java, Chrome, Firefox, etc.
Deployment Rings (Phased Rollout)
Ring
Environment
% of Fleet
Soak Time
Purpose
Ring 0
Lab/Test
N/A
24-48 hrs
Functional validation
Ring 1
IT Early Adopters
5%
48-72 hrs
Real-world pilot
Ring 2
Business Pilot
15%
5-7 days
Broader compatibility
Ring 3
General Deployment
50%
7-14 days
Main rollout
Ring 4
Mission Critical
30%
After Ring 3
Final deployment
Workflow
Step 1: Configure Patch Sources
# WSUS (Windows Server Update Services)# Configure WSUS server to sync with Microsoft Update# Via PowerShell on WSUS server:
Install-WindowsFeature -Name UpdateServices -IncludeManagementTools
& "C:\Program Files\Update Services\Tools\WsusUtil.exe" postinstall CONTENT_DIR=D:\WSUS
# Configure GPO for WSUS clients# Computer Configuration > Administrative Templates > Windows Components > Windows Update# Specify intranet Microsoft update service location: http://wsus-server:8530