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 instalaciones+3 en 7 días39 EstrellasMITsincronizado hace 10 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/report-generation-techniqueEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete7a0c94c7…a597aff8
7a0c94c7755e…d99ba597aff81 archivo · 2.6 KBEscaneoBajosin hallazgos
Fuentegithub.com/AeonDave/malskill/tree/main/offensive-techniques/report-generation-technique@21cd568
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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/andbehaviours/verification-before-completion/logic when a finding is not yet report-ready.
Report structure
1. Cover page
[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:
### [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 applicable6. 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).
Archivos de esta versión
- SKILL.md5.1 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 nov 2026 | 21cd568 | 7a0c94c7 | Firmada | – |
Más de AeonDave
Todo de este publicadorMás en Informes y cumplimiento
Ver la categoría- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login