Skip to main content

Pentest Reporting

Cyver Core transitions your team from manual, time-consuming reporting to an automated, token-based reporting engine. Instead of copying and pasting data across static text documents, you will build dynamic templates once and let the platform automatically generate comprehensive, branded reports in seconds.

Follow this onboarding flow to set up your automated reporting pipeline: Templates > Client/Assets > Project/Findings > Publishing.

1. Preparing Your Templates

Before testing begins, setting up your core templates ensures that every report your team produces follows your exact branding, structural hierarchy, and data collection standards without requiring manual formatting every time.

A. Create Your Report Template

Define the visual and structural output of your final document.

  • Navigate to Settings > Report Templates and click + New Report Template.
  • Add Sections: Build your document structure (e.g., Cover Page, Executive Summary, Technical Details).
  • Format & Use Tokens: Use Markdown for styling and insert dynamic tokens (like {Project_Name} or {Findings_Table}) to pull live project data directly into the document.
  • Styling: Customize the look and feel to match your corporate branding.
  • For a complete walkthrough on styling, Markdown, and using tokens, read our detailed guide on Customizing Report Templates.

B. Build Finding Libraries & Templates

Building a centralized knowledge base prevents pentesters from rewriting the same vulnerability descriptions over and over. Reusing "gold-standard" templates ensures consistent, high-quality technical data automatically feeds into your final report.

  • Navigate to Settings > Finding Libraries and click + Add Finding Library.
  • Open the library and click + Add Finding Template to manually create your standard vulnerabilities. Alternatively, you can push real-world vulnerabilities from active projects into the library by opening a finding and selecting Add to Library.
  • Check out our comprehensive guide on Finding Libraries and Findings Templates.

C. Create Your Pentest Template

Bundle your workflows, scopes, and reporting standards into a repeatable service offering.

  • Navigate to Settings > Pentest Templates and click + New Pentest Template.
  • Workflows & Methodologies: Link your specific Workflow Templates, Checklists, and Compliance Norms (like OWASP). 

Tip: Download Ready-to-Use Frameworks

No need to build frameworks from scratch! You can download comprehensive, globally recognized standards from our GitHub repository and easily import them into your workspace.

  • Report & Finding Defaults: Link the Report Template you created above and define the default CVSS version to ensure scoring consistency.
  • To learn more, read our article on Customizing Pentest Templates.

2. Client Onboarding

Reporting isn't just about listing vulnerabilities; it's about mapping those risks to specific business contexts. Setting up the client workspace ensures that vulnerabilities are tied to specific target assets and that the final report is delivered securely to the correct stakeholders.

  • Add Client: Navigate to Clients to create the dedicated workspace.
  • Add Users: Invite the specific client stakeholders who need access to the reports and findings.
  • Add Assets: Define the scope by adding the target URLs, IPs, or networks that will be tested.
  • For more details, refer to our Onboarding Clients article.

3. Project Execution & Findings

This is where the actual testing occurs and data is gathered. How you manage your finding statuses here directly controls what goes into the final report and what the client can see in their portal.

A. Start a New Pentest

  • Project Creation: Create a new project by selecting the specific Client and the Pentest Template you prepared.
  • Define Scope: Navigate to the project's Scope tab to officially attach the target Assets.

B. Manage Findings

  • Add Findings: Navigate to the Findings tab. Instead of writing from scratch, click Import/Export > Import from Library to pull your pre-written Finding Templates directly into the project.
  • Draft Mode: Keep findings in Draft or To Review while you are still working. These statuses are strictly internal and hidden from the client.
  • Live Ticketing: When a finding is ready, change its status to Pending Fix. This automatically triggers notifications and makes the vulnerability visible in the Client Portal.
  • Discover more about importing findings in Import Findings.
  • Discover finding statuses in Finding Status.

4. Report Generation & Delivery

Turn weeks of technical testing and finding management into a polished, executive-ready PDF document with a single click.

  • Generate the Draft: Navigate to the Report tab inside your project. Click Generate Report from Report Template. Cyver Core will instantly populate all your predefined tokens with the project's live data to create your first draft.
  • Review & Export: Review the generated document. You can easily export the branded PDF directly for physical distribution or executive summaries.
  • Publishing: Once the report is finalized, click Publish to make the interactive version securely visible on the Client Portal.
  • For more reporting features, explore our full article on Generating, Changing, and Duplicating Report Templates.

 

Was this article helpful?