Skip to main content

​
Browse Findings

Open Findings to view findings across your organization. Use the target selector to show all targets or focus on one target. Search findings, filter by severity or assignee, and sort the results to focus your triage.

​
Drill Into a Target

Use the target selector to focus on one target. Then:
  • switch between Open, Resolved, and Archived
  • include secured findings in the Open view when needed
  • filter, search, sort, and page through results

​
Finding Actions

Open a finding to:
  • review full details, evidence, proof-of-concept detail, and AI-generated summaries
  • assign or unassign an owner
  • add comments
  • resolve or reopen the finding
  • create a linked issue in Linear or Jira (if connected)
  • request a patch (if available)
  • archive, unarchive, or delete when appropriate
  • start retest actions when available

​
Finding Artifacts

Finding details are designed to give security and engineering teams enough context to verify, prioritize, and fix the issue. Depending on the finding type, details can include:
  • severity
  • CVSS v3.1 score
  • OWASP category and vulnerability tags
  • exploitability assessment
  • affected endpoint, host, file path, component, or package when available
  • evidence captured during the run
  • proof-of-concept or approach details
  • attack flow graph when available
  • impact summary
  • remediation guidance
  • validation details or retest actions when available
Use the evidence and proof-of-concept detail to reproduce the issue in a controlled environment before changing production systems. Vulnerable-component findings may include advisory or CVE evidence when the affected component and version are available.

​
Severity and CVSS

MindFort uses severity to help teams prioritize triage quickly. Finding details show the severity label and the CVSS v3.1 score when available. Prioritize:
  1. critical and high findings that are exploitable
  2. findings with clear proof-of-concept evidence
  3. issues that cross tenant, user, or role boundaries
  4. findings affecting internet-exposed or privileged components

​
Bulk Actions

For large queues, select multiple findings and apply batch actions:
  • resolve or reopen
  • archive or unarchive
  • create Linear or Jira tickets when connected
  • delete
Available actions depend on the current tab and your permissions.

​
Collaboration Flow

  1. Assign owner.
  2. Add implementation notes in comments.
  3. Resolve the finding when remediation is ready for validation.
  4. Retest and confirm final status.

​
API and MCP

List findings programmatically with the same filters the UI uses:
  • Findings API — GET /v1/findings (API key)
  • MCP — list_findings tool (OAuth)
Use status=ACTIVE&exclude_secured=true to match the default Open tab, status=RESOLVED for the Resolved tab, status=ARCHIVED for the Archived tab, and assessment_id to scope results to one assessment run.