External (perimeter)
What an attacker sees from the Internet: exposed services, VPN, email and websites.
Penetration testing
A penetration test is an authorised intrusion test: we try to exploit the vulnerabilities in your website, network or applications as an attacker would, to prove the real risk and tell you in which order to fix it. It is carried out by a certified team (CEH, eJPT), with manual validation, not just scanners.
| Vulnerability scan | Pentest | Audit | |
|---|---|---|---|
| Goal | List known flaws | Prove whether they can be exploited | Review controls and processes |
| Depth | Automated and broad | Manual and targeted | Organisational and technical |
| Result | A list of findings | Evidence, impact and priorities | A risk map and a plan |
What an attacker sees from the Internet: exposed services, VPN, email and websites.
What someone already inside your network, or with a stolen account, could do.
Following the OWASP Top 10 and the WSTG testing guide: authentication, authorisation, injections.
According to the OWASP MASVS standard: storage, communications and logic.
Wireless networks and the configuration of Microsoft 365, Azure or AWS.
Phishing simulations and tests on people’s processes.
No prior information, like an external attacker. It measures what can be seen from outside.
With a user account or some documentation. The most common option for businesses.
With access to the code or architecture. It finds more in less time.
We follow recognised methodologies (OWASP WSTG, PTES, OSSTMM and NIST SP 800-115) and map techniques to MITRE ATT&CK.
We define what is tested, when and how, and sign the authorisation letter and the NDA.
We gather public and technical information about the target, as an attacker would.
We try to exploit what we find without disrupting operations and stop at any risk.
We deliver the results and go through them with management and the technical team.
We check that the fixes work, according to the agreed scope.
There is no single price: we prepare a tailored proposal based on:
It should not. We agree testing windows, avoid destructive techniques and stop if anything puts a production system at risk.
Only for grey or white box tests. In black box we work without prior information, like an external attacker.
We tell you straight away, without waiting for the final report, so you can act as soon as possible.
Yes: the report is evidence that you assess the effectiveness of your measures, which NIS2, ISO 27001 and many insurers ask for.
Yes. Before starting we sign the authorisation letter and the NDA.
Tell us what you want to test and we will send a proposal with scope and dates.