Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/reporting-pentest-reportReporting and compliance

reporting-pentest-report

⁨Structure a professional penetration-test report (engagement deliverable, not a single bug). Load at the end of a pentest, on "write the pentest report", "executive summary", "deliverable", or compiling findings for a client. Signals: engagement wrap-up, multiple findings, client report.⁩

v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/reporting-pentest-report

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
zHGY0I7y4Y…EqlnazCQ==The CLI checks the SHA-256 and the signature before it writes a file.
Packagecbfd2055…a7331926
cbfd20556964…5e94a73319261 file · ⁦1.4 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/reporting/reporting-pentest-report@ee0e0c5

When it governs

End of a pentest engagement, when findings become a client deliverable. Different from a bug-bounty report (reporting-bug-bounty-writeup): this is the whole engagement — executive narrative plus detailed findings — read by both executives and engineers.

Structure

  1. Executive summary — non-technical: what was tested, overall risk posture, the 3–5 things that matter, and business impact. One page. No jargon.
  2. Scope & methodology — assets/IPs/apps in scope, dates, testing type (black/grey/white), standards followed (PTES/OWASP WSTG/NIST), and limitations.
  3. Findings — one per issue, ordered by risk. Each: title, severity (CVSS vector + rating), affected assets, description, reproduction steps (exact requests/commands), evidence (screenshots/output), impact (business terms), remediation (specific fix), references.
  4. Risk ratings — a consistent method (CVSS + likelihood/impact matrix); explain it.
  5. Remediation roadmap — prioritized, with quick wins vs strategic fixes; owners/timelines if known.
  6. Appendices — full tool output, methodology detail, out-of-scope notes, retest results.

Quality bar

  • Reproducible: an engineer can follow each finding from a clean state.
  • Two audiences: executives read the summary; engineers read the findings — serve both.
  • Actionable remediation: name the specific fix (parameterize the query, enforce object-level authz), not "sanitize input" (see defense-hardening-baseline).
  • Evidence hygiene: redact secrets/PII; store raw evidence securely; keep the client's data confidential.

Gotchas

  • Severity must reflect demonstrated impact in context, not the theoretical max.
  • Don't bury the critical findings under low-severity noise — lead with what matters.
  • Deliver the report over a secure channel; it's a map of how to break the client.

References

PTES; OWASP WSTG; NIST SP 800-115; FIRST CVSS 3.1.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5cbfd2055Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login