it-vulnerability-compliance

Validates vulnerability findings and produces audit-ready remediation and compliance evidence records.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/lwokeray/cowork-plugins --skill it-vulnerability-compliance-lwokeray
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: it-vulnerability-compliance
Source: https://github.com/lwokeray/cowork-plugins/tree/main/plugins/it-operations-cowork/skills/it-vulnerability-compliance
Command: npx skills add https://github.com/lwokeray/cowork-plugins --skill it-vulnerability-compliance-lwokeray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security teams receive scanner findings and audit requests that mix confirmed risks, false positives, and stale data, making it hard to decide what to fix, what to accept, and how to prove closure. This Skill turns raw scanner and audit claims into validated, owned risk decisions with verifiable evidence. ## Core Features & Use Cases - Finding Validation: Confirm asset scope, affected versions, exposure, and exploitability before classifying findings as confirmed, not applicable, mitigated, false positive, or needs review. - Remediation Planning: Build fix plans with dependencies, rollback, pilot waves, verification tests, owners, and due conditions—without assuming patch success equals closure. - Exception & Compliance Management: Create time-bound risk exceptions with compensating controls and map audit evidence to requested controls without overclaiming certification. - Use Case: A scanner flags a CVE on a production server. Use this Skill to verify the affected version is actually present, assess real exploitability, plan the patch rollout with rollback, and define the exact evidence needed to close the finding. ## Quick Start Validate this vulnerability scan finding for our production web servers and produce a remediation plan with verification evidence and owner assignments.

Frequently Asked Questions about it-vulnerability-compliance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a vulnerability scan finding before remediation?▼

Confirm the asset exists and is in scope, verify the affected component or version is present, then assess exposure, required privileges, and compensating controls. Classify the finding as confirmed, not applicable, mitigated, false positive, or needs review with supporting evidence.

How do I prioritize vulnerability remediation beyond scanner severity?▼

Assign risk using exploitability, exposure, privilege requirements, business impact, asset criticality, and existing control strength rather than scanner severity alone. Then select remediation, mitigation, isolation, or a time-bound exception based on that assessment.

Why does a finding remain open after the patch is installed?▼

Patch installation success does not prove the vulnerable runtime, configuration, package, image, or service instance is remediated. Check the running version, required restarts, duplicate instances, and scan freshness before closing the finding.

What makes a valid risk exception for a vulnerability?▼

A valid exception requires a confirmed risk and scope, a business reason remediation cannot occur now, a named risk owner and approver, compensating controls with evidence, residual risk, an expiry date, and a planned remediation path. Indefinite exceptions are not allowed.

What evidence should I provide for a compliance audit?▼

Map current configuration, logs, tickets, approvals, and test results to the requested policy or control, recording source, collection time, scope, and owner. Distinguish design evidence from operating evidence and record control failures openly without claiming certification.