Skip to content

Founder

Senior pentest without theater.

I review production SaaS with the judgment of someone looking for real impact: where login, billing, data, and permissions can become lost revenue, exposure, or a blocked B2B sale. No jargon: evidence, priority, and fixes a founder can act on.

  • CompTIA PenTest+ specialization
  • Mutual NDA the same day
  • 25-hour Sprint for R$9,500
  • Yearly test under Article 22-A
Gabriel L. Ferreira
Lead Pentester
FOUNDER • LEAD PENTESTER • SAAS

Senior pentester: Gabriel L. Ferreira, RET founder

I review SaaS as a senior pentester who understands products in production. I look for where login, billing, data, or access can become revenue loss, exposure, or a blocked B2B deal.

Gabriel L. Ferreira

Founder & Lead Pentester

// Training

Courses and specializations, with the issuer link.

These are completed courses, not certification exams. Each link opens the issuer verification page, with the name and date.

Security and penetration testing

Cloud

AI applications

Software engineering

// Who signs

The person behind every report.

I’m Gabriel L. Ferreira, founder and lead pentester at RET Tecnologia. I spend my days looking at production SaaS the way an attacker would: hunting for where login, billing, permissions, and data can turn into loss, exposure, or a blocked B2B sale. RET exists because building products with AI got fast, and reviewing what was built fell behind. I don’t come from security marketing; I come from breaking things with authorization and explaining, in plain language, what it costs. Every report carries my name because that’s how I trust my own work.

How I work

Proof, not theater

I don’t ship a scary list of alerts. I ship what breaks, why it matters in money or data, and what to fix first. If it can’t be reproduced, it isn’t a finding.

Always under authorization

Nothing is tested without signed scope, an agreed window, and a clear boundary of what won’t be touched. Serious security starts with rules of engagement, not surprises.

Founder language

The report is for a decision. I write for the business owner and the developer at once: no useless jargon, impact explained in terms of revenue, access, and trust.

Responsible disclosure

When I find something in research, I report it with minimal evidence and follow the fix. Public proof only with authorization from whoever was fixed.

The path

  1. 2010

    Solo developer

    I have worked as a solo developer since 2010.

  2. 2025

    RET as a company

    In July 2025 I opened RET TECNOLOGIA EM INFORMATICA LTDA (CNPJ 61.709.429/0001-47) to make that work professional.

  3. Roots

    Research and responsible disclosure

    I started in offensive security and research, reporting real flaws with minimal evidence and accountability. That’s where it became clear the problem is rarely an exotic exploit: it’s loose access control, a poorly drawn boundary, and a payment flow that trusts the client.

  4. Focus

    The AI-built SaaS gap

    Vibe coding made the MVP appear in days. But login, per-customer isolation, checkout, and permissions are still the part nobody reviews before selling. RET was born to close exactly that gap, with a human eye where automated tooling can’t reach.

  5. Method

    The Cascavel Framework

    I organized my way of hardening products into what I call Cascavel internally: a forensic hardening method that treats the application as a surface to be armored in layers (containment, isolation, and verification) instead of a generic checklist. It’s the backbone of every review and of how RET’s own site is built.

  6. Ladder

    An honest product ladder

    Instead of selling pentest to everyone, I built a ladder: Promptbook for the first paid review, AuditMySaaS to watch what changes, Risk Review for the human read that decides, and Manual Pentest to prove what breaks. Each rung escalates only when risk asks for it.

  7. Proof

    Find My SaaS, in public

    On Find My SaaS I reported three real flaws: an S3 upload, an inflatable metric with 564 simulated clicks, and an invalid social login on a sensitive route, with a public fix and acknowledgment from Mano Deyvin. It’s the external proof the method works off the slide.

Public work you can check

Recent articles

Why Cascavel

The name isn’t decoration. Cascavel (the pit viper) is the idea of a defense that warns before it bites: layers that contain, isolate, and verify, so a flaw in one spot doesn’t become total access. I apply it both to reviewing a client’s SaaS and to hardening this very site.

In practice, it means distrusting external context, requiring server-side ownership checks, isolating data per customer, and never letting "works in the demo" be mistaken for "holds real customers".

When it makes sense to call me

  • Before closing a B2B sale that depends on the customer trusting your security.
  • After a review or scan flagged a signal and you don’t know if it’s serious.
  • Before opening the product to many more users, when the cost of a mistake grows with it.
  • When a customer or investor asks for proof of security and you have nothing to show.

What guides me

I don’t promise total security. No one serious does. I promise to show what breaks, with evidence, priority, and a fix your team can actually apply. If your SaaS already has people paying, customer data, or a B2B proposal on the table, this is the moment to leave "it should be safe" behind.

If you want to see the work up close, the code and public research live on GitHub. To talk about scope, the path is the Pentest page.

Where to find me