Sample report

    See exactly what you receive.

    A walkthrough of the real artifacts inside a TitanDef.ai penetration test report — annotated block by block, so you can judge report quality before you ever scope an engagement.

    Request a pen test scope call →Illustrative · content redacted
    SAMPLE / V2026.Q336 PP · SIGMA RULES

    Artifact · 01 / Executive summary

    The one page a board actually reads.

    Executive Summary · Excerpt
    Engagement #PT-26-014

    What this means
    for the business.

    We tested the systems that hold customer billing, support tooling, and the admin console. An attacker working from the open internet could reach customer data in under a day. Three fixes close most of the exposure.

    Business Risk
    Material
    Pre-remediation
    Revenue at Risk
    $4.2M
    ARR exposed
    Time to Fix
    14d
    Top-3 criticals
    Audit Impact
    SOC 2
    CC6.1, CC7.2
    01 / In Plain Terms

    What an attacker could do.

    • i.Phish a single support agent and read every customer's billing data within an hour.
    • ii.Pivot from a stale cloud role into the production database without triggering an alert.
    • iii.Hijack a logged-in admin session through the SSO callback and act as that admin.
    02 / Recommended Order

    What to fix, by when.

    • ImmediatePatch deserialization path · rotate exposed service tokens
    • 30 daysEnforce hardware MFA on support + admin roles
    • 60 daysRe-scope IAM roles · enable session-binding on SSO

    Full technical detail and AI-actionable fixes ship in the engineer's companion report.

    1. 01
      Business framing

      One paragraph, in plain business language — what we tested and what an attacker could reach.

    2. 02
      Blast-radius KPIs

      Materiality, revenue at risk, time-to-fix, and the SOC 2 controls impacted (auditors typically pull this block, the findings register, and the retest letter as Type II evidence) — the numbers a board actually asks for.

    3. 03
      Plain-terms attacks

      Three attacker narratives written for non-engineers. No CVEs, no jargon — just what a real adversary could do.

    4. 04
      Fix-by-when order

      Prioritized remediation with immediate / 30-day / 60-day windows, so leadership can commit a plan out of the meeting.

    Artifact · 02 / Findings & posture

    Every finding, verified.

    Pen Test Report · Excerpt
    Engagement #PT-26-014
    01 / Findings

    What we found.

    • Authenticated RCE via deserializationPT-2026-014
      api.client.example.com · Verified · PoC delivered
    • Privilege escalation via misconfigured IAM rolePT-2026-021
      aws · prod-acct · Exploited in lab
    • Session fixation on SSO callbackPT-2026-027
      auth.client.example.com · Reproduced
    • Stored XSS in admin notes fieldPT-2026-033
      admin.client.example.com · Reproduced
    • Verbose error disclosure on 500 responsesPT-2026-041
      Multiple endpoints · Informational
    02 / Engagement

    Posture at a glance.

    6/ 23
    Exploited of Total · PoC Delivered
    Severity MixCritical-led
    1C4H9M9L
    Status
    Sample engagement
    D1 to D9
    Engineers
    2 + model-assisted
    Methodology
    Gray-box
    Report
    Delivered May 13
    1. 05
      Severity + PoC evidence

      Every finding has a working proof-of-concept and a status of Verified, Reproduced, or Informational. Every finding manually validated.

    2. 06
      Severity mix bar

      One-glance view of critical-led vs. noise-heavy engagements. Critical and High findings always sit at the top.

    3. 07
      Engagement KPIs

      Exploited-of-total tells you how much of what we found we could actually chain into impact — the honest signal of engagement quality.

    4. 08
      Methodology tag

      Window, engineer count, and methodology (gray-box / black-box / white-box) — traceability for procurement and auditors.

    Artifact · 03 / Sample engagement

    Sample engagement, kickoff to board-ready delivery.

    Sample engagement · D1 → D9
    Seven steps · no shortcuts
    1. 01

      Plan

      Scope the pen test and map to MITRE ATT&CK.

      We agree pen-test scope, rules of engagement, and success criteria, then map every objective to MITRE ATT&CK so coverage is measurable from day one.

    2. 02

      Recon

      OSINT + active surface inventory.

      Passive OSINT and active discovery build a complete inventory of your external attack surface — domains, subdomains, exposed services, leaked credentials, and third-party footprints.

    3. 03

      Hunt

      Our AI-augmented pen-test team hunts web, API, cloud, identity, and business-logic surfaces in parallel.

      Our AI-augmented pen-test team hunts in parallel across web, API, cloud, identity, and business-logic surfaces — covering ground a traditional pen-test team would have to serialize across weeks.

    4. 04

      Validate

      Human experts confirm every finding with a working proof-of-concept.

      Nothing reaches your report without a working proof-of-concept reviewed by a human pen-tester. Scanner noise, theoretical risks, and unreachable bugs are eliminated before they ever land on your desk.

    5. 05

      Chain

      Isolated bugs linked into real attack paths with composite risk scores.

      Individual findings are stitched into the attack paths an actual adversary would walk, with composite risk scores reflecting real-world exploitability — not CVSS in a vacuum.

    6. 06

      Detect

      We hand blue teams the Sigma rules to catch each technique.

      Each validated technique ships with a Sigma rule your blue team can drop into their SIEM, turning every pen-test finding into durable detection coverage.

    7. 07

      Report

      Board-ready pen-test report: severity badges, attack chains, prioritized roadmap.

      A board-ready pen-test report with executive narrative, severity badges, attack-chain diagrams, evidence, fix-and-verify steps, and an AI-actionable companion file for your engineers.

    Detection handoff

    Every engagement ships Sigma rules for the SOC and an AI-actionable companion file for engineering — so findings turn into detections and fixes the same day the report lands.

    Free retest

    Remediated findings get a free retest within 60 days. The report is updated with verified-fixed status your auditor can use as evidence.

    1. 09
      D1–D9 cadence

      Kickoff, recon, hunt, validate, chain, detect, report — the seven-step pipeline every engagement follows, with dates and owners.

    2. 10
      Sigma detection handoff

      The report ships with Sigma rules for your SOC and an AI-actionable companion file for engineers — findings become detections and fixes the same day.

    What's in the report

    Six sections, no filler.

    01CoverEngagement metadata, methodology, classification, and delivery date.
    02Executive summaryThe blast-radius KPIs, plain-terms attacker narratives, and fix-by-when order — one page for the board.
    03Findings listEvery finding with severity, CWE, CVSS, status, and evidence pointers.
    04Fully-worked findingOne critical, end-to-end: target, PoC request, impact narrative, and a fix with a verification step.
    05Sigma detection rulesCopy-paste rules for your SIEM so the SOC can detect the attack you just saw exploited.
    06Engagement timelineD1–D9 mapped to activity and evidence — the audit trail your assessor already expects.

    Sample report FAQ

    What a good pen test report actually includes.

    A good pen test report has two audiences and three jobs. For the board: a one-page executive summary that names the business risk in plain language, quantifies revenue and audit impact, and gives a prioritized fix-by-when order. For engineering: every finding with a working proof-of-concept, a clear impact narrative, and a concrete fix with a verification step — not just a scanner dump. And it should ship with detection artifacts (Sigma rules or equivalents) so your SOC can spot the same attack the next time. If a report only lists CVEs and CVSS scores, it is a scanner output, not a pen test report.

    No. The engagement number, target hostnames, revenue figure, and finding details are illustrative — real customer engagements are covered by NDA and never leave client environments. The report structure, artifact layouts, evidence format, and Sigma-rule delivery match exactly what you receive on a real TitanDef.ai engagement.

    Yes. Under our white-label program for MSPs and MSSPs, the report is delivered on your letterhead — your logo, your colors, your engagement numbering — with our methodology and evidence-quality guarantees behind it. See the MSSP page for wholesale pricing.

    Full report

    Want the full report as a PDF?

    Leave your email and we'll send the complete sample deliverable — executive summary, findings register, Sigma rules, and timeline. Or email saurabh@titandef.com.

    or email saurabh@titandef.com

    Next step

    Get a report like this on your own environment.

    Thirty-minute scoping call. Fixed-scope quote within one business day. Focused engagements in 5 to 7 business days. First findings within 72 hours of kickoff.