Vai al contenuto
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
aeondave/report-generation-techniqueReport e compliance

report-generation-technique

⁨Assessment and bug-bounty reporting: executive summaries, single-finding submissions, CVSS, evidence chains, MITRE ATT&CK mapping, remediation, and review-ready structure.⁩

v2026.11.13-21cd5683 installazioni+3 in 7 giorni39 StelleMITsincronizzato 10 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/report-generation-technique

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
FqbXlxEfKg…i5ySxmCg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto7a0c94c7…a597aff8
7a0c94c7755e…d99ba597aff81 file · ⁦2.6 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/offensive-techniques/report-generation-technique@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

Goal: produce professional penetration test reports that meet industry standards and satisfy both technical and executive audiences.

When this technique applies

  • Need to compile pentest findings into a structured report.
  • Writing executive summaries or detailed technical findings.
  • Creating attack narratives or remediation guidance.
  • Preparing a single-finding submission under a bug-bounty or VDP program.

Initial triage

Before writing, classify the deliverable and the evidence maturity so the report structure matches the engagement outcome.

  • Starting state: are you producing an executive summary, a full technical report, an interim findings memo, or a single-finding writeup?
  • First questions: who is the audience, what evidence is already validated, what findings are report-ready, and what methodology/scope context must be stated up front?
  • Immediate actions: sort findings by severity and confidence, identify missing proof or remediation details, and build the report skeleton before prose.
  • Tool-family direction: this technique mostly coordinates evidence and structure; pull from the relevant technique/tool outputs rather than inventing new tooling here.
  • Escalation rule: do not polish narrative before confirming evidence quality, scope statements, and remediation ownership.

Bug-bounty / VDP intake and submission

  • Before target activity, consult the selected program's current official policy and submission portal. Record program and asset eligibility, relevant exclusions or testing restrictions, disclosure route, and required fields; do not infer platform defaults or carry rules across programs.
  • For a validated finding, populate the current required fields and category, check applicable duplicate and disclosure rules, and submit only through the designated channel. Track the report ID and status; answer triage follow-ups with requested clarifications and stay within the program's disclosure terms.

Boundary with other skills

  • Evidence production: the relevant offensive or analysis technique should already have produced validated findings and artifacts.
  • Writing support: use behaviours/evidence-before-claims/ and behaviours/verification-before-completion/ logic when a finding is not yet report-ready.

Report structure

1. Cover page

text
[CLASSIFICATION LEVEL]
Penetration Test Report
[ENGAGEMENT TITLE]

Client: [CLIENT NAME]
Assessment Dates: [START DATE] -- [END DATE]
Report Date: [REPORT DATE]
Assessor(s): [ASSESSOR NAME(S)]
Report Version: 1.0
Distribution: [DISTRIBUTION LIST]

2. Executive summary

  • Written for non-technical leadership (C-suite, board members, risk committee).
  • 1-2 pages maximum.
  • Overall risk rating with justification.
  • Key statistics: total findings by severity, systems tested, critical issues.
  • Top 3-5 findings summarized in business impact terms.
  • Strategic recommendations (business decisions, not technical fixes).
  • Comparison to previous assessment if applicable.

3. Scope and methodology

  • Systems, networks, and applications in scope (with IP ranges, URLs).
  • Explicitly stated exclusions.
  • Testing approach and methodology (PTES, OWASP, custom).
  • Testing window and any constraints.
  • Tools used (with versions).
  • Limitations encountered during testing.

4. Findings summary table

ID Finding Severity CVSS Affected Systems Status

Sorted by severity (Critical to Informational).

5. Detailed findings

Each finding:

markdown
### [ID] -- Finding Title

**Severity**: Critical | High | Medium | Low | Informational
**CVSS**: X.X (v4.0 or v3.1 vector, e.g. CVSS:4.0/AV:X/AC:X/AT:X/PR:X/UI:X/VC:X/VI:X/VA:X/SC:X/SI:X/SA:X or CVSS:3.1/AV:X/AC:X/PR:X/UI:X/S:X/C:X/I:X/A:X)
**CWE**: CWE identifier and name, when applicable.
**Affected Systems**: [IP/hostname/URL list]
**MITRE ATT&CK**: TXXXX -- Technique Name

#### Description
What the vulnerability is, where it exists, and the technical root cause.

#### Evidence
[Screenshot placeholder: evidence-XX.png]
[Redacted proof-of-concept details]

#### Impact
Business impact: what an attacker could achieve.

#### Remediation
1. Immediate mitigation
2. Root cause fix
3. Preventive measures

#### Verification
How to confirm the fix was applied correctly.

#### References
- CVE-XXXX-XXXXX
- Relevant CWE identifier, if applicable

6. Attack narrative (optional)

Chronological walkthrough: initial access, privilege escalation, lateral movement, objective completion. Mapped to MITRE ATT&CK at each step.

7. Remediation priorities

Group fixes by effort and impact:

  • Quick wins (low effort, high impact).
  • Strategic fixes (architectural changes).
  • Compensating controls (interim measures).

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.11.13-21cd56813 nov 202621cd5687a0c94c7Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login