Securin remediation guidance
Skill securin-public/securin-skills/skills/securin-remediation-guidance
Use this skill when the user asks "how do I fix this exposure", "remediate this vulnerability", "what's the fix for...", "patch guidance for CVE-XXX", "workaround for this vuln", or needs an actionable fix plan for a specific exposure or CVE. The skill reads remediation, solution, and patch fields already populated in the platform (built-in, mapped, or scanner-provided) first, and only offers a web-search enrichment after user confirmation. For prioritization across many exposures use securin-exposure-triage; for global CVE intel use securin-cve-enrichment. Requires the Securin Platform MCP server.From its SKILL.md
npx -y skills add securin-public/securin-skills --skill securin-remediation-guidanceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
12.7 KB, as published. Nobody here has run it
Remediation Guidance
Purpose
Produce an actionable fix plan for a specific exposure or CVE — drawn primarily from the platform's own remediation content (built-in fields, mapped attributes, scanner-native fields). Web search is an opt-in enrichment, not a default step.
When to use
- "How do I fix CVE-2024-3400?"
- "Remediate exposure
exp-abc123" - "Patch guidance for log4j"
- "What's the workaround while we can't patch?"
- "Compensating controls for this vuln"
- "Generate a ticket body for this exposure"
Pre-flight
Step 0 — Account preflight (CC-1)
See _shared/account-preflight.md. Required — remediation plans read the user's exposure records.
Before using this skill, read every file in the references folder, including the shared references/_shared/ docs.
Suggested tools
Pre-flight (CC-1, see shared doc)
getUserProfile— resolve caller's accessible accounts + user-idgetEffectiveAccess/getEffectiveAccessWorkspaces— per-resource access when needed
Read remediation content (primary)
searchExposureData(source) orexposureQuery(composite) — exposure records; this is where most remediation content lives, underexposure.mappedAttributes.*/compositeExposure.sources.mappedAttributes.*or scanner-specific fieldssearchVulnerabilityData— CVE record with fixed-in version and vendor references (when available)searchAssetData(source) orassetQuery(composite) — asset platform context (OS, version) so the fix advice is relevantsearchComponentData— installed component / package version (for package-manager style remediation)getApiFields(entityType=['EXPOSURE'], searchText='remediation')— discover all remediation-bearing fields for this accountgetApiFields(entityType=['EXPOSURE'], searchText='solution')— same for scanner-nativesolutionfieldsgetApiFields(entityType=['EXPOSURE'], searchText='patch')/'fix'— same for patch / fix-info fields
Integrations / actions
getConfiguredIntegrations— call early. Returns every configured scanner + ticketing integration withid,name,vendorName,type(SCANNER/TICKETING), andprefix(e.g.WIZ,Q-VMDR,NESSUS,SNYK,SERVICE_NOW_INCIDENT). Two uses:- Find scanner-specific remediation fields. The
prefixmaps to an integration-specific field group — pass it asfetchGroupstogetApiFields(entityType=['EXPOSURE'])to retrieve that integration's remediation/solution/advisory fields (e.g., Qualyssolution, Tenablesolution, Rapid7solution). Scanner-native fields often have richer vendor advisory text than the genericexposure.mappedAttributes.vendorRemediation. - Detect ticketing handoff options. Filter
type = 'TICKETING'to find Jira / ServiceNow / ServiceNow_Incident integrations for draft ticket output.
- Find scanner-specific remediation fields. The
Deep links (CC-2)
- See _shared/deep-links.md. Call
createDeepLinkfor every list or table of exposure / asset records you surface. Skip only for single-record drilldowns and purely conceptual responses (no customer data list). Do not fabricate or omit links for list responses.
Opt-in enrichment (after user confirms)
- Web search — vendor advisory, KB article, community workarounds. Do not run by default.
Workflow
Step 1 — Identify the subject
- Exposure-id → fetch the single exposure record.
- CVE → fetch all matching exposures in the account scope (filter
exposure.mappedAttributes.vulnerabilityIds = 'CVE-X' AND exposure.status = 'Open'). If many, ask the user whether to plan for all, a subset, or give a CVE-level summary. - Vulnerability name (no CVE) → resolve via
searchVulnerabilityDataon name/aliases; confirm with the user.
Step 2 — Read platform remediation fields first
Fetch the exposure(s) with searchExposureData. Always include at minimum:
"fields": [
"exposure.exposureId",
"exposure.title",
"exposure.scores.scoreLevel",
"exposure.scores.score",
"exposure.mappedAttributes.vulnerabilityIds",
"exposure.mappedAttributes.vendorRemediation",
"exposure.remediationTarget.status",
"exposure.remediationTarget.dueDate",
"exposure.remediationTarget.priority",
"asset.criticality",
"asset.reachability"
]
For richer coverage (account-specific integration fields), pre-discover via getApiFields(entityType=['EXPOSURE'], searchText='remediation') and append matched apiPaths.
The canonical field :
| Field | Notes |
|---|---|
exposure.mappedAttributes.vendorRemediation | Primary source of scanner-provided remediation text. Always request this field first. Example real value: (example: a vendor advisory patch instruction) |
genericExposure.vulnerability.attributes.vendorRemediation | Alternate path on generic-connector exposures |
Secondary / structured remediation fields (also populated on most accounts):
| Field | Type | Use |
|---|---|---|
exposure.remediationTarget.status | enum On Track / Overdue / Met / Missed | SLA state |
exposure.remediationTarget.dueDate | date | Due date |
exposure.remediationTarget.priority | string (P1, P2, …) | Priority band |
exposure.remediationTarget.targetDays | integer | SLA target window |
exposure.scores.remediationScore | number | Platform-computed remediation urgency |
Account-specific integration fields may exist (Qualys, Tenable, CrowdStrike, Rapid7 — discover via getApiFields(entityType=['EXPOSURE'], searchText='remediation')). Present whatever is populated, clearly labeled with the source field.
Step 3 — Enrich with asset + vulnerability context, and discover scanner-native remediation
Run in parallel:
-
searchAssetData(or composite) to get the affected asset's OS, version, criticality, reachability. -
searchVulnerabilityDatafor the CVE record if not already fetched — confirm severity, KEV, exploit status. -
getConfiguredIntegrations— critical step. From the response, identify which SCANNER integration produced the exposure (match the exposure's scanner source to an integration'sprefix). Then call:getApiFields(entityType=['EXPOSURE'], fetchGroups='<PREFIX>', searchText='remediation') getApiFields(entityType=['EXPOSURE'], fetchGroups='<PREFIX>', searchText='solution') getApiFields(entityType=['EXPOSURE'], fetchGroups='<PREFIX>', searchText='fix')to enumerate that scanner's remediation/solution/fix fields. Add those paths to your
searchExposureDatafieldsarray to pull the scanner-native remediation text. Common integrations and their typical remediation fields:- Qualys VMDR/EASM (
Q-VMDR,Q-EASM,Q-PC,Q-WAS) —solutionfield - Tenable Nessus / IO / SC (
NESSUS,TIO_QA,TSC) —solutionfield - Rapid7 InsightVM / Nexpose (
IVM,IVM_CLOUD,NEXPOSES) —solutionfield - WIZ (
WIZ) — remediation steps in the finding record - CrowdStrike Falcon Spotlight (
FS) —remediationfield - Snyk (
SNYK) —fixedIn/remediation
Ticketing integrations (
type = 'TICKETING', e.g.SERVICE_NOW_INCIDENT) surface draft-ticket handoff options in Step 5. - Qualys VMDR/EASM (
Step 4 — Ask before web-searching
The platform remediation content is often sufficient. Before running web search, ask:
"I found remediation guidance in the platform (sources: <list>). Want me to also search vendor advisories / KBs on the web for more depth? (Y/n)"
If the user says yes, proceed to Step 5. If no, skip to Step 6.
Step 5 — (Opt-in) Web-search vendor advisories
Only when the user confirmed. Search for:
- The official vendor advisory for the CVE.
- KB article or release notes for the fixed version.
- Known workarounds / compensating controls.
Read the content — do not just link. Quote the specific steps. See references/patch-lookup-patterns.md.
Step 6 — Construct the fix plan
Organize findings into this structure. Fields you couldn't populate (because the platform didn't have them and web search was declined) are explicitly marked "not available".
## Remediation Plan — <CVE or exposure id>
**Subject:** <CVE> on <asset hostname>
**Severity:** <Critical/High/Medium/Low/Info> (KEV: yes/no, score: <exposure.scores.score>)
**Remediation status:** <On Track / Overdue / Met / Missed> (due <date>, priority <P1/P2/…>)
**Asset:** <hostname> — <OS + version>, criticality <numeric 1–5>, reachability <Exposed / NotExposed>
### Remediation guidance from the platform
_Source: `<field path>` (integration: `<name>`)_
> <quoted content>
_Source: `<another field>`_
> <quoted content>
### Fixed version (if known)
- <version> — source: `<field path>` or vendor advisory
### Workaround
- <quoted or "none documented in platform record">
### Compensating controls
- <quoted or "none documented; consider WAF / network segmentation">
### Pre-patch risk (from platform)
- Other open exposures on the same asset(s): <list or "none">
- Asset criticality: <>
- Reachability: <>
### Ticketing draft (copy-paste)
**Title:** Patch <CVE> on <asset>
**Body:**
> <all of the above, with platform deep link>
> — Drafted by Claude + securin-remediation-guidance. Create manually in your ticketing system (MCP M1 is read-only for write actions).
### Platform links
- Exposure record: <url>
- Vulnerability record: <url>
- All open exposures for this CVE in your account: <url>
### Additional web-sourced references (if the user opted in)
- Vendor advisory: <url> — quoted excerpt: <…>
- KB article: <url> — quoted excerpt: <…>
Handoff (draft, don't create)
If getConfiguredIntegrations shows a ticketing integration (Jira, ServiceNow) configured:
- Draft a ticket body suitable for copy-paste.
- Do not create the ticket. Write actions are out of scope for MCP Milestone 1.
See references/patch-lookup-patterns.md for platform-specific upgrade command templates and ticket boilerplate.
Edge cases
- Platform has zero remediation content for this exposure — tell the user explicitly. Offer web search as an opt-in.
- Exposure is a misconfiguration (no CVE) —
exposure.mappedAttributes.remediationor scanner-nativesolutionis usually the best source; skip CVE queries. - Multi-CVE exposure — pull remediation content per CVE; deduplicate if multiple CVEs share the same fix.
- True zero-day (no patch yet) — the platform likely has
vulnerabilities.tags = 'Zero Day'set; route viasecurin-zero-day-exposure-analysisfor compensating-controls guidance. - Asset is EOL — flag; upgrade may not be possible, recommend isolation / replacement.
Scope guard (CC-3)
- Global CVE intel (no specific fix plan) →
securin-cve-enrichment. - Prioritization across many exposures →
securin-exposure-triage. - "Am I affected by threat X" →
securin-threat-correlation. - Zero-day-specific analysis →
securin-zero-day-exposure-analysis. - Unknown platform capability → fall back to the platform's built-in
Securin__search_toolsmeta-tool to look up the right MCP tool by description.
Visual output (CC-4)
When this skill produces aggregated or multi-row data (counts, trends, distributions, comparisons, single-CVE reports), emit a chart/graph/infographic in the Securin brand palette (#712880 / #453983 / #542ade / #987bf7 / #d7cbfb), Lato font, light theme, with the Securin logo. Default colormap uses the monotone gradient defined in _shared/brand.md. Offer customization after delivery; never default to a different brand.
References
- Patch Lookup Patterns — platform upgrade-command templates, ticket boilerplate.
- Shared: Account Preflight
- Shared: Composite vs Source
- Shared: Deep Links
- Shared: FQL Grammar
- Shared: Sorting Rules
- Shared: Brand & Visual Communication