Early access · Limited availability

The penetration test your auditor will accept, on the timeline your board expects.

CyberOrbit produces ISO 27001, SOC 2 and PCI-DSS aligned penetration test reports: methodology, evidence, CVSS, remediation and re-test sign-off, in days, not quarters.

  • Aligned to PTES, OWASP & NIST SP 800-115
  • Reviewed and signed by a certified security professional
  • Re-test included, no extra SOW
cyberorbit.ai/reports/acme-corp · Q2 2026

External Penetration Test Report

acme-corp.com · v1.2 · ref CO-2026-04781
Signed offSigned
2
Critical
7
High
14
Medium
19
Low
Critical
Authentication bypass on /admin via JWT alg=none
CWE-287 · CVSS 9.4 · OWASP A07
9.4
High
Subdomain takeover: billing-staging via dangling CNAME
CWE-350 · CVSS 8.1 · evidence ref 4.2
8.1
Medium
SPF record permits ~all, email spoofing path exists
CWE-290 · CVSS 5.3 · mail.acme-corp.com
5.3
SIGNED OFF · 02 MAY 2026 · 14:22 UTC
M. Chen, Certified Security Professional, CyberOrbit
Used by security & GRC teamsbuilding audit packs across Australia, the UK and EU.
3,200+
Assessments delivered
94%
Pass first-time audit review
4d
Median time to signed report
11
Compliance frameworks mapped
01 · The problem

Why the pentest gets pushed to next quarter.

Every security lead has run this maths: the SOC 2 deadline is in six weeks, the pentest firm needs eight, the SOW is three weeks behind on legal, and the auditor wants evidence formatted just so. Something has to give. Usually it's the pentest.

PROBLEM · 01

Scope takes longer than the test.

Six rounds of email to agree IPs, assets, windows, and rules of engagement. By the time the SOW is signed, the auditor is already on your case for evidence.

"We spent four weeks on the scoping call before anyone touched a scanner.", Head of Security, Series-B SaaS

PROBLEM · 02

Reports are PDFs your auditor can't parse.

Findings without CVSS. Evidence buried in screenshots. Remediation guidance that says "patch the system." The auditor sends it back with a request for "more rigour", and you've burned a fortnight.

"The PDF was 84 pages and our auditor flagged 12 findings as not actionable.", vCISO, healthtech

PROBLEM · 03

Re-test is a second SOW, not a follow-up.

You fix the criticals. You need a re-test to close the audit finding. The firm quotes you for a brand-new engagement, and the loop starts again. Compliance becomes a budget line, not a control.

"Re-test was 60% of the original cost. We deferred it to next year.", Compliance Manager, fintech

02 · How it works

Four steps. One signed report.

From kickoff to signed-off audit artifact, every assessment moves through the same four stages. No surprise scope changes, no re-test invoices.

01
Day 0 — 1

Scope

Drop in your in-scope domains, IPs, and accounts. CyberOrbit generates a draft SOW, rules of engagement, and an authorisation letter ready for your auditor.

SOW.pdf · Auth letter.pdf
02
Day 1 — 3

Test

Reconnaissance, vulnerability validation, and exploitation chains run continuously — with every action timestamped, attributable, and evidenced in chain-of-custody logs.

Evidence chain · Live stream
03
Day 3 to 4

Report

Findings rendered with CVSS, CWE, OWASP and framework mapping, business-language impact, and step-by-step remediation. Reviewed and signed by a certified security professional.

Pentest Report v1.0.pdf
04
Within 30 days

Sign-off

You remediate. We re-test, evidence the fix, and reissue a signed letter — included, not invoiced. Hand the bundle to your auditor and close the finding.

Re-test sign-off letter.pdf
03 · Coverage

Six coverage categories. Every finding evidenced.

CyberOrbit runs the assessment as a human pentester would, but in parallel, continuously, and with every step machine-evidenced. We've grouped the work into the categories your auditor asks about.

External attack surface

Subdomain enumeration, certificate transparency, exposed services, dangling DNS, and orphaned assets: everything an outsider can find before they touch your perimeter.

ReconDNSCertsSubdomains

Web application & API

OWASP Top 10 and API Top 10 coverage with authenticated flows, broken-access-control chains, business-logic testing, and validated exploit paths. Not just scanner output.

OWASP A01–A10APIAuth

Network & infrastructure

Open ports, weak ciphers, end-of-life services, default credentials and unsegmented networks, mapped to CVEs with reachable exploitation, not theoretical CVSS.

CVE-validatedTLSPorts

Identity & cloud config

IAM misconfigurations across AWS, Azure and GCP. Over-privileged service principals, public S3, dormant admin accounts, and SSO bypass surfaces.

AWSAzureGCPIAM

Email & brand defence

SPF, DKIM, DMARC posture; lookalike domain detection; impersonation pathways. Auditors increasingly want this and most reports skip it.

DMARCSPF/DKIMLookalikes

Attack-chain intelligence

Findings linked into plausible exploitation paths: "this leaked credential reaches this exposed admin via this misrouted DNS", so remediation is prioritised by blast radius, not CVSS alone.

Kill chainMITRE ATT&CKBlast radius
03b · The engine

A multi-model security unit, not a single LLM.

CyberOrbit pairs frontier reasoning models with fast open-source models on Groq, so every finding is generated, cross-checked, and validated before it reaches the report. The result: pentest-grade depth without scanner-grade false positives.

Frontier reasoning, not just patterns

GPT-5.5 and Claude Opus 4.6 plan the engagement, write the exploit chain, and explain every finding in plain English. Pathfinder reconnaissance fingerprints the stack first so the right scanners run on the right targets.

Open-source models on Groq for the heavy lifting

Llama, Qwen, and Mixtral instances on Groq inference run hundreds of validation passes per finding in parallel — fast enough to test every payload variant without the per-token cost of a frontier model on each call.

A self-correcting, self-validating unit

Every finding is generated by one agent and checked by another. Disagreements are resolved by a third reasoning model with access to the raw HTTP traffic. False positives don't make it into the report — they get caught at the validation layer, not by your auditor.

Sandboxed exploitation, real evidence

After scanners complete, an isolated Ubuntu sandbox runs adaptive payloads with nmap, sqlmap, nuclei, and custom Python — every action timestamped and hashed into the chain-of-custody log. The exploit is real, the evidence is real, the screenshots are real.

Models in rotation:GPT-5.5·Claude Opus 4.6·Llama 3.3·Qwen 2.5·Mixtral 8×22B

Inference: OpenAI · Anthropic · Groq · Together

04 · What you receive

What's actually in the report.

Six artifacts. Each one written to be the answer to a specific auditor question — so when control evidence is requested, you forward a section, not a 100-page PDF.

Part 01pp. 1 — 6

Executive summary & risk posture

One-page board view: severity distribution, attestation, posture trend versus last engagement, and the three remediations that close the biggest exposure.

Audit answer →"What is the current risk position?"
Part 02pp. 7 — 12

Methodology & scope statement

Frameworks followed (PTES, OWASP, NIST SP 800-115), targets in/out of scope, dates, tooling, and rules of engagement — signed and dated.

Audit answer →"Was the test conducted to a recognised standard?"
Part 03pp. 13 — 58

Findings with CVSS, CWE & OWASP

Every finding carries CVSS 3.1, CWE class, OWASP category, framework cross-references (ISO A.8.29, SOC 2 CC7.1, PCI 11.3), and machine-readable JSON for ingestion into GRC tools.

Audit answer →"Show me the issues, classified."
Part 04pp. 59 — 74

Evidence & chain-of-custody

Timestamped logs, screenshots, request/response captures, and the hash trail proving the test happened, when, and by whom. The bit auditors keep asking for.

Audit answer →"How do I know the test was actually performed?"
Part 05pp. 75 — 88

Remediation guidance

Per-finding fix steps, owner role suggested, effort estimate, and detection rules so blue-team can verify when the fix lands.

Audit answer →"What is the remediation plan?"
Part 06pp. 89 — 92

Tester attestation & sign-off

Reviewed and signed by a certified security professional. Re-test addendum issued within 30 days of remediation and bundled with the original engagement, no second SOW.

Audit answer →"Who signed this off, and against what?"

Pre-mapped to the frameworks your auditor uses.

Every finding carries cross-references so the same report serves multiple audits — without re-formatting the evidence.

ISO 27001:2022A.8.29 · A.8.8
SOC 2 (Type II)CC7.1 · CC4.1
PCI-DSS 4.011.3 · 11.4
HIPAA164.308(a)(8)
Essential 8ML2 · ML3
CPS 234 (APRA)Para 27 · Para 35
NIST CSF 2.0ID.RA · PR.PS
CIS Controls v8CIS 18 · CIS 7
06 · Pricing

Your annual pentest costs $15,000. Ours starts from $7,999, and delivers in 48 hours.

One-time or continuous — pick how you engage. Re-test included on every tier. No per-asset surprise bills.

Most popular starting point

Pentest On-Demand

A full external penetration test — reconnaissance, exploitation, attack chains — delivered as a signed, audit-ready report within 48 hours. No SOW negotiation, no 6-week wait. Re-test addendum included at no extra cost.

  • Certified security professional sign-off
  • CVSS 3.1 · CWE · OWASP per finding
  • Chain-of-custody evidence bundle
  • Re-test addendum within 30 days
  • ISO 27001, SOC 2, PCI-DSS cross-references
$7,999
one-time · per engagement
Get started →

Delivered in 48 hrs · no subscription

Or choose continuous coverage
Most popular

Pro

Growth-stage SaaS · VP Engineering / CTO

$1,499/ mo

$1,199/mo annual · $14,388/yr

  • 2 signed reports per year
  • Up to 50 endpoints per assessment
  • AI attack chain analysis
  • ISO 27001, SOC 2, PCI-DSS cross-references
  • Jira and Slack integrations
  • Email support, 48h SLA
  • Re-test addendum included
Get started

Scale

Series B+ · Head of Security / CISO

$2,999/ mo

$2,399/mo annual · $28,788/yr

  • 4 signed reports per year
  • Up to 150 endpoints per assessment
  • Full adversarial scan suite
  • HIPAA, Essential 8, CPS 234 mapping
  • SSO (SAML/OIDC), API access
  • Dedicated CSM, 4h SLA
  • Multi-team workspaces, RBAC
  • Unlimited retention, audit-ready export
Get started

Enterprise

Mid-market & regulated · CISO / Director

Custom
  • Unlimited signed reports
  • Unlimited targets and assessments
  • Full adversarial scan suite
  • All compliance frameworks
  • Dedicated CSM, 99.9% uptime SLA
  • White-labelled reports on request
  • Custom agent configuration
Talk to us
MSP Programme

Resell or white-label for your clients

Add audit-ready penetration testing to your service stack. White-labelled reports, no pentesters to hire. Partner pricing available on application.

Talk to us about partner pricing

All tiers include certified professional sign-off · re-test addendum · chain-of-custody evidence · framework cross-references

05 · Common questions

What auditors and security leads ask us first.

The questions that come up in every scoping call. If yours isn't here, book the walkthrough below — we'll give you a straight answer in plain English.

Audit window closing?

Get an audit-grade penetration test before your next assessment cycle.

Book a 20-minute walkthrough. We'll show you the report your auditor will see, and the evidence chain underneath it.