Domain 1Recon & ReportingCORE

Importance of Reporting in Penetration Testing

Foundational chapter explaining why reporting is the core deliverable of penetration testing, how it bridges technical findings to business decisions, and the key stakeholders who consume different parts of the report.

Domain: Domain 1: Reconnaissance & Reporting•Updated: 2026-09-01
#reporting#communication#stakeholders#business-impact#oscp-exam

OSCP Report Writing: Importance of Reporting in Penetration Testing

1. Why Reporting Matters

The Report IS the Deliverable

In penetration testing, the actual hacking is merely the means to an end. The report is the product the client pays for and the artifact that creates lasting value. This principle cannot be overstated:

  • A perfect hack with a poor report = failed engagement. Even if you achieve full domain compromise, if you cannot document what you found, how you found it, and how to fix it, the engagement has failed.
  • The report is the only lasting artifact. After the engagement ends, the tools are packed up, the access is removed, and the only thing remaining is the report.
  • The report justifies the investment. The client’s management team needs to see the return on their penetration testing budget. The report provides that justification.

The OSCP Exam Context

For the OSCP exam specifically, the report carries significant weight:

  • The exam consists of two components: the practical penetration test (24-hour window) and the written report (submitted within 1 working day after closing the exam).
  • You can pass the practical portion but fail the exam due to a poor report. Offensive Security has a strict grading rubric for reports.
  • The report must demonstrate that you understand what you exploited, why it was vulnerable, and how to remediate it.
  • Plagiarism is strictly enforced. All content must be your own original work.

Exam Tip: Many candidates underestimate the report. Spend at least 4-6 hours on your report. Start drafting notes during the 24-hour exam window so you have raw material to work with.

The Reporting Value Chain

The penetration testing process follows a clear value chain where reporting sits at the critical transition point between technical discovery and business action:

Reconnaissance → Exploitation → Evidence Collection → Analysis & Triage → Report Writing → Remediation Guidance → Risk Reduction

Each stage feeds into the next. The report is the bridge that converts raw technical data into actionable business intelligence.

Beyond technical value, the report serves important legal and compliance functions:

  • Legal documentation: It records the scope, rules of engagement, and activities performed during the test. This protects both the tester and the client.
  • Audit trail: External auditors (SOC 2, ISO 27001, PCI-DSS) require evidence of regular security testing. The report is that evidence.
  • Regulatory compliance: Many regulations (GDPR, HIPAA, PCI-DSS) mandate periodic penetration testing with documented results.
  • Liability protection: A future breach occurs, the report demonstrates due diligence was performed.

2. Key Stakeholders Who Read Your Report

Understanding your audience is the single most important skill in report writing. Different stakeholders need different information presented in different ways.

Stakeholder Breakdown

Stakeholder What They Care About Report Section Reading Depth
CISO / Security Director Overall risk posture, budget justification, compliance status Executive Summary Full read of exec summary, skims technical
CTO / IT Director Technical impact, remediation effort, resource requirements Executive Summary + Technical Overview Reads exec summary, reviews high-severity findings
System Administrators Specific vulnerabilities on their systems, exact fix steps Technical Findings Reads only findings relevant to their systems
Developers Code-level issues, patch details, secure coding guidance Technical Findings + PoC Reads findings affecting their applications
Legal / Compliance Audit trail, regulatory alignment, scope boundaries Full Report + Appendices Reviews scope, legal disclaimers, compliance mapping
External Auditors Evidence of due diligence, methodology soundness Full Report Reviews methodology, evidence, conclusions
Board Members Business risk, financial exposure, strategic direction Executive Summary (first page only) Reads only the first 1-2 pages

Writing for Multiple Audiences

The challenge is that a single report must serve all these audiences simultaneously. The solution is layered reporting:

  1. Layer 1 (Executive Summary): Written for non-technical leadership. Focuses on risk, impact, and business consequences. Uses plain language without jargon.
  2. Layer 2 (Technical Overview): Written for technical management. Provides context about the testing methodology, scope, and overall technical findings.
  3. Layer 3 (Technical Findings): Written for engineers and administrators. Contains detailed technical information, PoC code, exact commands, and specific remediation steps.
  4. Layer 4 (Appendices): Written for auditors and reviewers. Contains raw data, tool output, and supporting documentation.

The Audience Awareness Test

Before writing any section of your report, ask yourself:

“If I were [target stakeholder], what would I need to know to make a decision?”

For example:

  • As a CISO: “What is the biggest risk? How much will it cost to fix? What should I prioritize?”
  • As a Developer: “What exactly is wrong with my code? How do I fix it? Can you show me the vulnerable line?”
  • As an Auditor: “Was the testing methodology sound? Is there evidence to support each finding?”

3. Critical Concepts to Master

Business Impact Translation

The ability to translate technical vulnerabilities into business risk is what separates junior testers from senior consultants.

Technical Finding Business Impact Translation
SQL injection on login form “Attackers can access all customer data including names, emails, and payment information stored in the database”
CVE-2024-1234 in Apache Struts allows RCE “A known critical vulnerability with public exploit code allows complete server takeover, potentially compromising all hosted applications”
Weak TLS 1.0 configuration “Encrypted communications can be intercepted, exposing sensitive data in transit including login credentials and financial information”
Default credentials on admin panel “Any unauthorized user can access administrative functions without authentication, gaining full control over the system”
Unpatched Windows Server (missing 12 updates) “The server is missing critical security patches released over the past 6 months, leaving it exposed to multiple known exploits”

Actionability

Every finding in your report must have a clear, actionable remediation path. A finding without remediation is just an observation, not a deliverable.

Actionable remediation includes:

  • Specific steps to fix the issue
  • Reference to patches, updates, or configuration changes
  • Code examples showing the fix
  • Verification steps to confirm the fix works
  • Prioritization based on severity

Defensibility

Your report must withstand scrutiny from:

  • Auditors: Who will verify your methodology was sound
  • Legal teams: Who may use the report in litigation
  • Technical peers: Who may attempt to reproduce your findings
  • Management: Who will question the severity ratings and recommendations

To make your report defensible:

  • Document every step with evidence
  • Use industry-standard scoring (CVSS)
  • Reference authoritative sources (CVEs, CWEs, OWASP)
  • Maintain chain of custody for evidence
  • Be honest about limitations and scope

4. The Reporting Mindset

Shift Your Thinking

Many OSCP candidates approach reporting as an afterthought. The right mindset is:

Start thinking about the report from the moment you begin the engagement.

Practical implications:

  • Take screenshots as you work, not after
  • Copy command output to a notes file in real time
  • Document your thought process and decision-making
  • Record timestamps for all significant activities
  • Note failed attempts (they demonstrate thoroughness)

The Professional Standard

In the professional penetration testing industry, the report is typically:

  • 40-60% of the engagement effort. For a 5-day engagement, 2-3 days are spent on reporting.
  • Reviewed by multiple people. Senior testers review junior testers’ reports before delivery.
  • Presented to the client. A debrief meeting walks through the findings with the client’s team.
  • Followed up. Re-testing after remediation is common and requires referencing the original report.

5. Common Reporting Pitfalls for OSCP Candidates

Pitfall 1: Underestimating the Report

Many candidates spend 22 hours hacking and 2 hours writing. This is backwards. A good ratio is:

  • 24-hour exam: Focus on hacking, but document as you go
  • Report writing day: Dedicate the full day to writing, reviewing, and polishing

Pitfall 2: Copying from Sources

Offensive Security uses plagiarism detection. Common mistakes:

  • Copying exploit descriptions from Exploit-DB
  • Copying remediation advice from vendor advisories
  • Using AI-generated content without modification
  • Copying from classmates or online forums

Solution: Write everything in your own words. Reference sources, but never copy verbatim.

Pitfall 3: Missing Required Elements

The OSCP report template has specific required sections. Missing any of these can result in failure:

  • Executive Summary
  • Technical Findings for each machine
  • Proof of exploitation (screenshots)
  • Remediation recommendations

Pitfall 4: Poor Evidence Quality

Common evidence problems:

  • Screenshots that are too small or blurry
  • Missing the actual proof (e.g., showing the exploit command but not the result)
  • Not showing the flag capture (user.txt / root.txt)
  • Inconsistent screenshot naming

6. Practical Tips Summary

Tip 1: Before writing, ask yourself: “If I were the CISO, what would I need to know to make a decision?”

Tip 2: A good report should be understandable by a non-technical manager AND detailed enough for a senior engineer to implement fixes.

Tip 3: Start documenting during the engagement. Your future self will thank you when writing the report.

Tip 4: Use the Offensive Security provided template. Do not create your own format.

Tip 5: Write in past tense (“I exploited…” not “I will exploit…”).

Tip 6: Proofread your report at least twice. Grammar and spelling errors reduce professionalism.

Tip 7: Include the exact commands you ran. Copy from your terminal history.

7. Key Takeaways

  1. The report is the product. Hacking is the means; the report is what the client receives and what determines your success.
  2. Know your audience. Different stakeholders need different information at different detail levels.
  3. Translate technical to business. Convert vulnerabilities into business risk that leadership can act on.
  4. Be actionable. Every finding must have a clear remediation path.
  5. Be defensible. Document everything with evidence, use standard scoring, and reference authoritative sources.
  6. Start early. Begin documenting during the engagement, not after.
  7. Be original. Write in your own words. Plagiarism will result in exam failure.

8. Further Reading