// Practical guide
How to pass a security due diligence
What technical security due diligence is
When serious money comes in (a round, an acquisition, a big enterprise customer), the other side sends someone to look under the hood. Security due diligence is that inspection: they want to know whether your product protects login, customer data and billing, or whether they are buying a liability. A serious finding here is not just embarrassment, it is a valuation discount or a cancelled deal.
The good news: due diligence rewards those who prepared. Showing up with the sensitive flows already tested and with evidence changes the conversation from "prove it is secure" to "here is the proof".
RET runs this test: a 25-hour Sprint for R$9,500, within 7 business days. See price and timeline for my case
What the buyer actually looks at
It is not a generic firewall checklist. In SaaS, the focus is what sustains revenue and customer trust.
- Access control: tenant isolation, IDOR, server-side authorization.
- Customer data: how it is stored, who accesses it, privacy law.
- Billing: signed webhook, server-side price, no unlocking a plan without payment.
- Secrets: no key in the client bundle or the repository.
- Incident history and how it was handled.
What kills the deal
Some findings scare a buyer disproportionately, because they signal a lack of maturity. Cross-tenant leakage is the worst (it breaks the central promise of a multi-tenant SaaS). An exposed secret in the front-end comes right after. And the absence of any security testing, even with no finding, already raises the "nobody looked at this" alarm.
How to show up prepared
Do not wait for due diligence to start to find out where you stand. A scoped Manual Pentest delivers the evidence report a buyer respects, and Risk Review is the cheaper read to find and fix the obvious first. Arriving with "we already tested, here is the report and the fixes" turns due diligence from a risk into a negotiation advantage.
Frequently asked questions
Do I need a pentest before the round?
Not mandatory, but it helps a lot. Arriving at due diligence with a pentest report and the fixes done changes the dynamic: instead of the buyer finding problems, you show you already solved them. That protects valuation and timeline.
What most kills a deal on the security side?
Cross-tenant leakage (multi-tenant), an exposed secret in the front-end, and the total absence of any testing. The first two are concrete findings; the third is a maturity signal that scares on its own.
Can I start cheap?
Yes. Risk Review reads 1 to 3 sensitive flows and tells you what to fix before due diligence. If the deal requires a formal report, the Manual Pentest delivers the evidence in the expected format.
Who runs it at RET?
Gabriel Lima Ferreira, founder and lead pentester, with an authorized scope and reproducible evidence.
Keep reading
Vulnerability and fix
IDOR in Stripe checkout
Vulnerability and fix
Secure file upload in SaaS
Practical guide
How to answer a customer security questionnaire
Comparison
Firebase vs Supabase: security for AI-built apps
By tool
Security for code generated with Cursor
By city
SaaS security and pentest in Brasília (DF)