Servana

Application security

Web application security testing

We test your web applications the way an attacker would: logins, permissions, data, and the business logic only your app has.

Who it's for.

Who it's for

  • SaaS companies whose customers ask for a recent penetration test
  • Businesses launching a new web app, customer portal or major release
  • Teams handling payments, personal information or other sensitive data online

What we test.

What we test

  • The OWASP Top 10

    Injection, cross-site scripting, broken access control and the rest of the most common web flaws.

  • Authentication

    Logins, password resets, multi-factor authentication and sessions.

  • Access control

    Whether one user can see or change another user's data.

  • Business logic

    Flaws specific to how your app works, like skipping a payment step.

  • Data handling

    How your app stores, sends and exposes sensitive information.

  • Configuration

    Headers, cookies, error messages and the server your app runs on.

What you get.

Included with every engagement

  1. 01

    Scope and rules of engagement

    What's in scope, when we test and how, agreed in writing before we start.

  2. 02

    Executive summary

    What we found and what it means for the business, in plain English.

  3. 03

    Technical findings

    Each issue with its severity, evidence and steps to reproduce it.

  4. 04

    Remediation guidance

    Practical fixes, in order of priority, that your team can act on.

  5. 05

    Debrief

    A walkthrough of the findings with the people who'll fix them.

  6. 06

    Retest

    Confirmation that what you fixed is actually closed.

From first call to fixed.

How it works

  1. 01

    Scoping call

    We learn what you want tested, why, and by when.

  2. 02

    Quote and authorisation

    A fixed quote, the exact scope and the rules of engagement, signed off in writing before we touch anything.

  3. 03

    Testing

    We test within the agreed window, and tell you straight away if we find something critical.

  4. 04

    Report

    A plain-English summary for leadership, and technical detail and fixes for your team. Every finding ranked by risk.

  5. 05

    Debrief

    We walk the people fixing things through the findings and answer their questions.

  6. 06

    Retest

    Once you've fixed the findings, we test again to confirm they're closed.

Frequently asked questions.

FAQ

Do you test as a signed-in user?

Yes, usually. We test as an outsider and as signed-in users with different roles, because the most serious flaws are often behind the login. You give us test accounts for each role.

Should we test production or staging?

A staging environment that matches production is often the safest choice. If we test production, we agree what's off limits and when we test, before we start.

Do you test the API behind the app too?

Most web apps run on an API, so the two often go together. If you need both, we scope them as one engagement.

Do you need our permission to test?

Always, in writing. We only test systems you own or are authorised to have tested, and the scope is signed off before we start. In South Africa, testing a system without permission is a crime under the Cybercrimes Act, and we won't do it.

How much does it cost?

You get a fixed quote after the scoping call, based on what's in scope. No hourly billing.

Find the gaps before someone else does.

Tell us what you'd like tested and when you need the report. You'll get a clear scope and a fixed quote.