Skip to main content

Process

Check, find, close, seal

The four actions in our logo are the work itself. At every step, you know in advance what will happen and what we need from you.

  1. 01 / 05

    Request and NDA

    What we need from you
    A link to the product or its files, the expertise deadline, a contact person.
    What we do
    We define the requirements, prepare the NDA and agree on access rights.
    Result
    A signed NDA and a testing plan.
  2. 02 / 05

    Automated and AI scan

    What we need from you
    Read-only access to the repository, server or APK/IPA.
    What we do
    A Claude AI agent reviews the code, configuration, dependencies, headers and server; automated scanners run.
    Result
    An initial list of findings.
  3. 03 / 05

    Manual review

    What we need from you
    Test accounts (one for each role).
    What we do
    A specialist manually tests business logic, authorization, IDOR and file uploads, and confirms or rejects the AI findings.
    Result
    Confirmed findings, with evidence and severity.
  4. 04 / 05

    Fixes

    What we need from you
    Review the fixes or apply them yourself.
    What we do
    We prepare a patch or PR; if needed, we write clear instructions for your team.
    Result
    Closed vulnerabilities.
  5. 05 / 05

    Re-scan and report

    What we need from you
    A new build or deployment.
    What we do
    We re-check everything and prepare the APK/IPA checksums.
    Result
    A readiness report — ready for submission to the expertise.

Standards we rely on

The official expertise relies on the same standards. So we speak the same language.

  • OWASP Top 102021
  • OWASP ASVSWeb
  • OWASP MASVSMobile
  • OWASP MASTGMobile
  • MASWEMobile
  • OWASP Mobile Top 102024
  • CWEWeakness

Show us before you submit to the expertise

Leave a request: we scan your product and show exactly where the risks are and what it takes to close them.

Request a scan