An Attacker Doesn't See Three Reports. They See a Path.
Scanners score findings one at a time. Pentesterra correlates network, web, API, code, and OSINT results into multi-step attack chains - mapped to MITRE ATT&CK, scored for business impact, backed by real exploit verification, and re-checked after every fix.
How it works
Cross-domain correlation
The engine pulls findings from every source - network scan, web and API pentest, code analysis, OSINT - and builds a graph of how they connect. A medium on a VPN, an info on an admin API, and a low on a build runner become one path from the internet to the database.
- →Network + web + API + code + OSINT findings in one graph
- →The artifact from step one is the input to step two
- →Not a list of vulnerabilities - realistic exploitation routes
- →Recomputed on every assessment cycle
MITRE ATT&CK mapped
Every node in a chain is mapped to an ATT&CK tactic and technique - initial access, execution, privilege escalation, lateral movement, impact - so the path reads the way a defender's playbook is organized.
- →Per-node tactic and technique mapping
- →Phase view from initial access to business impact
- →Aligns with detection and response coverage
- →Chain diff between cycles: new, closed, changed
Business impact and compliance context
A chain that ends at a payment database matters more than one that ends at a marketing microsite. Each path is scored for business impact and mapped to the compliance frameworks it touches, so the report leads with priority, not volume.
- →Business-process and asset-criticality scoring
- →Compliance mapping: OWASP, PCI-DSS, GDPR, NIST, ISO
- →Executive summary plus the single highest-leverage fix
- →Patch-first queue driven by validated, chained risk
Powered by real verification
Chains are built from verified findings, not CVSS guesses. Where a step is exploitable, the engine has a proof of concept. After a fix lands anywhere on the path, the whole chain is re-run to confirm it is actually broken.
- →Every chain step backed by exploit verification
- →Regression detection when a fixed step reopens
- →Before / after evidence per path
- →Feeds the fix-revalidation loop
FAQ
What is attack chain analysis?
It is the process of correlating individual security findings into multi-step attack paths - showing how an attacker moves from an entry point through several weaknesses to a high-value target - instead of treating each finding as an isolated ticket.
How is it different from a vulnerability report?
A vulnerability report scores each finding independently. Attack chain analysis models the artifact an attacker carries between steps - a shell, a token, a session - so a set of low and medium findings can add up to a critical path that no single score reflects.
Which sources feed the chains?
Network scanning, web and API penetration testing, code and supply chain analysis, and OSINT. If a module has a finding, the chain engine can use it.
Does it re-check after remediation?
Yes. When a fix is applied anywhere on a chain, the engine re-runs the whole path and reports whether it is genuinely broken, and it raises a regression alert if a previously closed step reopens.