Skip to main content
  • Overview: high-level security status and activity
  • Assessments: active, scheduled, and historical assessments
  • Findings: browse, filter, assign, and manage the finding lifecycle
  • Code Review: configure and review code changes when enabled for your organization
  • Coverage (Beta): review tested surfaces and coverage gaps
  • Agents: directed agent runs, reusable templates, and schedules
  • Analytics: organization-wide finding and remediation trends
  • Target Inventory: manage targets, DNS verification, scope, credentials, and login instructions
  • Infrastructure: explore infrastructure relationships when enabled for your organization
  • Knowledge Lakes: manage team and target documents used by MindFort agents
  • Reporting: generate and manage downloadable reports
  • Settings: profile, team, billing, notifications, integrations, WAF, API keys, and status
  • Billing: quick access to credits, subscription, payment methods, and invoices
  • Docs: open this documentation

​
Assessments vs. Agents

Assessments are fully autonomous penetration tests. Once started, the platform runs the entire assessment end-to-end without any input from you. You configure the target and method, press start, and review findings when it finishes. Agents are directed security operations. You describe what you want done, and agent teams carry out the work based on your instructions. During execution you can monitor progress, approve steps, and provide additional direction as needed. Agents are ideal when you need targeted investigation, custom checks, or anything that requires human guidance along the way.

​
MindFort as the Security Context Platform

MindFort is not only a set of scanners or agents. It is the place where your security context lives: targets, scope, guardrails, credentials, login instructions, uploaded knowledge, memories, findings, remediation context, reports, and integrations. The agent workflows use that context as they work. Assessments can discover findings, Agents can investigate targeted questions, MCP can bring findings into coding agents, Slack can launch directed work from team conversations, and reports can package the results for stakeholders. Each workflow connects back to the same platform context instead of creating isolated security artifacts.
  1. Keep target configuration current.
  2. Run assessments regularly.
  3. Triage findings and assign owners.
  4. Retest and validate resolved findings.
  5. Publish regular reports.

​
Core Security Artifacts

  • Scope and guardrails define what agents may test and which areas require extra care.
  • Credentials and login instructions unlock authenticated coverage.
  • Assessment logs show endpoint and note evidence recorded for an assessment run.
  • Findings capture severity, CVSS score where available, evidence, proof-of-concept detail, and remediation guidance.
  • Reports package target-level results for stakeholders.

​
Access Notes

Some sections depend on role, plan, or billing status. If a feature is unavailable, confirm:
  • user role permissions
  • active subscription state
  • feature availability for your organization