Skip to content
LupoSec

Service 01 · Penetration testing

We attack your systems the way a real adversary would, then show you how to stop it.

Manual, expert-led testing, not a scanner export with a logo on it. Every finding is reproduced and explained. We can fix the issues for you too, and every fix is verified with a free retest.

What we test

Engagement types

Web applications & APIs

Authentication, authorisation, business logic, injection, SSRF and multi-tenant isolation. REST, GraphQL and gRPC, tested against OWASP ASVS and the API Top 10.

External network

Your internet-facing attack surface as an attacker sees it: discovery, exposed services, misconfigured edge, VPNs and remote access.

Internal network & Active Directory

An "assume breach" test from a foothold inside: lateral movement, privilege escalation, AD and Entra ID attack paths.

Cloud (GCP · AWS · Azure)

IAM privilege escalation, exposed storage, metadata abuse, Kubernetes and serverless. This is where our founders spent their careers.

Mobile

iOS and Android apps and their backends: insecure storage, certificate pinning, API abuse and reverse engineering.

Targeted red team

Goal-based adversary simulation against agreed crown jewels, to test whether your detection and response work.

Methodology

Built on standards, driven by experience

Our testing follows PTES, the OWASP Web Security Testing Guide and ASVS, and NIST SP 800-115, so the work is repeatable and auditable.

Standards are the floor. The findings that matter most usually come from chaining small issues into a real attack path, and from knowing how cloud platforms fail in practice. That knowledge comes from years of defending them.

What you receive

A report people actually use

  • Executive summary in plain language, with a risk rating for leadership and the board
  • Every finding reproduced, with step-by-step evidence and a CVSS v4 score
  • Specific remediation guidance for your stack, not generic advice
  • Attack-path narrative showing how small issues chain into big ones
  • Optional hands-on remediation: our engineers fix the findings with your team
  • A free retest and an updated report once the fixes are in

FAQ

Common questions

How long does a pen test take?

Most web, API or external network tests take 5–10 working days of testing. Larger cloud or internal engagements take longer. We give you a fixed timeline when we scope.

Will testing break production?

We agree rules of engagement up front: test windows, excluded systems, rate limits and an emergency contact. Destructive techniques are only used with your explicit approval, and preferably against staging.

Do you need written authorisation?

Yes, always. We do not test anything without a signed authorisation from someone entitled to give it. If your environment is hosted by a third party, we help you meet their testing policy.

Can we share the report with customers or auditors?

Yes. Alongside the full technical report we can provide an attestation letter that confirms the scope, dates and remediation status without exposing details.

Can you fix the issues you find?

Yes. Unlike many testing firms, we offer hands-on remediation. The engineers who found the vulnerabilities work with your team to fix them, then retest. See Posture Assessment & Remediation for how we work.

Does this help with NIS2 or DORA?

Both require regular security testing. Our findings are mapped to the relevant controls, so the report doubles as evidence for compliance.

Ready to see your systems through an attacker's eyes?

Tell us what you run and what keeps you up at night. We will come back with a proposed scope, timeline and quote.