Product

One orchestrator, eight security activities.

Each activity is a self-contained security engagement with its own report shape. Run one, or run several together. They execute concurrently against the same target, through whichever coding agent you already use.

security-architecture-review

Security Architecture Review

Controls matrix (presence, placement, layering), a design-principles verdict, operational & regulatory fit, CSA CCM v4 domain conformance, and a Design verdict for milestone gating.

threat-modeling

Threat Modeling

Adversary classes, STRIDE (+ LINDDUN when personal data is in scope), attack chains, every threat dispositioned Mitigated / Gap / Accepted, and an explicit residual risk statement.

sast

SAST — Static Code Analysis

Code-level findings with taint paths, CWE/OWASP mapping, and illustrative fix diffs. The agent states a CVSS v3.1 vector; Secfoo computes the base score from it with FIRST.org's published formula.

sca-reachability

SCA — Reachability & Upgrade Triage

Dependency inventory, a reachability verdict per risk, and a grouped upgrade plan. Package versions are checked against OSV.dev, so advisories come from a real database and the model is never asked to invent a CVE ID.

secret-scanning

Secret Scanning — Code, Confluence & Docs

Exposed credentials across source, config, git history, and linked Confluence pages, with a rotation-first remediation list.

prompt-review

Prompt Review

LLM prompt, tool-definition, and agent-behavior security review.

deployment-readiness

Deployment Readiness

Production security and operational readiness review.

responsible-ai-compliance

Responsible AI Compliance

Governance, transparency, fairness, and oversight review — drives the dashboard's Responsible AI risk badges.

Architecture review vs. threat modeling

These two look adjacent but answer different questions and fail differently, so Secfoo keeps them separate rather than merging them into one "threat assessment."

Control-centric · evaluative

Security Architecture Review

Asks is this design sound? Are controls present, correctly placed, and layered? Is least privilege enforced by the topology or merely by policy? Does the design fail safe? It also covers ground with no attacker at all: recoverability, key lifecycle, maintainability, regulatory fit.

Adversary-centric · generative

Threat Modeling

Asks what could go wrong, and who would make it go wrong? Enumerate threats from assets and trust boundaries, then disposition each as mitigated, accepted, or a gap, and state residual risk explicitly.

An architecture review can pass every checklist item and still miss a threat nobody enumerated. A threat model can list fifty threats and still miss that the design has no blast-radius containment. Run both.

Agents

Bring the agent you already use

Secfoo drives a coding-agent CLI that's already installed and logged in on your machine, or calls a model directly with an API key. Pick one with --agent, choose a model with --model or a per-agent default in config, and run secfoo agents to see what's on your PATH.

Agent IDRuns withModel selectionNotes
claudeClaude Code✓Read-only tool grant. MCP servers from your Secfoo config load automatically and nothing else does. Reports cost.
agentCursor✓MCP via secfoo mcp sync.
codexCodex CLI✓Runs in Codex's read-only sandbox. Reports token usage.
copilotGitHub Copilot CLI✓Copilot auto-approves tools, so read-only relies on the review instructions, not a sandbox.
geminiGemini CLI✓MCP via secfoo mcp sync. Reports token usage.
opencodeOpenCode✓Shell, edit and web-fetch permissions denied for the run. Reports cost.
droidFactory Droid✓Set FACTORY_API_KEY for non-interactive runs.
agyAntigravity—Headless mode denies tool calls that need approval.
devinDevin CLI—Log in first with devin auth login.
apiOpenAI, Anthropic or Gemini API key✓No agent CLI needed: pip install "secfoo[api]". Source files are sent in the prompt. Cost comes from LiteLLM.

Setup and troubleshooting for each one: Agent setup guide →

Program dashboards

Coverage across every project, not just the last run

Each focused activity gets its own program page. Architecture and threat-modeling views are built from what a report can state at review time and the exceptions you record. SAST, SCA and secret findings carry an open/closed lifecycle across rescans. Approximations are labeled, never guessed.

Security Architecture Review

Coverage %CCM v4 conformance heatmapFindings dispositionGate-decision mixRecurring root causes

Threat Modeling

STRIDE × asset-class matrixThreat dispositionRecorded risk acceptancesRecurring archetypesThreats found post-build

SAST

Open / closed findingsCVSS v3.1 bandsNetwork-reachable findingsSeverity & date filters

SCA

Cross-project vulnerability registerOSV.dev advisoriesReachability verdicts

Secret Scanning

"Looks live" funnelSource breakdownCross-project registerEvidence truncated to 8 chars
Threat modeling program dashboard with coverage and STRIDE
Threat Modeling: coverage, depth mix and STRIDE.
Security architecture design verdict and data-flow diagram
Security Architecture: design verdict and data-flow diagram.
Findings

Findings that follow the code, and leave with you

Keyed by code, not wording

A SAST or secret finding's identity is its CWE or secret type, the file, and a hash of the source around the reported line. An agent rephrasing a title doesn't create a duplicate, and two issues in one file stay distinct.

Open until it's fixed

After each run, findings that reappear stay open and findings that don't are closed. SCA findings are keyed by package and advisory, so a version bump that doesn't fix the issue keeps it open.

Skip what you've already scanned

Every run records the git commit it scanned. Rerun the same commit on a terminal and Secfoo asks first; --rescan scans anyway. CI runs always scan.

Export as JSON Lines or SARIF

secfoo findings export writes open findings, with language, framework and a code-free description of the vulnerable construct. --format sarif produces SARIF 2.1.0 for GitHub code scanning; --no-locations strips paths.

secfoo findings export                                   # open findings, JSON Lines
secfoo findings export --format sarif --project 1 -o findings.sarif
secfoo cost --by skill --since 2026-09-01                # AI spend across past runs
Assessments

One case file per review, from Ready to Completed

An Application ID / Security Assessment Request, a review status, and one or more attached runs or uploaded files — like an AI-BOM inventory. The Assessments, Third-Party, and Responsible AI dashboard pages are all built on top of it.

secfoo assessment create \
  --project https://github.com/org/vendor-app \
  --type third-party --app-id APP-042 \
  --sar SAR-2026-0007 --reviewer "Jane Doe"

secfoo run --skill security-architecture-review \
  --agent claude --assessment 1