Skip to main content
Cyber gives you two kinds of report: an export of findings you pick, for a ticket, a fix review, or a customer, and the full report each test run writes when it finishes. Neither one starts a new scan, so you can export or rewrite as often as you need.

Prerequisites

  • View access to the Cyber app. Viewers can export findings and download run reports.
  • For a selected-findings export: at least one finding in the app. See Triage security findings.
  • For a Custom report: Chat access in the workspace and a reference report (PDF or DOCX, up to 5 MB).

Choose a report

Export selected findings as a PDF

1

Open Reports

Open your app from the Apps list in the Cyber sidebar and click Reports in the app header.
2

Select findings

The list shows Confirmed findings by default, grouped by severity. Change the status filter to include other stages, or use Quick select (Open, Fixed, or All). Tick findings one by one, or use Select all on a severity group.You can select up to 200 findings. Your selection is kept while you change filters, so one report can mix stages.
3

Export

In the action bar at the bottom, check the count and severity summary, keep Standard report selected, and click Export PDF.Success state: “Report ready. Your download has started.” Keep the page open while it reads “Preparing your PDF.”
Selected findings and the Standard report export bar.
Click Clear selection to start over. A failed export keeps your selection, so you can retry.

Write a custom report in your format

Use a Custom report when findings must match a template your team or customer already uses, such as an internal security review format.
1

Select findings

On Reports, select findings as for a Standard report.
2

Switch to Custom report

In the action bar, choose Custom report. Under Reference report, CloudThinker uses the reference saved in Report preferences if there is one. To use a different file for this report only, click Upload a reference report.
3

Generate

Click Generate custom report.Success state: a chat opens with your selected findings and reference loaded, and CloudThinker writes the report there. Ask follow-ups in the same chat to refine it.
CloudThinker copies the reference’s structure and style, not its facts. Example findings in the reference never appear as your results.

Set how future runs write their report

Report preferences belong to the app, not the workspace. Each run writes its report using the preferences saved when it starts, so change them before the next run.
1

Open Report preferences

On Reports, click Report preferences in the toolbar.
2

Choose the style and format

Pick Standard report or Custom report. For Custom, add a reference report (PDF or DOCX, up to 5 MB). Add Instructions · Optional, for example:
Under Output format, choose PDF or DOCX.
3

Save

Click Save preferences.Success state: the button reads Saved. The next run uses these settings. Runs already started, and selected-findings exports, aren’t affected.

Download or revise a run report

1

Open the run report

On Reports, click Latest Run report. For an older run, open Runs, select the run, and click its Report tab.
2

Download it

Click the download icon (Download report).Success state: the file downloads in the format chosen in Report preferences when that run started.
3

Revise it (optional)

Click the pencil icon (Revise report), describe the change in What should change?, for example “Shorten the executive summary and write it in Vietnamese.”, and click Generate revision.Success state: a new version is written from the same evidence. The original stays available, and no new test run starts.
Read the report’s coverage and authentication limitations before you share its conclusion. A revision only changes presentation. For a new verdict after a fix, run another test.

What reports include

  • Evidence: captured requests, responses, and screenshots saved during the run. Exporting or revising never captures new evidence.
  • Redaction: passwords, tokens, cookies, and keys are replaced with placeholders. Use your own test credentials to replay a request.
  • Limitations: a run report states what the run couldn’t test, such as areas behind a failed login, and when a needed screenshot is missing.
  • Proof flow: shown on the finding page and in copied findings, but left out of PDFs.

Troubleshooting

For every Cyber problem in one place, see Cyber troubleshooting.
The button is disabled when no finding is selected, when more than 200 are selected, or while an export is already preparing. Select between 1 and 200 findings.
If a selected finding changed since you picked it, the export fails instead of dropping it silently. Your selection is kept, so check it and click Export PDF again.
The tooltip reads “Chat access is required for Custom reports.” Ask a workspace admin for Chat access.
Add a reference report, or save one in Report preferences. Files must be PDF or DOCX, up to 5 MB.
The report is written when the run finishes. A stopped run doesn’t produce one, and a failed run that ends before writing it shows the same message. Start a new run to get a report.
Each run keeps the preferences from when it started. Use Revise report to change an existing report, or start a new run.

Next steps

Triage security findings

Check each finding’s proof before you share it

Run a security test

Run again to verify fixes and get a new report