# One finding per issue, whichever tool found it

Import from the scanners your team already runs, then correlate what they report into a single finding per issue. Each tool’s evidence is kept and attributed. Manual findings sit in the same list, in the same shape.

_stage 4 of the engagement._

## More from Tandera

- [Tandera](https://tandera.io/): Pentest operations platform — scope to retest
- [About](https://tandera.io/about)
- [Attack chains](https://tandera.io/attack): Chain findings into attack narratives
- [Blog](https://tandera.io/blog)
- [Changelog](https://tandera.io/changelog)
- [Compare](https://tandera.io/compare)
- [Contact](https://tandera.io/contact)
- [Docs](https://tandera.io/docs)
- [Integrations](https://tandera.io/integrations): Every supported security tool, generated from the parser registry
- [Client portal](https://tandera.io/portal): Share results with clients
- [Privacy policy](https://tandera.io/privacy)
- [Recon](https://tandera.io/recon): Automated attack-surface discovery
- [Reports](https://tandera.io/reports): White-label pentest report generation
- [Security](https://tandera.io/security)
- [Solutions](https://tandera.io/solutions)
- [Terms](https://tandera.io/terms)
- [Tools](https://tandera.io/tools)

---

Canonical: https://tandera.io/findings
This page as markdown: https://tandera.io/findings.md
Index for agents: https://tandera.io/llms.txt

Every page here is also available as markdown: append `.md` to the path (e.g. `/recon.md`, `/index.md` for this homepage, `/blog/<slug>.md`), or request the canonical path with `Accept: text/markdown`.