Servana

Penetration testing

Internal penetration testing

We start inside your network, as a compromised laptop or a malicious insider would, and show how far someone could get.

Who it's for.

Who it's for

  • Businesses that want to know what happens if one laptop or account is compromised
  • Teams with sensitive systems that should be out of reach from the rest of the network
  • Companies preparing for a customer audit, PCI DSS or ISO 27001

What we test.

What we test

  • Privilege escalation

    From an ordinary user account to admin, and exactly how.

  • Lateral movement

    Moving from one machine to the next across your network.

  • Active Directory

    Attack paths through your directory, a common route to taking over a whole network.

  • Credentials and secrets

    Passwords and keys left where they can be found or reused.

  • Segmentation

    Whether your sensitive systems really are out of reach.

  • Sensitive data

    What someone inside could get to, shown safely and without copying it.

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

Where do you start from?

Usually from an ordinary employee's position: a laptop on your network with a standard account, because that's what an attacker has after one successful phishing email. We agree the starting point with you.

Why test from the inside if our perimeter is secure?

Because attackers rarely need to break the perimeter: one phishing email or stolen password puts them inside. An internal test shows what happens next, and how to stop it spreading.

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.

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.