Syncing to the Cloud portal
With the Cloud edition, every machine that runs secfoo (laptops and CI runners) pushes its results to one hosted portal, so a team sees all of them in one place. Local runs and secfoo serve keep working exactly as before.
1. Get an ingest key
Your portal admin issues API keys per workspace. You need an ingest key: it lets a machine push results. A view key is for signing in to the portal in a browser, and secfoo cloud login rejects it. Don't have a workspace yet? Request one.
2. Connect the machine
secfoo cloud login --api-key <ingest-key>
secfoo checks the key with the portal, then saves it to ~/.secfoo/cloud.toml, readable only by you. If your organisation uses its own portal address, add --portal-url https://portal.example.com.
3. Run as usual
From now on, every successful secfoo run on this machine is pushed to the portal when it finishes. If the push fails (no network, portal down), the run itself still succeeds and stays queued locally. Check and catch up with:
secfoo cloud status # which portal, and how many local runs haven't synced
secfoo cloud sync # push them now
Use the same --app-id for the same system on every machine. Runs from your laptop and from CI against the same target then land in one assessment in the portal, not one per machine.
In CI
Store the ingest key as a CI secret and log in at the start of the job:
secfoo cloud login --api-key "$SECFOO_INGEST_KEY"
secfoo run --skill sast --skill secret-scanning --agent api --target . \
--project-name payments-api --app-id APP-042 --json > secfoo-result.json
What's sent to the portal
| What | Includes |
|---|---|
| The report | The full Markdown report, as you'd see it in secfoo show. |
| Run details | Activity, agent, status, start and finish times, duration, tokens and reported cost, any Confluence URLs, the scan scope, and the secfoo version. |
| Project | Its identifier (the path or repository URL) and display name. |
| Assessment | Type, status, application ID, SAR number, reviewer, review date and notes. |
Your source code is not sent. The report text can quote short snippets of it as evidence, the same as when you share a report by hand.
Disconnecting
secfoo cloud logout
Removes cloud.toml. Nothing local is deleted, and runs already in the portal stay there.