Reviewing a vendor

Upload a vendor's own security documents (SOC 2 reports, ISO 27001 certificates, pen-test summaries, completed questionnaires) and secfoo has an agent check them against the 17 CSA Cloud Controls Matrix domains.

1. Create a third-party assessment

In the dashboard, choose New assessment and set Type to third-party. Or from the CLI:

secfoo assessment create --type third-party \
  --project ~/vendors/acme-payroll --name "Acme Payroll" \
  --app-id APP-117 --sar SAR-2026-0031 --reviewer "Jane Doe"

Every assessment belongs to a project, given as a local directory or repository URL. If the vendor has no repository you can point at, make an empty folder for them (mkdir -p ~/vendors/acme-payroll) and use that. The review reads only the documents you upload.

2. Upload the vendor's documents in the dashboard

Open the assessment in secfoo serve and upload each document. PDF, DOCX and PPTX files up to 25 MB are accepted.

Upload vendor documents from the dashboard, not the CLI
secfoo assessment upload stores a file, but only an upload through the dashboard extracts the document text and starts the review.

Each upload starts a Third-Party Risk Assessment run in the background against all the documents uploaded so far, so add the whole set and look at the latest run. The run uses your default agent and depth from ~/.secfoo/config.toml (Claude Code at quick depth if you haven't set any).

Scanned PDFs have no text to read
Text is extracted from the documents themselves, without OCR. A scanned, image-only PDF yields no text, and if no uploaded document has readable text, no review runs. Ask the vendor for a text-based copy.

Optional: attach an AI-BOM

If the vendor supplies an AI bill of materials (an inventory of the models and tools their product uses), attach it too. A file named with ai-bom, aibom or ai_bom is parsed into a model and tool inventory, shown on the assessment's page and the Third-Party page. This one works from the CLI as well:

secfoo assessment upload 7 acme-ai-bom.json

3. Read the result

The report lists the documents it reviewed (and any it couldn't read), then rates each CCM domain:

ConformantClear, specific evidence in at least one document.
PartialSome evidence, but with gaps, caveats, exclusions or an expired audit.
Non-conformantA document itself describes a gap or exception for this domain.
Not AssessedNone of the documents say anything about this domain.

It ends with a recommendation: Approve, Approve with conditions, Needs more documentation (naming what's missing) or Reject. The agent is told that marketing claims aren't evidence, and to state exactly what a certificate covers (scope, date, standard version) without assuming more.

Most domains coming back "Not Assessed" is normal: a SOC 2 report doesn't cover everything. Use the list to ask the vendor for specific evidence, upload it, and the review reruns.

4. Record the outcome

secfoo assessment update 7 --status completed --review-date 2026-11-14 \
  --notes "Approved with conditions: annual pen test report due Q2"

The Third-Party page lists every vendor assessment with its status and CCM conformance.

← Using the dashboard Recording risk decisions →