Receber por email
← Voltar para o catálogo

Blackpoint Vulnerability Management

Use esta skill para analisar dados de exposição da Blackpoint Cyber (CompassOne), incluindo vulnerabilidades de host, histórico de varredura, vazamentos na dark web e exposições externas na internet.

31estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add wyre-technology/msp-claude-plugins

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/blackpoint-vulnerability-management/svg)](https://www.skillteca.com.br/skills/blackpoint-vulnerability-management)

Skills relacionadas

Ver todas de Documentos →

Alerta por categoria

Receba novas skills de Documentos toda segunda

1 email curto, só com as skills novas de Documentos. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Blackpoint Vulnerability Management

CompassOne exposes four exposure lenses against a tenant's assets: host-level vulnerabilities, scan history, dark-web leaks, and internet-facing external exposures. This skill covers all four and how to combine them into a prioritized remediation view.

API Tools

| Tool | Purpose | |------|---------| | blackpoint_vulnerabilities_list | Host-level vulnerability findings | | blackpoint_vulnerabilities_scans_list | Vulnerability scan history and status | | blackpoint_vulnerabilities_darkweb_list | Dark-web exposures (leaked data) | | blackpoint_vulnerabilities_external_list | Internet-facing external exposures |

Filters That Matter

blackpoint_vulnerabilities_list accepts:

  • tenant_id, asset_id — scope
  • severity — low, medium, high, critical
  • status — open, fixed, ignored, false_positive
  • cve_id — pivot on a specific CVE
  • patch_available — is a fix published?
  • exploit_available — is it weaponized in the wild?

The fix-now cohort is the intersection: severity in {high, critical}, status: open, exploit_available: true, patch_available: true — a known, weaponized, fixable problem that has not been fixed.

blackpoint_vulnerabilities_darkweb_list exposure types: credentials, documents, data_breach, malware.

blackpoint_vulnerabilities_external_list exposure types: open_port, vulnerable_service, certificate_issue, misconfiguration.

blackpoint_vulnerabilities_scans_list status values: pending, running, completed, failed.

Common Workflows

Prioritized remediation list for a tenant

  1. Check blackpoint_vulnerabilities_scans_list — if the last

completed scan is stale or recent scans failed, say so; it caps confidence in everything below.

  1. Pull blackpoint_vulnerabilities_list for the tenant.
  2. Filter to the fix-now cohort and present it first.
  3. List remaining open criticals/highs (especially no-patch ones)

separately with a compensating-controls note.

Dark-web exposure check

  1. blackpoint_vulnerabilities_darkweb_list for the tenant.
  2. For credentials exposures, recommend forced password resets and

an MFA enforcement check.

  1. Flag data_breach and malware exposures for follow-up.

External attack-surface review

  1. blackpoint_vulnerabilities_external_list for the tenant.
  2. Group by exposure type; treat vulnerable_service and

open_port on management ports as highest priority.

  1. Pair with certificate_issue findings for a complete edge view.

Edge Cases

  • Stale scans — never present a vulnerability rollup without

checking scan recency first; old data misleads the reader.

  • No-patch criticals — separate these from the fix-now list;

they need compensating controls, not a patch ticket.

  • Read-only — remediation actions happen outside CompassOne;

the MCP cannot mark findings fixed.

Best Practices

  • Risk-weight, do not just severity-sort: exploitability and patch

availability change the priority order materially.

  • Combine all four lenses for QBRs — host, scan, dark-web, external

tell complementary stories.

  • Always cite CVE IDs and asset IDs so a finding can be re-pulled.

Related Skills

  • [incident-response](../incident-response/SKILL.md) - Detection-to-vulnerability correlation
  • [asset-inventory](../asset-inventory/SKILL.md) - Mapping findings to assets
Compartilhar X LinkedIn