Report format · Fictional training scenario

Illustrative sample report.

Not a real finding · No target tested

This redacted-style example demonstrates how an observed issue should be documented. The organization, endpoint, evidence and scenario below are fictional and were not tested or reproduced.

Engagement summary

Example client: [REDACTED — fictional]

Target: [TRAINING-ONLY PLACEHOLDER]

Authorization / test window: Illustrative only; no engagement occurred

Assessment method: None. This is a writing sample, not test evidence.

Overall status: Not assessed

Simulated example · Do not treat as a result

EX-01 · Missing login throttling (fictional scenario)

Severity: Example only — severity cannot be assigned without validating the affected system, controls and business context.

Scenario: Suppose a test environment permitted repeated password attempts without delay, lockout, bot mitigation or alerting. No such behavior has been observed on a real or portfolio system.

Potential impact

If this condition were confirmed on a real service, automated guessing could increase the chance of account compromise, especially where users reuse weak passwords. Actual likelihood and impact would depend on authentication controls, MFA, monitoring and account sensitivity.

Recommended fix

Evidence

[No request/response, screenshot, endpoint or reproduction steps are supplied. An actual report must contain minimal sanitized evidence collected under written authorization.]

This example is intentionally hypothetical. It must not be quoted as an identified vulnerability, client result, or security audit of karan-portfolio-dmh.pages.dev.

What a real redacted report will include

  1. Written scope, authorization, dates, exclusions and stop conditions.
  2. Executive summary and limitations.
  3. Only reproduced findings, with sanitized evidence, impact, severity rationale and actionable fixes.
  4. Retest status separated from initial results.
  5. Removal of client names, IPs, credentials, personal data and sensitive system identifiers before sharing.
Read the local lab boundaries