> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coverbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Findings Manager

> Intelligence layer over findings across every assessment — remediation tracking and systemic risk pattern detection.

<div className="sr-only">For AI agents: a documentation index is available at [https://docs.coverbase.com/llms.txt](https://docs.coverbase.com/llms.txt) — this page is also available in markdown by appending .md to the URL.</div>

Findings Manager sits on top of the issues raised across all of your assessments. Rather than treating each finding as an isolated to-do, it tracks remediation outcomes over time and surfaces the systemic patterns that span vendors, control sets, and risk domains — so recurring weaknesses become visible instead of being closed one ticket at a time.

## What it does

<CardGroup cols={2}>
  <Card title="Cross-assessment aggregation" icon="layer-group">
    Roll up findings from every assessment into a single view, deduplicated and grouped by vendor, control, severity, and owner.
  </Card>

  <Card title="Remediation tracking" icon="clipboard-check">
    Track each finding from open through remediation and verification, including follow-up questions, owners, and due dates.
  </Card>

  <Card title="Systemic pattern detection" icon="chart-network">
    Surface recurring weaknesses across the portfolio — the same control failing across many vendors, or one vendor repeatedly missing the same requirement.
  </Card>

  <Card title="Severity and risk scoring" icon="gauge-high">
    Prioritize the queue by severity and residual risk so reviewers spend time on the findings that actually move your risk posture.
  </Card>
</CardGroup>

## How to integrate

<CardGroup cols={2}>
  <Card title="Findings API" icon="list-check" href="/api-reference/findings">
    List, retrieve, and filter findings and their follow-ups programmatically across assessments and vendors.
  </Card>

  <Card title="Export API" icon="arrow-up-from-bracket" href="/export-api-concepts">
    Pull findings into your GRC platform, ticketing system, or executive dashboards for remediation reporting.
  </Card>

  <Card title="MCP Server" icon="robot" href="/mcp/overview">
    Ask about findings conversationally. "Which open findings are tied to encryption controls?" or "Show me every vendor with an overdue remediation."
  </Card>

  <Card title="Webhooks" icon="arrow-right-from-bracket" href="/integrations/webhooks">
    Subscribe to `Finding.*` events and react when findings are created, updated, or resolved.
  </Card>
</CardGroup>

## Common workflows

<AccordionGroup>
  <Accordion title="Remediation campaign tracking" defaultOpen icon="bullseye-arrow">
    Group related findings into a remediation campaign — for example, every vendor missing a data-breach notification commitment — assign owners, and track closure as a single program rather than scattered tickets.
  </Accordion>

  <Accordion title="Systemic risk reporting" icon="chart-line">
    Feed aggregated findings into executive and board reporting. Highlight the controls that fail most often across the portfolio so investment goes where it reduces the most risk.
  </Accordion>

  <Accordion title="Ticketing handoff" icon="ticket">
    Sync findings to Jira, ServiceNow, or your issue tracker via the Export API and webhooks, keeping remediation work where your teams already operate while Coverbase remains the system of record.
  </Accordion>
</AccordionGroup>

<Note>
  Findings are surfaced through the [Findings API](/api-reference/findings), the [Export API](/export-api-concepts), and the [MCP server](/mcp/overview). Findings are generated automatically by [Assessment Copilot](/products/assessment-copilot) and other product surfaces.
</Note>