Gaining initial access (see exploitation-concepts) is rarely the actual goal of an engagement — it’s a foothold. Post-exploitation is about determining what that access actually means in terms of real business impact, and reporting is where that impact gets communicated in a way the target organization can actually act on. This is arguably the most important phase professionally: a finding that never gets fixed because the report was unclear delivered no real value at all.

What post-exploitation actually investigates

  • Privilege escalation — can initial, limited access be escalated to a higher privilege level (from a regular user to an administrator, for instance)? Often exploits a second, separate weakness from whatever provided initial access.
  • Lateral movement — can the foothold be used to reach other systems on the network that weren’t the original entry point? This is what turns “one server was vulnerable” into “the entire internal network was reachable from one server.”
  • Data access — what sensitive data is actually reachable from this position, concretely? This is what separates a low-impact finding from a critical one — the same technical vulnerability can have wildly different real-world severity depending on what it actually exposes.
  • Persistence (in a red-team context specifically) — could an attacker maintain access even after the initial vulnerability is patched? Tested specifically to evaluate detection and incident response, not as a default step in every engagement.

Why “we got in” is an incomplete finding

A report that just says “we gained access via X” without following through on impact leaves the target organization unable to properly prioritize the fix. “We gained access via a default password on a printer’s admin panel, and from there reached the finance department’s file share containing unencrypted payroll data” is a fundamentally more useful, actionable finding than “the printer had a default password” — the same root cause, but the second version tells the organization nothing about why it matters.

Anatomy of a good report

  • Executive summary — a non-technical overview of overall risk and the most critical findings, written for people who make budget/priority decisions, not technical staff.
  • Findings, ranked by severity — each with a clear description, the actual business impact (see cia-triad for the vocabulary), steps to reproduce, and evidence (screenshots, logs).
  • Remediation guidance — specific, actionable fixes, not just “patch this” — the whole point of the exercise is enabling a fix, not just recording that a problem exists.
  • Methodology and scope — what was tested, what wasn’t, and how, so the organization understands the boundaries of what the engagement actually covered (and, just as importantly, didn’t).

Severity ratings

Findings are typically ranked (critical/high/medium/low, or using a scoring system like CVSS) based on a combination of exploitability (how easy is this to actually pull off) and impact (what happens if it’s exploited) — directly the “likelihood × impact” risk framing from what-is-cybersecurity. A trivially exploitable issue exposing critical data is critical; a hard-to-exploit issue with minor impact is low, and most findings sit somewhere between.

Responsible disclosure (outside a formal engagement)

When a vulnerability is found outside a scoped engagement (independent security research, a bug bounty program), responsible disclosure means privately reporting it to the affected organization first, giving them reasonable time to fix it before any public disclosure — as opposed to publishing details immediately, which can hand attackers a working weakness before a fix exists. Most organizations with a security program publish a disclosure policy and, increasingly, run structured bug bounty programs specifically to make this process clear and legally safe for researchers.

Gotchas

  • A report itself is highly sensitive — it’s effectively a detailed map of an organization’s weaknesses, and needs to be handled, stored, and transmitted with commensurate care (encrypted delivery, restricted access) rather than treated as an ordinary document.
  • Overstating severity to seem more impressive, or understating it to seem less alarming, both undermine a report’s usefulness — accurate, well-justified severity ratings are what let an organization prioritize correctly across many findings.
  • The engagement isn’t actually done when the report is delivered — a retest to confirm fixes were properly applied (not just superficially patched) is standard practice and often contractually included.
↑ Back to Ethical Hacking