Ethical hacking and penetration testing
A penetration test is a real, controlled and authorised attack on your systems. It goes beyond listing known vulnerabilities: it tries to exploit and chain them to show how far an attacker would get and what to fix first.
What it covers
- Web applications and APIs.
- Internet-facing and internal infrastructure.
- Wireless networks.
- Social engineering, together with the ethical phishing service.
- An executive report for management and a technical report for the IT team.
- A closing session to walk through the findings and how to fix them.
We only attack what has been authorised in writing, within the agreed window. We never test third-party systems without their permission.
How we work
- Scope and authorisationWe agree systems, test windows and limits in writing.
- ReconnaissanceWe map what an attacker can see from outside and inside.
- Controlled exploitationWe try to exploit and chain vulnerabilities within scope.
- ReportEvery finding with evidence, impact and how to fix it.
Frequently asked questions
How is it different from a vulnerability scan?
A scan is automated and finds known issues. In a penetration test a person tries to exploit them, chains them together and finds logic flaws a scanner cannot see.
Can it affect production systems?
Before starting we agree the scope, test windows and critical systems, and we use controlled techniques to keep the risk to a minimum.
How long does it take?
It depends on scope. We estimate it at the first meeting, once we know which systems are included.