tolmo findings to review Tolmo-authored findings and findings from connected scanners in one list. All subcommands accept --org and --profile. Use --json for structured output.
List and filter findings
--include-info.
Use the filter facets endpoint to discover filter values for your organization.
View a finding
Create a draft
API keys and ordinary user tokens can create draft findings. They cannot publish findings.--title and --severity are required. When you use a user token, also supply --resource-name to identify the affected resource. The default visibility is draft, and the default status is open. Use either --description for inline Markdown or --description-file for a file. Pass --description-file - to read stdin.
Save the ID returned by creation. Drafts are not included in the ordinary customer findings list.
Import a scanner report
Useupload to import a Markdown security report as third-party findings:
## Unified finding details section and findings with ### USR-<number>: <title> headings:
security-report.md
Keep the provider, source, and finding identifiers stable when you import an updated report. Matching records are updated instead of duplicated.
Change status
open, in_review, closed, acknowledged, and false_positive. Use the underscore in false_positive.
You can attach a justification to in_review, closed, or false_positive. Use either --justification or --justification-file; - reads stdin. --proof-url is available only for in_review and requires an HTTP or HTTPS URL.
For scanner findings, status changes affect Tolmo’s record. They do not update the source provider. A later scan can replace the local status.
Review status history
Manage evidence attachments
Sign in withtolmo auth login to manage attachments. These operations require a user token; organization API keys are not accepted.
--output. Pass --force to overwrite an existing local file. Attachment deletion is permanent and requires --yes.