Interpreting PoC artifacts
Read every Pentrova finding: the captured exchange, the sandbox proof where there is one, the chain steps, and the evidence for auditors, secrets masked.
Every finding in your queue was confirmed by AI review of evidence captured from your target. This guide walks through what a finding can include so you know what to read first and what to forward to engineering.
What a finding includes#
- Captured exchange — where the finding has one, the HTTP request and response that demonstrate the issue. Copy it as a cURL command or raw HTTP and re-send it from any standard client, or, on paid plans, download it as Markdown or HAR.
- Sandbox output — for findings where the sandbox proof-of-concept check retrieved a proof (attempted for confirmed Critical and High findings in the classes it supports), the captured output (for example, the result of
idorhostnameon an RCE finding) with the secrets Pentrova recognises (passwords, tokens, API keys and session values) masked. Personal data is not removed, so treat it as sensitive. - Impact and remediation — the impact statement, the relevant compliance mappings, and a remediation hint.
Sandbox output#
For a remote-code-execution finding, the captured output is the first place to look — if the exploit produced id, uname -a, or a tracked marker string, the output shows it verbatim, with recognised secrets masked.
$ id
uid=33(www-data) gid=33(www-data) groups=33(www-data)
$ cat /etc/hostname
app-staging-7f3b
Captured exchanges#
Each step of a finding (or a chain) includes the request Pentrova sent and the response it received, as raw HTTP — method line, headers, body — so you can re-send it yourself. Chain steps are ordered so the path reads top to bottom.
Re-checking after a fix#
Where the finding has a captured request, copy it as cURL and re-send it against the patched build. If the issue no longer shows, the fix worked, and confirming it did not need Pentrova’s tooling. To have Pentrova check again, run a retest; how many retests your plan includes is on the pricing page. Otherwise, run a new pentest of the target.
What to forward first#
For most triage conversations, forward the captured exchange for the terminal step plus the impact statement. That is the minimum an engineer needs to understand the impact and start a fix; the rest is there when someone asks for more detail.