Reports & Report Import
Generate comprehensive security reports, export findings in multiple formats, and import findings from external security assessments.
Generating reports
PDF reports
Generate a PDF report of your findings with charts, metrics, and remediation guidance.
- Go to Findings
- (Optional) Apply filters to narrow the report scope — severity, repositories, status,
date range, search text, and any advanced (
fq) clause - Open the Download dropdown (next to the table) and click PDF
The report contains exactly the findings you see: it is generated with the same filters as the table, and its cover states the active scope as chips.
What the report contains, written for security leadership:
- Executive summary: severity counts, outcome counts (open, in progress, resolved, fix ready, exploitable with EPSS of 50% or more), a bottom-line callout, and the scope and methodology, including how many findings came from repository scans and how many from pentests.
- Risk at a glance: severity distribution, findings by type, the CWE categories where findings concentrate, and vulnerable dependencies by package.
- Top-priority findings: up to six distinct issues to fix first, with at least one for every finding type that has a critical finding. A vulnerable package or rule that repeats across files counts once, with its number of locations. Each card shows CVSS, EPSS, confidence, age since detection, owner, business risk and the recommended fix. Badges show evidence the platform holds: validated by a pentest, reachable or not reachable, and whether a pull request or ticket has already been created.
- Findings register: the findings grouped by type, worst first, with severity, status, age and location. The register lists up to 500 findings; the summary counts and charts always cover every finding in scope. For the full list, use the JSON export below.
- Remediation roadmap: a three-phase plan, marking the items that already have a pull request or ticket.
Within the same severity, findings are ranked by exploitation evidence, then reachability, then CVSS, then EPSS. EPSS only exists for known CVEs in dependencies, so it never pushes code, secret or pentest findings down the list.
Status follows the platform: findings awaiting action are Open, findings with a submitted pull request or a filed ticket are In progress, and solved findings are Resolved.
The report is generated asynchronously so the app never waits on it. You receive an email with the PDF attached — open or save it straight from your inbox. The same report also appears in your in-app notification center with a download link.
Availability: Scale plans and above. Rate limit: 5 PDF reports per hour per organization.
JSON (SARIF) export
Export findings for use in other security tools, dashboards, or external systems.
- Go to Findings
- (Optional) Apply filters
- Open the Download dropdown and click JSON
- The file downloads immediately
The file is a SARIF document with the same findings as the table: same filters, same default exclusions (false positives, duplicates, sandbox). Tool names appear as the Plexicus engine names, and secret findings never include the secret value.
Report import (AI-powered)
Import findings from external security assessments (pentests, third-party reports) and let AI extract findings automatically.
Supported formats
- Markdown (.md)
- Plain text (.txt)
- CSV (.csv)
- Excel (.xlsx)
- Word documents (.docx)
Import a report
- Go to Integrations → Connectors → Connectors
- Find AI Report Import
- Click Configure or Import
- Select a repository (the findings will be associated with this asset)
- Upload the report file
- Click Import Report
The report is sent to Plexicus's AI processor, which extracts findings and maps them to your codebase. This process consumes AI credits per report; see Credits per action in Settings → Usage.
Processing
Once submitted:
- The report is analyzed by LLM
- Findings are extracted and deduplicated
- High-confidence findings are created in Plexicus
- Lower-confidence entries are flagged for review
Check the Findings page after a few moments; imported findings will appear with a Imported label and the source report name.
Managing exported/imported data
View export history
- Go to Settings → Account
- Scroll to Export History
- View recent exports and downloads
Re-download a PDF report
- Open the report email and save the attached PDF again from your mailbox, or
- Go to the notification center (bell icon) and click the report's download link
Reports have no expiry; regenerate any time using the steps above.
Review imported findings
Imported findings appear in your Findings list and can be:
- Triaged (marked false-positive, mitigated, etc.)
- Assigned to developers
- Linked to tickets
- Exported again in reports
API
Exports and API tokens
Finding exports (JSON/SARIF, CSV, PDF reports and their download) are available in the web
app only: the export routes answer 403 to API and service tokens. To read findings from an
integration, use the findings API with an API token instead; see the
API Guide for authentication and request conventions.
Import via API
POST /report-imports
Upload a report file. The response returns a workflow_id; the import runs asynchronously and the findings appear in the repository view when it completes.
Troubleshooting
"Report generation failed"
- Ensure you have findings to include in the report
- Try generating with fewer filters first
"PDF report is taking too long"
- Generation runs in the background; the app stays responsive
- You'll receive an email with the PDF attached when it is ready
"AI Report Import failed"
- Verify the file format is supported (.md, .txt, .csv, .xlsx, .docx)
- Ensure the file is not corrupted
- Check that you have AI credits remaining
"AI credits insufficient"
- Each report import costs AI credits (see Credits per action in Settings → Usage)
- Check your allowance in Settings → Billing, or send a plan change request from there
Best practices
- Use filters for focused reports: Export findings by severity or tool to create targeted reports for stakeholders
- Schedule regular exports: Export weekly or monthly snapshots for compliance tracking
- Import third-party reports early: Import pentests or vendor assessments immediately to avoid duplicate work
- Tag imported findings: Use labels to distinguish imported findings from automated scanner results
Next Steps
- Triage findings after import or export
- Create tickets from findings for tracking
- Generate remediations for code-based findings