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

​
Pin findings for follow-up

Select Pin finding on a finding to keep it near the top of your results. Select Unpin finding to remove it. Pins still respect your current filters. You can pin up to 100 findings. Pins are personal to your account and organization in the current browser; they are not shared with teammates or synchronized across browsers. Members whose only role is auditor cannot pin findings.

​
Recover a retest with failed credentials

If a retest reports an authentication failure or an unavailable credential, select Choose another credential in the finding details. Choose a valid credential from the same target, review both accounts for a dual-account finding, and select Retest. See credential recovery for the full steps.

​
Finding Artifacts

Finding details provide context to help security and engineering teams investigate, prioritize, and address reported issues. 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. Review the evidence in the context of your application before accepting a finding’s severity or conclusion. Record corrections through Agent Context or a False Positive decision when appropriate. 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

​
Adjust a finding rating

When severity overrides are enabled for your organization, open a red-team finding and select Edit beside its rating. Choose a severity and, optionally, a CVSS v3.1 score from 0.0 to 10.0 with one decimal place, then select Save override. Use Restore MindFort rating to return to the generated rating. Changing a rating does not resolve the finding; record your triage reasoning in a comment. Members whose only role is auditor cannot change ratings.

​
Record a resolution decision

When resolving a finding, choose the reason that matches your decision:
  • Fix: Record the remediation and how it was verified.
  • Won’t Fix: Explain why your team is accepting or deferring the issue.
  • False Positive: Explain why the reported issue is not a vulnerability. This archives the finding as a false positive and requires a reason.
A manually resolved finding is not the same as a successful retest. After deploying a fix, use Retesting to validate it against the target.

​
Give agents feedback

Use Agent Context in the finding details to add or edit feedback about accuracy, severity, evidence quality, or missing context. Give a specific explanation that future agents can use when investigating the target. Members whose only role is auditor can read existing feedback but cannot edit it.

​
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 review the result and supporting evidence.

​
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.