Перейти к содержимому
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-techniqueОтчеты и соответствие требованиям

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 установки+3 за 7 дней39 ЗвездыMITсинхронизировано 10 часов назад

Установка

Ещё нет NotHoly CLI? Сначала установите её.

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

Пишет в ⁦~/.notholy/skills⁩ после проверки подписи и SHA-256.

ПодписьПодписано, ed25519
FqbXlxEfKg…i5ySxmCg==CLI проверяет SHA-256 и подпись, прежде чем записать хоть один файл.
Пакет7a0c94c7…a597aff8
7a0c94c7755e…d99ba597aff81 файл · ⁦2.6 KB⁩
ПроверкаНизкийзамечаний нет
Проверка не нашла в этой версии ничего подозрительного.Вся проверка
Источникgithub.com/AeonDave/malskill/tree/main/offensive-techniques/report-generation-technique@21cd568

Эта запись еще не переведена на русский, поэтому показан текст на другом языке: 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).

Файлы этой версии

Права

ПравоЗаявленоНайдено проверкой
Читает файлыНетНет
Пишет файлыНетНет
Выполняет команды shellНетНет
Ходит в сетьНетНет
Использует коннекторыНетНет
Управляет браузеромНетНет

Замечания проверки

Проверено 13 нояб. 2026 г.

Проверка не нашла в этой версии ничего подозрительного.

Чистая проверка снижает риск, но не доказывает, что пакет безопасен. Читайте то, что ставите.

ВерсияОпубликованаКоммитSHA-256ПодписьИзменение прав
v2026.11.13-21cd56813 нояб. 2026 г.21cd5687a0c94c7Подписана–

Спрашивайте обо всём, что позволяет ваш скоуп.

Создайте аккаунт, пополните баланс и задайте первый вопрос в чате или в терминале.

  1. 1/3

    Создайте аккаунт

    Личный или для компании. Позже можно перейти на аккаунт компании без потери баланса и ключей.

    ЛичныйКомпания
  2. 2/3

    Пополните баланс

    Картой. Оплата за токены, без подписки.

    $5.00минимальное пополнение
  3. 3/3

    Спрашивайте

    В чате, или установите CLI и выполните notholy login в терминале.

    $ notholy login