[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EVC2JB6WST7V144PDC7HNP":3,"skill-same:01M6EVC2JB6WST7V144PDC7HNP":121},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":14,"repositoryHtmlUrl":67,"repositoryHomepageUrl":68,"ownerHtmlUrl":69,"ownerBlogUrl":6,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6EVC2JB6WST7V144PDC7HNP","implementing-patch-management-workflow",null,"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","henriquescastilho\u002Fmy-claude","henriquescastilho","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153296945?v=4","01M6ESH7EXPXTH9CVQ4K16SRG8","Henrique Scheer","01M6ESH7JHEK2PTNNH4HEH787Z",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-patch-management-workflow\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"workflow","patch","management","implementing patch management workflow","software","testing","id","systematic","across","organization","process","vulnerability","ansible","risk","vulnerability-management","sccm","wsus","patch-management","vulnerabilities","cybersecurity","2026-11-10 10:12:30",false,"---\nname: implementing-patch-management-workflow\ndescription: Patch management is the systematic process of identifying, testing, deploying,\n  and verifying software updates to remediate vulnerabilities across an organization's\n  IT infrastructure. An effective patc\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- vulnerability-management\n- patch-management\n- wsus\n- sccm\n- ansible\n- risk\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- ID.RA-01\n- ID.RA-02\n- ID.IM-02\n- ID.RA-06\nmitre_attack:\n- T1190\n- T1203\n- T1068\n---\n# Implementing Patch Management Workflow\n\n## Overview\nPatch 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.\n\n\n## When to Use\n\n- When deploying or configuring implementing patch management workflow capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Vulnerability scan results identifying missing patches\n- Patch management tools (WSUS, SCCM\u002FMECM, Ansible, Intune, Jamf)\n- Test environment mirroring production\n- Change management process (ITIL or equivalent)\n- Asset inventory with OS and application versions\n\n## Core Concepts\n\n### Patch Lifecycle Phases\n1. **Discovery**: Identify available patches from vendors and vulnerability scans\n2. **Assessment**: Evaluate patch applicability and risk\n3. **Prioritization**: Rank patches by severity, exploitability, and asset criticality\n4. **Testing**: Validate patches in non-production environment\n5. **Approval**: Change advisory board (CAB) review and approval\n6. **Deployment**: Phased rollout to production systems\n7. **Verification**: Confirm successful installation and no regressions\n8. **Reporting**: Document compliance metrics and exceptions\n\n### Patch Categories\n- **Security Patches**: Address CVEs and security vulnerabilities\n- **Critical Updates**: Non-security bug fixes affecting stability\n- **Service Packs**: Cumulative update collections\n- **Feature Updates**: New functionality (Windows feature updates, etc.)\n- **Firmware Updates**: BIOS\u002FUEFI, NIC, storage controller firmware\n- **Third-Party Patches**: Adobe, Java, Chrome, Firefox, etc.\n\n### Deployment Rings (Phased Rollout)\n| Ring | Environment | % of Fleet | Soak Time | Purpose |\n|------|------------|------------|-----------|---------|\n| Ring 0 | Lab\u002FTest | N\u002FA | 24-48 hrs | Functional validation |\n| Ring 1 | IT Early Adopters | 5% | 48-72 hrs | Real-world pilot |\n| Ring 2 | Business Pilot | 15% | 5-7 days | Broader compatibility |\n| Ring 3 | General Deployment | 50% | 7-14 days | Main rollout |\n| Ring 4 | Mission Critical | 30% | After Ring 3 | Final deployment |\n\n## Workflow\n\n### Step 1: Configure Patch Sources\n\n```bash\n# WSUS (Windows Server Update Services)\n# Configure WSUS server to sync with Microsoft Update\n# Via PowerShell on WSUS server:\nInstall-WindowsFeature -Name UpdateServices -IncludeManagementTools\n& \"C:\\Program Files\\Update Services\\Tools\\WsusUtil.exe\" postinstall CONTENT_DIR=D:\\WSUS\n\n# Configure GPO for WSUS clients\n# Computer Configuration > Administrative Templates > Windows Components > Windows Update\n# Specify intranet Microsoft update service location: http:\u002F\u002Fwsus-server:8530\n```\n\n```yaml\n# Ansible: Configure patch repositories for Linux\n# roles\u002Fpatch-management\u002Ftasks\u002Fconfigure_repos.yml\n---\n- name: Configure RHEL patch repository\n  yum_repository:\n    name: rhel-patches\n    description: RHEL Security Patches\n    baseurl: https:\u002F\u002Fsatellite.corp.local\u002Fpulp\u002Frepos\u002Fpatches\n    gpgcheck: yes\n    gpgkey: file:\u002F\u002F\u002Fetc\u002Fpki\u002Frpm-gpg\u002FRPM-GPG-KEY-redhat-release\n    enabled: yes\n\n- name: Configure Ubuntu patch sources\n  apt_repository:\n    repo: \"deb https:\u002F\u002Fapt-mirror.corp.local\u002Fubuntu {{ ansible_distribution_release }}-security main\"\n    state: present\n  when: ansible_os_family == \"Debian\"\n```\n\n### Step 2: Automated Patch Assessment\n\n```python\n# patch_assessment.py - Correlate vulnerability scans with available patches\nimport subprocess\nimport platform\nimport json\n\ndef get_windows_pending_patches():\n    \"\"\"Query Windows Update for pending patches via PowerShell.\"\"\"\n    ps_cmd = \"\"\"\n    $Session = New-Object -ComObject Microsoft.Update.Session\n    $Searcher = $Session.CreateUpdateSearcher()\n    $Results = $Searcher.Search(\"IsInstalled=0 AND Type='Software'\")\n    $Results.Updates | ForEach-Object {\n        [PSCustomObject]@{\n            Title = $_.Title\n            KB = ($_.KBArticleIDs -join ',')\n            Severity = $_.MsrcSeverity\n            Size = [math]::Round($_.MaxDownloadSize \u002F 1MB, 2)\n            Published = $_.LastDeploymentChangeTime.ToString('yyyy-MM-dd')\n            CVE = ($_.CveIDs -join ',')\n        }\n    } | ConvertTo-Json\n    \"\"\"\n    result = subprocess.run(\n        [\"powershell\", \"-Command\", ps_cmd],\n        capture_output=True, text=True, timeout=120\n    )\n    return json.loads(result.stdout) if result.stdout.strip() else []\n\ndef get_linux_pending_patches():\n    \"\"\"Query package manager for available security updates.\"\"\"\n    if platform.system() != \"Linux\":\n        return []\n\n    # Try apt (Debian\u002FUbuntu)\n    try:\n        result = subprocess.run(\n            [\"apt\", \"list\", \"--upgradable\"],\n            capture_output=True, text=True, timeout=60\n        )\n        packages = []\n        for line in result.stdout.strip().split(\"\\n\")[1:]:\n            if line:\n                parts = line.split(\"\u002F\")\n                packages.append({\n                    \"package\": parts[0],\n                    \"available_version\": parts[1].split()[0] if len(parts) > 1 else \"\",\n                    \"source\": \"apt\"\n                })\n        return packages\n    except FileNotFoundError:\n        pass\n\n    # Try yum\u002Fdnf (RHEL\u002FCentOS)\n    try:\n        result = subprocess.run(\n            [\"dnf\", \"updateinfo\", \"list\", \"security\", \"--available\"],\n            capture_output=True, text=True, timeout=60\n        )\n        packages = []\n        for line in result.stdout.strip().split(\"\\n\"):\n            parts = line.split()\n            if len(parts) >= 3:\n                packages.append({\n                    \"advisory\": parts[0],\n                    \"severity\": parts[1],\n                    \"package\": parts[2],\n                    \"source\": \"dnf\"\n                })\n        return packages\n    except FileNotFoundError:\n        return []\n```\n\n### Step 3: Patch Testing Automation\n\n```yaml\n# Ansible playbook: test_patches.yml\n---\n- name: Test Patches in Lab Environment\n  hosts: test_servers\n  become: yes\n  vars:\n    rollback_snapshot: \"pre-patch-{{ ansible_date_time.date }}\"\n\n  tasks:\n    - name: Create VM snapshot before patching\n      community.vmware.vmware_guest_snapshot:\n        hostname: \"{{ vcenter_host }}\"\n        username: \"{{ vcenter_user }}\"\n        password: \"{{ vcenter_pass }}\"\n        datacenter: \"{{ datacenter }}\"\n        name: \"{{ inventory_hostname }}\"\n        snapshot_name: \"{{ rollback_snapshot }}\"\n        state: present\n      delegate_to: localhost\n\n    - name: Apply security patches (RHEL\u002FCentOS)\n      dnf:\n        name: \"*\"\n        state: latest\n        security: yes\n        update_cache: yes\n      when: ansible_os_family == \"RedHat\"\n      register: patch_result\n\n    - name: Apply security patches (Ubuntu\u002FDebian)\n      apt:\n        upgrade: dist\n        update_cache: yes\n        only_upgrade: yes\n      when: ansible_os_family == \"Debian\"\n      register: patch_result\n\n    - name: Reboot if required\n      reboot:\n        reboot_timeout: 600\n        msg: \"Rebooting for patch installation\"\n      when: patch_result.changed\n\n    - name: Run post-patch validation\n      include_tasks: validate_services.yml\n\n    - name: Report patch results\n      debug:\n        msg: \"Patching {{ 'succeeded' if patch_result.changed else 'no updates' }} on {{ inventory_hostname }}\"\n```\n\n### Step 4: Production Deployment\n\n```yaml\n# deploy_patches.yml - Phased production rollout\n---\n- name: Ring 1 - IT Early Adopters\n  hosts: ring1_hosts\n  serial: \"25%\"\n  max_fail_percentage: 10\n  become: yes\n  tasks:\n    - import_tasks: apply_patches.yml\n    - import_tasks: validate_services.yml\n    - name: Wait for soak period\n      pause:\n        hours: 48\n      run_once: true\n\n- name: Ring 2 - Business Pilot\n  hosts: ring2_hosts\n  serial: \"20%\"\n  max_fail_percentage: 5\n  become: yes\n  tasks:\n    - import_tasks: apply_patches.yml\n    - import_tasks: validate_services.yml\n\n- name: Ring 3 - General Deployment\n  hosts: ring3_hosts\n  serial: \"10%\"\n  max_fail_percentage: 3\n  become: yes\n  tasks:\n    - import_tasks: apply_patches.yml\n    - import_tasks: validate_services.yml\n```\n\n### Step 5: Verification and Reporting\n\nRun a post-patch vulnerability scan to confirm patch installation:\n```bash\n# Trigger post-patch verification scan\ncurl -k -X POST \"https:\u002F\u002Fnessus:8834\u002Fscans\u002F$VERIFY_SCAN_ID\u002Flaunch\" \\\n  -H \"X-Cookie: token=$TOKEN\"\n\n# Compare pre-patch and post-patch results\n# Expecting reduction in vulnerabilities matching deployed patches\n```\n\n## Patch Management SLAs\n| Severity | SLA (Internet-Facing) | SLA (Internal) | SLA (Air-Gapped) |\n|----------|----------------------|----------------|-------------------|\n| Critical (CVSS 9+) | 48 hours | 7 days | 14 days |\n| High (CVSS 7-8.9) | 7 days | 14 days | 30 days |\n| Medium (CVSS 4-6.9) | 30 days | 30 days | 60 days |\n| Low (CVSS 0.1-3.9) | 90 days | 90 days | 90 days |\n\n## Best Practices\n1. Maintain current asset inventory to ensure complete patch coverage\n2. Test all patches in a non-production environment before deployment\n3. Use phased rollouts with automatic rollback capabilities\n4. Coordinate patch windows with change management process\n5. Track patch compliance metrics and report to leadership\n6. Automate where possible to reduce manual effort and human error\n7. Maintain exception documentation for systems that cannot be patched\n8. Include third-party application patching (not just OS patches)\n\n## Common Pitfalls\n- Patching only operating systems and ignoring third-party applications\n- No rollback plan if patches cause service disruption\n- Treating all patches with equal urgency (no risk-based prioritization)\n- Manual patch processes that cannot scale\n- No post-patch verification to confirm successful installation\n- Ignoring firmware and BIOS updates\n\n## Related Skills\n- prioritizing-vulnerabilities-with-cvss-scoring\n- implementing-vulnerability-remediation-sla\n- implementing-continuous-vulnerability-monitoring\n","# Implementing Patch Management Workflow\n\n## Overview\nPatch 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.\n\n\n## When to Use\n\n- When deploying or configuring implementing patch management workflow capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Vulnerability scan results identifying missing patches\n- Patch management tools (WSUS, SCCM\u002FMECM, Ansible, Intune, Jamf)\n- Test environment mirroring production\n- Change management process (ITIL or equivalent)\n- Asset inventory with OS and application versions\n\n## Core Concepts\n\n### Patch Lifecycle Phases\n1. **Discovery**: Identify available patches from vendors and vulnerability scans\n2. **Assessment**: Evaluate patch applicability and risk\n3. **Prioritization**: Rank patches by severity, exploitability, and asset criticality\n4. **Testing**: Validate patches in non-production environment\n5. **Approval**: Change advisory board (CAB) review and approval\n6. **Deployment**: Phased rollout to production systems\n7. **Verification**: Confirm successful installation and no regressions\n8. **Reporting**: Document compliance metrics and exceptions\n\n### Patch Categories\n- **Security Patches**: Address CVEs and security vulnerabilities\n- **Critical Updates**: Non-security bug fixes affecting stability\n- **Service Packs**: Cumulative update collections\n- **Feature Updates**: New functionality (Windows feature updates, etc.)\n- **Firmware Updates**: BIOS\u002FUEFI, NIC, storage controller firmware\n- **Third-Party Patches**: Adobe, Java, Chrome, Firefox, etc.\n\n### Deployment Rings (Phased Rollout)\n| Ring | Environment | % of Fleet | Soak Time | Purpose |\n|------|------------|------------|-----------|---------|\n| Ring 0 | Lab\u002FTest | N\u002FA | 24-48 hrs | Functional validation |\n| Ring 1 | IT Early Adopters | 5% | 48-72 hrs | Real-world pilot |\n| Ring 2 | Business Pilot | 15% | 5-7 days | Broader compatibility |\n| Ring 3 | General Deployment | 50% | 7-14 days | Main rollout |\n| Ring 4 | Mission Critical | 30% | After Ring 3 | Final deployment |\n\n## Workflow\n\n### Step 1: Configure Patch Sources\n\n```bash\n# WSUS (Windows Server Update Services)\n# Configure WSUS server to sync with Microsoft Update\n# Via PowerShell on WSUS server:\nInstall-WindowsFeature -Name UpdateServices -IncludeManagementTools\n& \"C:\\Program Files\\Update Services\\Tools\\WsusUtil.exe\" postinstall CONTENT_DIR=D:\\WSUS\n\n# Configure GPO for WSUS clients\n# Computer Configuration > Administrative Templates > Windows Components > Windows Update\n# Specify intranet Microsoft update service location: http:\u002F\u002Fwsus-server:8530\n```\n\n```yaml\n# Ansible: Configure patch repositories for Linux\n# roles\u002Fpatch-management\u002Ftasks\u002Fconfigure_repos.yml\n---\n- name: Configure RHEL patch repository\n  yum_repository:\n    name: rhel-patches\n    description: RHEL Security Patches\n    baseurl: https:\u002F\u002Fsatellite.corp.local\u002Fpulp\u002Frepos\u002Fpatches\n    gpgcheck: yes\n    gpgkey: file:\u002F\u002F\u002Fetc\u002Fpki\u002Frpm-gpg\u002FRPM-GPG-KEY-redhat-release\n    enabled: yes\n\n- name: Configure Ubuntu patch sources\n  apt_repository:\n    repo: \"deb https:\u002F\u002Fapt-mirror.corp.local\u002Fubuntu {{ ansible_distribution_release }}-security main\"\n    state: present\n  when: ansible_os_family == \"Debian\"\n```\n\n### Step 2: Automated Patch Assessment\n\n```python\n# patch_assessment.py - Correlate vulnerability scans with available patches\nimport subprocess\nimport platform\nimport json\n\ndef get_windows_pending_patches():\n    \"\"\"Query Windows Update for pending patches via PowerShell.\"\"\"\n    ps_cmd = \"\"\"\n    $Session = New-Object -ComObject Microsoft.Update.Session\n    $Searcher = $Session.CreateUpdateSearcher()\n    $Results = $Searcher.Search(\"IsInstalled=0 AND Type='Software'\")\n    $Results.Updates | ForEach-Object {\n        [PSCustomObject]@{\n            Title = $_.Title\n            KB = ($_.KBArticleIDs -join ',')\n            Severity = $_.MsrcSeverity\n            Size = [math]::Round($_.MaxDownloadSize \u002F 1MB, 2)\n            Published = $_.LastDeploymentChangeTime.ToString('yyyy-MM-dd')\n            CVE = ($_.CveIDs -join ',')\n        }\n    } | ConvertTo-Json\n    \"\"\"\n    result = subprocess.run(\n        [\"powershell\", \"-Command\", ps_cmd],\n        capture_output=True, text=True, timeout=120\n    )\n    return json.loads(result.stdout) if result.stdout.strip() else []\n\ndef get_linux_pending_patches():\n    \"\"\"Query package manager for available security updates.\"\"\"\n    if platform.system() != \"Linux\":\n        return []\n\n    # Try apt (Debian\u002FUbuntu)\n    try:\n        result = subprocess.run(\n            [\"apt\", \"list\", \"--upgradable\"],\n            capture_output=True, text=True, timeout=60\n        )\n        packages = []\n        for line in result.stdout.strip().split(\"\\n\")[1:]:\n            if line:\n                parts = line.split(\"\u002F\")\n                packages.append({\n                    \"package\": parts[0],\n                    \"available_version\": parts[1].split()[0] if len(parts) > 1 else \"\",\n                    \"source\": \"apt\"\n                })\n        return packages\n    except FileNotFoundError:\n        pass\n\n    # Try yum\u002Fdnf (RHEL\u002FCentOS)\n    try:\n        result = subprocess.run(\n            [\"dnf\", \"updateinfo\", \"list\", \"security\", \"--available\"],\n            capture_output=True, text=True, timeout=60\n        )\n        packages = []\n        for line in result.stdout.strip().split(\"\\n\"):\n            parts = line.split()\n            if len(parts) >= 3:\n                packages.append({\n                    \"advisory\": parts[0],\n                    \"severity\": parts[1],\n                    \"package\": parts[2],\n                    \"source\": \"dnf\"\n                })\n        return packages\n    except FileNotFoundError:\n        return []\n```\n\n### Step 3: Patch Testing Automation\n\n```yaml\n# Ansible playbook: test_patches.yml\n---\n- name: Test Patches in Lab Environment\n  hosts: test_servers\n  become: yes\n  vars:\n    rollback_snapshot: \"pre-patch-{{ ansible_date_time.date }}\"\n\n  tasks:\n    - name: Create VM snapshot before patching\n      community.vmware.vmware_guest_snapshot:\n        hostname: \"{{ vcenter_host }}\"\n        username: \"{{ vcenter_user }}\"\n        password: \"{{ vcenter_pass }}\"\n        datacenter: \"{{ datacenter }}\"\n        name: \"{{ inventory_hostname }}\"\n        snapshot_name: \"{{ rollback_snapshot }}\"\n        state: present\n      delegate_to: localhost\n\n    - name: Apply security patches (RHEL\u002FCentOS)\n      dnf:\n        name: \"*\"\n        state: latest\n        security: yes\n        update_cache: yes\n      when: ansible_os_family == \"RedHat\"\n      register: patch_result\n\n    - name: Apply security patches (Ubuntu\u002FDebian)\n      apt:\n        upgrade: dist\n        update_cache: yes\n        only_upgrade: yes\n      when: ansible_os_family == \"Debian\"\n      register: patch_result\n\n    - name: Reboot if required\n      reboot:\n        reboot_timeout: 600\n        msg: \"Rebooting for patch installation\"\n      when: patch_result.changed\n\n    - name: Run post-patch validation\n      include_tasks: validate_services.yml\n\n    - name: Report patch results\n      debug:\n        msg: \"Patching {{ 'succeeded' if patch_result.changed else 'no updates' }} on {{ inventory_hostname }}\"\n```\n\n### Step 4: Production Deployment\n\n```yaml\n# deploy_patches.yml - Phased production rollout\n---\n- name: Ring 1 - IT Early Adopters\n  hosts: ring1_hosts\n  serial: \"25%\"\n  max_fail_percentage: 10\n  become: yes\n  tasks:\n    - import_tasks: apply_patches.yml\n    - import_tasks: validate_services.yml\n    - name: Wait for soak period\n      pause:\n        hours: 48\n      run_once: true\n\n- name: Ring 2 - Business Pilot\n  hosts: ring2_hosts\n  serial: \"20%\"\n  max_fail_percentage: 5\n  become: yes\n  tasks:\n    - import_tasks: apply_patches.yml\n    - import_tasks: validate_services.yml\n\n- name: Ring 3 - General Deployment\n  hosts: ring3_hosts\n  serial: \"10%\"\n  max_fail_percentage: 3\n  become: yes\n  tasks:\n    - import_tasks: apply_patches.yml\n    - import_tasks: validate_services.yml\n```\n\n### Step 5: Verification and Reporting\n\nRun a post-patch vulnerability scan to confirm patch installation:\n```bash\n# Trigger post-patch verification scan\ncurl -k -X POST \"https:\u002F\u002Fnessus:8834\u002Fscans\u002F$VERIFY_SCAN_ID\u002Flaunch\" \\\n  -H \"X-Cookie: token=$TOKEN\"\n\n# Compare pre-patch and post-patch results\n# Expecting reduction in vulnerabilities matching deployed patches\n```\n\n## Patch Management SLAs\n| Severity | SLA (Internet-Facing) | SLA (Internal) | SLA (Air-Gapped) |\n|----------|----------------------|----------------|-------------------|\n| Critical (CVSS 9+) | 48 hours | 7 days | 14 days |\n| High (CVSS 7-8.9) | 7 days | 14 days | 30 days |\n| Medium (CVSS 4-6.9) | 30 days | 30 days | 60 days |\n| Low (CVSS 0.1-3.9) | 90 days | 90 days | 90 days |\n\n## Best Practices\n1. Maintain current asset inventory to ensure complete patch coverage\n2. Test all patches in a non-production environment before deployment\n3. Use phased rollouts with automatic rollback capabilities\n4. Coordinate patch windows with change management process\n5. Track patch compliance metrics and report to leadership\n6. Automate where possible to reduce manual effort and human error\n7. Maintain exception documentation for systems that cannot be patched\n8. Include third-party application patching (not just OS patches)\n\n## Common Pitfalls\n- Patching only operating systems and ignoring third-party applications\n- No rollback plan if patches cause service disruption\n- Treating all patches with equal urgency (no risk-based prioritization)\n- Manual patch processes that cannot scale\n- No post-patch verification to confirm successful installation\n- Ignoring firmware and BIOS updates\n\n## Related Skills\n- prioritizing-vulnerabilities-with-cvss-scoring\n- implementing-vulnerability-remediation-sla\n- implementing-continuous-vulnerability-monitoring\n",{"name":5,"tags":52,"author":53,"domain":46,"license":15,"version":54,"nist_csf":55,"subdomain":41,"description":7,"mitre_attack":60},[41,44,43,42,39,40],"mahipal","1.0",[56,57,58,59],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06",[61,62,63],"T1190","T1203","T1068","main","7925716f065257435fdb12e97f7e52842147d5ad",".claude\u002Fskills\u002Fimplementing-patch-management-workflow","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude","https:\u002F\u002Fclaude.com\u002Fclaude-code","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho","Software · Applied AI · Quantitative Modeling · Building with Claude.","2026-06-10 12:24:46",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add henriquescastilho\u002Fmy-claude --skill implementing-patch-management-workflow",{"tool":78,"command":79},"bunx","bunx skills add henriquescastilho\u002Fmy-claude --skill implementing-patch-management-workflow",{"tool":81,"command":82},"pnpm","pnpm dlx skills add henriquescastilho\u002Fmy-claude --skill implementing-patch-management-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-patch-management-workflow\u002FSKILL.md",true,[86,92,97,103,107,111,117],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"assets\u002Ftemplate.md","ASSET","资产文件",1164,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-patch-management-workflow\u002Fassets\u002Ftemplate.md",{"path":93,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-patch-management-workflow\u002FLICENSE",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fapi-reference.md","REFERENCE","参考文档",4567,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-patch-management-workflow\u002Freferences\u002Fapi-reference.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fstandards.md",1499,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-patch-management-workflow\u002Freferences\u002Fstandards.md",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fworkflows.md",2455,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-patch-management-workflow\u002Freferences\u002Fworkflows.md",{"path":112,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":115,"sourceHtmlUrl":116},"scripts\u002Fagent.py","SCRIPT","脚本",9788,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-patch-management-workflow\u002Fscripts\u002Fagent.py",{"path":118,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":119,"sourceHtmlUrl":120},"scripts\u002Fprocess.py",14037,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-patch-management-workflow\u002Fscripts\u002Fprocess.py",[122,163,172,181,203,229],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":143,"publishedAt":47},"01M6F0B6XPQ65AX2X0DWK8KT3E","markitdown","Convert files and office documents to Markdown. Supports PDF, DOCX, PPTX, XLSX, images (with OCR), audio (with transcription), HTML, CSV, JSON, XML, ZIP, YouTube URLs, EPubs and more.","MIT","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-writer\u002Fskills\u002Fmarkitdown\u002FSKILL.md",[129,132,135,138],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[124,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162],"docx","PDF","pptx","xlsx","documents","csv","ocr","Audio","Bash","markdown","convert","read","write","edit","html","images","files","youtube","with",{"skillNo":164,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":171,"publishedAt":47},"01M6F06SBHR9F0SDWE282Y8075","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-writer\u002Fscientific_writer\u002F.claude\u002Fskills\u002Fmarkitdown\u002FSKILL.md",[167,168,169,170],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},[124,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162],{"skillNo":173,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":180,"publishedAt":47},"01M6F02D4R14EJAPBWVDF9J9VQ","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-writer\u002F.claude\u002Fskills\u002Fmarkitdown\u002FSKILL.md",[176,177,178,179],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},[124,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162],{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":47},"01M6F000KS6YB4MKS774G4R8ND","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-skills\u002Fscientific-skills\u002Fzarr-python\u002FSKILL.md",[],[188,189,190,191,192,193,194,195,196,197,198,199,200,201,202],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":47},"01M6EZZJWFXM1GR78KTW6J0DN8","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-skills\u002Fscientific-skills\u002Fwhat-if-oracle\u002FSKILL.md",[209],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[211,212,213,214,215,216,217,218,219,220,221,155,156,222,223,224,225,226,227,228],"oracle","what if oracle","go","run","ux","futures","analysis","explore","decision","branch","question","idea","exploration","options","stress-test","strategies","scenario","stress",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":245,"publishedAt":47},"01M6EZZCXAEB49RXGQCJX5E8GB","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-skills\u002Fscientific-skills\u002Fvenue-templates\u002FSKILL.md",[235,238,241,242],{"categoryNo":236,"categoryName":237,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":239,"categoryName":240,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":243,"categoryName":244,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000036","内容创作者",[246,247,248,249,250,251,252,253,152,254,155,156,157,255,256,257,258,259,202,260],"templates","venue templates","research","guidelines","NeurIPS","ICML","LaTeX","science","access","proposals","Academic","requirements","formatting","journal","chi"]