PENETRATION TESTING
A penetration test simulates how attackers would try to breach your systems, then shows what we were able to do, and how to fix it.
We use hands on testing to find real logic and abuse paths, supported by specialised tooling for coverage. Where it adds value we test with credentials so the impact is clear.
We follow recognised methodologies, including OSSTMM and NIST 800-115, alongside our in house approach shaped by hundreds of penetration tests. Findings are mapped where useful to OWASP Top 10 lists for web, API, and mobile, and to OWASP ASVS and MASVS for deeper assurance.
Penetration testing comes in three broad options, white box, grey box, and black box. This describes how much information we get before or during the assessment, from full design details to almost none. If you are unsure which suits your goals, timelines, or risk tolerance, we will help you pick the right approach.
We cover the products you actually ship. That includes web apps and front end flows, back end services and APIs like REST, GraphQL and gRPC, and mobile apps on Android and iOS. If you need network and infrastructure coverage, we test external and internal networks, internet exposed services, escalation paths, misconfigurations, and lateral movement opportunities.
Scoping is simple. Tell us what you need through a short form or a quick call. We send a clear scope with costings, number of days, and access requirements. Once you approve it, we book you in. Before testing, we confirm access and prerequisites. Testing runs on the booked days. Three working days after testing you receive the report. You also get one free retest to verify fixes.
Your deliverable is a risk rated PDF in plain English. It includes evidence, affected assets, clear steps to reproduce, and suggested fixes your engineers can action.
Most of the risk lives in your APIs now, so we test web and API together. We look at auth, access control, business logic, upload and parsing bugs, SSRF, injection, caching issues, and rate limits. We align to OWASP ASVS and the OWASP API guidance.
What you get
A clear report, replayable PoCs, fix advice in your stack, a short summary for stakeholders, and a retest window.
We test Android and iOS, the app, the device, and the backend it talks to. Storage and privacy, Keystore or Keychain, IPC, screenshots and backgrounding, cert pinning, jailbreak or root handling, biometrics, and API flows. We follow OWASP MASVS and MSTG.
What you get
Code level guidance with screenshots or short clips where useful, store hardening tips, and a retest.
Perimeter isn’t just firewalls, it’s cloud and your identity layer. We assess external and internal exposure, Active Directory and Entra ID, MFA and conditional access, SSO flows and session settings, legacy protocols, attack paths, M365 hardening, AWS, Azure and GCP configuration, Kubernetes and containers, and remote access.
What you get
An updated asset list showing what’s exposed and what changed, attack path diagrams where it helps, a prioritised fix plan your team can action, and a retest.
Sometimes the fastest way to find the bug is to read the code. We review auth and permission checks, data flow, dangerous APIs, crypto use, error handling, secrets, supply chain and dependencies, plus infrastructure as code like Terraform and Kubernetes manifests.
What you get
Annotated snippets or diffs, example fixes in plain language, an optional mini pattern library for your team, and a retest through pull requests if needed.
If you split logic across services, we test the seams as well as each service. Service to service auth, tokens, queues, schemas, GraphQL or REST specifics, rate limits, replay and race conditions, and config drift across environments.
What you get
A simple map of exposed surfaces, issues by service, and fixes that fit how you deploy.
We re run affected checks, confirm the fix, update evidence, and close the engagement. You leave with an updated report you can share.
