Servana

VAPT

Find the weaknesses before someone else does.

Vulnerability assessments and penetration tests for your networks, web applications and APIs. Done only with your written permission, with a plain-English report your team can act on.

Pick your test. We'll scope the rest.

What we test

Every engagement includes: a scoping call, written authorisation, a risk-ranked report with fixes, a debrief and a retest.

Assessment or penetration test? Wide, or deep.

Which test?

Most teams aren't sure which they need, and that's fine. Tell us what you're trying to achieve on the scoping call, and we'll recommend one, or both.

Vulnerability assessment

Wide. Finds the known weaknesses across everything in scope.

  • Answers: where are we exposed?
  • Checks every system in scope, then we verify the results
  • Ranks each weakness by real-world risk
  • Worth repeating regularly, and after big changes

Penetration test

Deep. Shows what an attacker could actually do.

  • Answers: how far could someone get?
  • Chains weaknesses together, the way a real attacker would
  • Proves the impact with evidence, safely and within agreed rules
  • Usually once a year, and after big changes

Pass a customer's security review: with a report they'll accept.

By need

Larger customers and partners often ask for a recent, independent penetration test before they sign. We scope the test around what they care about, and give you an executive summary you can share and the technical detail your team needs to fix things.

Meet a requirement: ISO 27001, PCI DSS and POPIA.

By need

ISO 27001 expects you to manage technical vulnerabilities. PCI DSS asks for regular vulnerability scans and penetration tests. POPIA requires reasonable security safeguards for personal information. Testing shows you actually check, not just that you have a policy. If we're also getting you ready for ISO certification, the findings go straight into your programme.

ISO 27001 readiness

Before you launch: test it before your customers do.

By need

A new app, an API for partners or a big release is the cheapest time to find a security flaw. We test before it goes live, so the fixes happen on your schedule, not after an incident.

After a big change: a migration, a merger or a new integration.

By need

Moving to the cloud, joining up two networks or connecting a new supplier changes what's exposed. A test afterwards tells you whether anything opened up along the way.

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

What's the difference between a vulnerability assessment and a penetration test?

A vulnerability assessment is wide: it finds and ranks the known weaknesses across everything in scope. A penetration test is deep: a tester tries to exploit weaknesses, chaining them together the way a real attacker would, to show how far someone could actually get. Not sure which you need? We'll recommend one, or both, on the scoping call.

How much does it cost?

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

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.

Will testing disrupt our systems?

We agree testing windows and rules of engagement with you first, and we avoid anything that could take a system down unless you've asked for it. If something looks fragile, we stop and talk to you before going further.

How long does it take?

It depends on the scope. You'll get a timeline with your quote, before anything starts.

What methodology do you follow?

Recognised ones: OWASP for web applications and APIs, and PTES and NIST SP 800-115 for networks. Findings are rated with CVSS, so a severity means the same thing to everyone reading the report.

Does testing help with ISO 27001?

Yes. ISO 27001 expects you to manage technical vulnerabilities, and a recent test is strong evidence that you do. If we're also getting you ready for certification, the findings feed straight into that work.

Will we talk to a real person?

Always. A named person runs your test and walks you through the report.

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.