patch-campaign
/patch-campaign
Plan and run a patch or remediation campaign — scoping affected assets, rollout rings, maintenance windows, rollback, owner communication, progress tracking and verification — for OS, application, firmware or cloud image updates. Use when a vulnerability or set of fixes must be deployed across many systems on a deadline.
- Author
- kaandgnsh ↗
- Repository
- Claude-Blue ↗
- Licence
- MIT
- Last repository change
- 01.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Plan and run a patch or remediation campaign — scoping affected assets, rollout rings, maintenance windows, rollback, owner communication, progress tracking and verification — for OS, application, firmware or cloud image updates. Use when a vulnerability or set of fixes must be deployed across many systems on a deadline.
Original author description
Plan and run a patch or remediation campaign — scoping affected assets, rollout rings, maintenance windows, rollback, owner communication, progress tracking and verification — for OS, application, firmware or cloud image updates. Use when a vulnerability or set of fixes must be deployed across many systems on a deadline.
How it works
- Plan
- Execute & track
- Output
- Related skills
- References
SKILL.md preview
--- name: patch-campaign description: Plan and run a patch or remediation campaign — scoping affected assets, rollout rings, maintenance windows, rollback, owner communication, progress tracking and verification — for OS, application, firmware or cloud image updates. Use when a vulnerability or set of fixes must be deployed across many systems on a deadline. license: MIT metadata: category: vulnerability-management version: "2.0.0" verification: documented --- # Patch Campaign ## Plan 1. **Scope**: affected assets from scanner + inventory + EDR software inventory (scanner alone misses unscanned assets). Group by platform, owner, criticality, and deployment tool (WSUS/Intune/ConfigMgr, Ansible, Jamf, AWS SSM Patch Manager, Azure Update Manager, golden images). 2. **Rings**: test/lab → pilot (5–10%, diverse) → broad → critical/sensitive systems with app-owner sign-off. Define success criteria per ring (no P1/P2 incidents, app health checks). 3. **Windows & rollback**: maintenance windows, snapshot/backup before change, documented rollback (uninstall KB, previous AMI/image, package downgrade). 4. **Exceptions**: systems that can't patch → compensating controls and `vuln-exception-review`. 5. **Communication**: owners get a list of their assets, deadline, and instructions; escalation path for misses. ## Execute & track | Metric | Source | |---|---| | % assets patched by ring/owner | Deployment tool + verification scan | | Failed installs | Tool reports (`Get-WindowsUpdateLog`, SSM compliance) | | Reboots pending | Patched but not effective until reboot | | Unreachable/unknown | Offline assets, no agent | Verification must come from an independent source (rescan or installed-version query), not only from the deployment tool's success status. AWS SSM example: `aws ssm list-compliance-summaries --filters Key=ComplianceType,Values=Patch,Type=EQUAL`. ## Output ``` Campaign <CVE/fix> deadline <date> Scope <n> assets (owners <n>) Rings: <status> Patched & verified <n> (<%>) Pending reboot <n> Failed <n> Exceptions <n> Unknown <n> Blockers: <> Next update: <date> ``` ## Related skills `vuln-prioritization`, `scan-result-triage`, `vuln-exception-review`, `asset-inventory-reconciliation` ## References - NIST SP 800-40 Rev. 4, Enterprise Patch Management Planning: https://csrc.nist.gov/pubs/sp/800/40/r4/final - AWS Systems Manager Patch Manager: https://docs.aws.amazon.com/systems-manager/latest/userguide/patch-manager.html - Windows Update for Business / Autopatch: https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/
Versions
The database has no other skills named patch-campaign.
Database snapshot: 13.11.2026 · package version 069911408cd2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90ot-vulnerability-management
Manage vulnerabilities in OT/ICS — passive version identification, ICS advisories (CISA ICSA, vendor PSIRTs), exploitability in context (network reachability, required access), compensating controls when patching isn't possible, vendor-approved patch testing and maintenance… - 90patch-plan
Design a vulnerability management program — SLAs, asset tiers, escalation, and metrics. Use when asked to "design a patching program", "set vulnerability SLAs", or "define our patch cadence". - 100implementing-patch-management-for-ot-systems
Implements a structured patch management program for OT/ICS environments where IT-style patching can cause process disruption or safety hazards, covering vendor compatibility testing, risk-based prioritization, staged test deployment, maintenance window coordination, rollback… - 98performing-endpoint-vulnerability-remediation
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… - 90vulnerability-management
Finds, prioritizes, and closes out vulnerabilities across code, dependencies, images, and infrastructure without drowning the team in unactionable findings. Use this whenever the user is deciding what to patch first, has a scanner producing hundreds of CVEs, is setting patch… - 100patch-sweep
Respond to a CVE wave across a whole portfolio of apps at once: inventory every repo and the platform project and domain it actually serves, find the real production branch, spot stale manual deploys, decide which apps are affected, mitigate, patch, ship, and confirm production.…