What's included

  • Authentication, authorization and session handling.
  • Input handling and injection.
  • Use of cryptography and handling of secrets.
  • Dependencies with known vulnerabilities.
  • A review of the most sensitive changes before a release, if you need it.

What you get

  • Findings with the file and line, why it's a problem and how to fix it.
  • Recurring patterns your team can avoid from now on.

Who it's for

  • Teams preparing a release that handles sensitive data.
  • Code written quickly that never had a security review.

Not included

  • Fixing the code myself (it can be quoted separately).
  • General code quality reviews unrelated to security.

Process

How I work

  1. Scope and authorization

    We define what to test, how and when. Nothing starts without your written authorization.

  2. Testing

    Manual testing and review, supported by tools. If I find something critical, I tell you right away.

  3. Report

    You get every finding rated with CVSS v4.0, with the steps to reproduce it and the recommended fix.

  4. Follow-up

    I walk your team through the results and answer questions while you apply the fixes.

Frequently asked questions

Which languages do you review?

Go is where I work every day; I also read Python, JavaScript and other common languages. Tell me your stack when you write and I'll confirm.

Have a system to test or review? Send me the scope

Tell me what you need tested (applications, APIs or environments), by when, and any constraints, and I'll reply with the next steps. I work in English and Spanish.

Looking for development? Websites, applications and backend projects go through RyuLabs.