Skip to main content

Penetration Testing

Penetration testing and security reviews for web apps and APIs, finding exploitable weaknesses before attackers do and fixing them in the code.

Where we use it

We conduct penetration testing to proactively identify and fix security vulnerabilities in our applications. By simulating attacks, we can find weaknesses in the system before malicious actors do. This is a critical step in protecting your application and user data.

Strengths

  • Proactively identifies and fixes security weaknesses.
  • Protects against data breaches and cyber attacks.
  • Supports security and compliance reviews.

Trade-offs

  • Can be expensive and time-consuming.
  • Can potentially disrupt services if not done carefully.
  • A clean report is not a permanent guarantee of security.

Questions

Vulnerability scanning is an automated process that identifies potential weaknesses. Penetration testing is a manual process where an ethical hacker attempts to actively exploit those weaknesses.

What we test

Sign-in and sessions
Password handling, account lockout, session expiry and password reset flows.
Access control
Whether a user can see or change another customer's records, for example by altering an ID in a link or API request.
Input handling
Injection, cross-site scripting and unsafe file uploads, the classic problems listed in the OWASP Top 10.
APIs and configuration
Unprotected endpoints, exposed admin panels, default credentials, missing security headers and weak TLS settings.

Scope, reporting and when you need an independent test

Every test is authorised in writing and scoped in advance: which systems, which environments and which dates. Findings are reported by severity with steps to reproduce and a recommended fix, and because we are developers, we can fix the code and retest.

Some situations call for a test by an independent, certified third party, for example when a regulator, bank or enterprise customer asks for one. In those cases we can prepare the system, work with the tester and close the findings. For the legal side of handling personal data, see our PDPL guide.

Let’s scope your project.

Tell us what you are building. We reply within one business day.