Documentation / Advanced Configurations
Upload findings to Pensuite AI using Prancer CLI
Upload Findings via Prancer CLI
Already have results from another scanner (Burp, Nessus, a custom tool)? You can push them into Pensuite AI through the Prancer CLI so they show up in the same dashboard, get auto-tagged with MITRE ATT&CK, and feed reports.
Before you start
- The Prancer CLI installed locally or in your CI runner. See PAC CLI in CI/CD.
- Your customer ID and a valid access token (generate one in Tokens).
- Findings exported as a JSON array of objects:
[
{ "title": "Open Redirect", "severity": "medium", "url": "https://example.com/r?u=..." }
]
Warning: The file must be a JSON array at the top level. Single objects or NDJSON will be rejected.
1. Run the upload command
prancer-pac uploadlog \
-i <customerId> \
-t <token> \
--productLine <productline> \
--PRODUCT <product> \
--uid <uid> \
--file <path/to/file.json>
| Parameter | Description |
| --- | --- |
| customerId | Your tenant ID. |
| token | API token for authentication. |
| productLine | Product line grouping (e.g. payments). |
| PRODUCT | Product name (e.g. checkout-api). |
| uid | Unique identifier for this upload (use a timestamp or build ID). |
| file | Local path to the JSON findings file. |
Tip: Use the build number or commit SHA as uid so you can correlate findings to a specific pipeline run.
Next steps
- PAC CLI in CI/CD — automate uploads on every build.
- PAC Findings — view and triage uploaded results.
- Third-party Integrations — push findings on to Jira, ServiceNow, Slack, etc.