Using the dashboard

secfoo serve opens a local web dashboard over everything you've scanned. You can also create assessments and start runs from it.

Starting it

secfoo serve                         # http://127.0.0.1:8787
secfoo serve --port 9000             # if 8787 is taken

It reads the same store as the CLI (~/.secfoo/), so runs started from either show up in both. Leave it running while you work; stop it with Ctrl+C.

No login, so keep it on localhost
The dashboard has no authentication. By default it listens on 127.0.0.1, reachable only from your own machine. Only use --host 0.0.0.0 where something else controls who can reach the port. For a shared, access-controlled view across a team, use the Cloud portal.

Finding your way around

Sidebar sectionPages
TopDashboard (program overview), Assessments (case files), Agents (adapter health)
AnalysisOne page per activity, e.g. SAST, SCA, Secret Scanning, Security Architecture, Threat Modeling
GovernanceThird-Party (vendor reviews) and Responsible AI

Press Ctrl+K anywhere to jump to a page or action by typing its name (↑/↓ to move, Enter to open, Esc to close). While a run is in progress, the top bar shows how many, with a link to Assessments. Most widgets have an info button that explains how the number is worked out, including where it's an approximation. Clickable table rows work with the keyboard too.

The Dashboard page

The landing page shows posture across every project: a checklist of four steps to your first signed-off review while you're getting started, the top findings across the program, and your most recent assessments.

Assessments: create, run, upload

The Assessments list shows every case file. Sort it by column, and select several rows to change their status in one go (Ready, In progress, Completed, Blocked).

To start a review from the browser:

  1. Choose New assessment (or Ctrl+K → New assessment).
  2. Fill in the project name, the project path (a local directory or a repository URL), the type (internal or third-party), and optionally the application ID, SAR number, reviewer, review date and notes.
  3. You land on the Run page. Pick one or more activities, the agent, the depth, and optionally Confluence URLs and paths to exclude.
  4. Start it. The run happens in the background, and the assessment page refreshes itself until it finishes.

The agent you choose must be installed and logged in on the machine running secfoo serve, the same as for the CLI.

Attachments. Upload files to an assessment from its page:

PDF, DOCX, PPTXVendor security documents, up to 25 MB each. On a third-party assessment, uploading one starts a Third-Party Risk Assessment automatically.
AI-BOMA file whose name contains ai-bom, aibom or ai_bom is parsed into a model and tool inventory.
Anything elseStored with the assessment as reference material.

A run's page

Shows the rendered report with severity badges, plus the agent, status, duration and cost. Architecture and threat-modeling diagrams render here once you've run secfoo vendor mermaid. Download the report as report.md, or the exact brief the agent received as prompt.md.

A project's page

Every run against one project, and an Activity coverage table listing each activity with when it last ran, including activities that have never been run against this project. That gap is often the most useful thing on the page.

Analysis: one page per activity

PageWhat you get
SASTProgram view of open and closed findings with CVSS bands. The findings list filters by project, severity and date. Each finding's page has the evidence, the fix, when it was first and last seen, and a review control.
SCAA cross-project vulnerability register. Each vulnerability's page shows the OSV.dev advisory where one matches, and the reachability verdict.
Secret ScanningA funnel that puts "looks live" credentials first, breakdowns by severity and source (code, config, history, docs), and a cross-project register.
Security ArchitectureCoverage, design verdicts, a CCM v4 conformance heatmap, findings disposition, exception aging, recurring root causes, and the most-deviated standards.
Threat ModelingCoverage, a per-project STRIDE × asset-class matrix, threat dispositions, accepted threats, assumptions, models needing rework, recurring archetypes and threats found post-build.
Other activitiesWhich projects have been scanned, when, and what each run found, with any diagrams.

Governance

Third-PartyEvery third-party assessment with its status, CCM conformance and any AI-BOM inventory. See Reviewing a vendor.
Responsible AIRisk badges per assessment, taken from the attached Responsible AI Compliance run's overall risk rating. A badge stays "provisional" until the assessment is marked Completed.

Agents

Lists every agent adapter, whether its CLI is installed on this machine, and when each last ran and last succeeded. If runs keep failing for one agent, start here, then see When a run fails.

← Reading a report Reviewing a vendor →