Performing Endpoint Vulnerability Remediation
Overview
Cybersecurity skill for performing endpoint vulnerability remediation. Follows industry best practices and security standards.
When to Use
Trigger phrases:
- "performing endpoint vulnerability remediation"
- "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"
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).
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
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
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Plan Operations — Define objectives, scope, and success criteria for endpoint vulnerability remediation operations.
- Prepare Environment — Set up tools, access, and data sources required for endpoint vulnerability remediation.
- Execute Core Workflow — Perform the endpoint vulnerability remediation operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: performing-endpoint-vulnerability-remediation3description: Use when 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.4license: Apache-2.05---67# Performing Endpoint Vulnerability Remediation89## Overview1011Cybersecurity skill for performing endpoint vulnerability remediation. Follows industry best practices and security standards.1213## When to Use1415**Trigger phrases:**16- "performing endpoint vulnerability remediation"17- "Remediating vulnerabilities identified by scanners (Nessus, Qualys, Rapid7)"18- "Responding to zero-day CVE advisories requiring immediate patching"19- "Maintaining compliance with patch management SLAs (critical within 14 days, high"202122Use this skill when:23- Remediating vulnerabilities identified by scanners (Nessus, Qualys, Rapid7)24- Responding to zero-day CVE advisories requiring immediate patching25- Maintaining compliance with patch management SLAs (critical within 14 days, high within 30 days)26- Building a prioritized remediation plan from vulnerability scan results2728**Do not use** this skill for vulnerability scanning itself (use scanning tools) or for application-layer vulnerability remediation (use DevSecOps processes).293031## When NOT to Use3233- When you lack proper authorization for testing34- For production systems without change management35- When the task requires legal or compliance expertise beyond technical scope363738## Prerequisites3940- Vulnerability scan results (Nessus, Qualys, or Rapid7 export in CSV/XML format)41- Patch management platform (WSUS, SCCM, Intune, or third-party like Automox)42- Administrative access to target endpoints or deployment infrastructure43- Change management process for production endpoint patching44- Testing environment for patch validation before production rollout4546## Workflow4748```python49# Example: IOC detection50import re5152IOC_PATTERNS = {53 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",54 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",55 "hash_md5": r"\b[a-f0-9]{32}\b",56 "hash_sha256": r"\b[a-f0-9]{64}\b",57}5859def extract_iocs(text: str) -> dict:60 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}61```62631. **Plan Operations** — Define objectives, scope, and success criteria for endpoint vulnerability remediation operations.642. **Prepare Environment** — Set up tools, access, and data sources required for endpoint vulnerability remediation.653. **Execute Core Workflow** — Perform the endpoint vulnerability remediation operations following established procedures.664. **Validate Results** — Verify that results meet quality standards and objectives.675. **Report Findings** — Document results, observations, and recommendations.686. **Follow Up** — Track remediation actions and verify fixes where applicable.6970## Tools7172- **Analysis Platform** — Data processing and visualization73- **Collaboration Tools** — Team coordination and knowledge sharing747576## Process77781. **Reconnaissance** — Gather target information, identify attack surface, enumerate services791. **Analysis/Exploitation** — Execute the technique, analyze results, document findings801. **Reporting** — Document IOCs, write findings, provide remediation recommendations8182## Verification8384- [ ] All endpoint vulnerability remediation procedures executed completely and documented85- [ ] Findings validated against multiple data sources86- [ ] False positives identified and filtered87- [ ] Results documented with evidence and timestamps88- [ ] Recommendations provided with risk-based prioritization8990## Anti-Rationalization Table9192| Rationalization | Reality |93|---|---|94| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |95| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |96| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |