Penetration testing
External penetration testing
We attack what you expose to the internet, the way a real attacker would and only with your written permission, to show what someone could actually reach.
Who it's for.
Who it's for
- Businesses whose customers or partners ask for an independent penetration test
- Teams that need penetration testing for PCI DSS, or as evidence for ISO 27001
- Anyone who wants proof of what's exploitable, not just a list of what might be
What we test.
What we test
Reconnaissance
What an attacker can learn about you from public sources before they start.
Exposed services
Exploiting weaknesses in internet-facing servers, VPNs and remote access.
The front door
Weak passwords, missing multi-factor authentication and other ways past a login, tested safely.
Web-facing systems
The websites and portals you expose, checked for the common ways in.
Chained weaknesses
Small issues combined into a real path in, the way attackers actually work.
Proof of impact
Evidence of what we could reach, without harming your systems or data.
What you get.
Included with every engagement
- 01
Scope and rules of engagement
What's in scope, when we test and how, agreed in writing before we start.
- 02
Executive summary
What we found and what it means for the business, in plain English.
- 03
Technical findings
Each issue with its severity, evidence and steps to reproduce it.
- 04
Remediation guidance
Practical fixes, in order of priority, that your team can act on.
- 05
Debrief
A walkthrough of the findings with the people who'll fix them.
- 06
Retest
Confirmation that what you fixed is actually closed.
From first call to fixed.
How it works
- 01
Scoping call
We learn what you want tested, why, and by when.
- 02
Quote and authorisation
A fixed quote, the exact scope and the rules of engagement, signed off in writing before we touch anything.
- 03
Testing
We test within the agreed window, and tell you straight away if we find something critical.
- 04
Report
A plain-English summary for leadership, and technical detail and fixes for your team. Every finding ranked by risk.
- 05
Debrief
We walk the people fixing things through the findings and answer their questions.
- 06
Retest
Once you've fixed the findings, we test again to confirm they're closed.
Frequently asked questions.
FAQ
What is an external penetration test?
A tester tries to break into what you expose to the internet, the way a real attacker would, within rules you agree to. You learn what's actually exploitable and what it would lead to, with evidence.
How often should we have one?
At least once a year, and after major changes to your systems. Some standards and customers ask for exactly that.
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.