Penetration testing before a product or API launch

When to test a new release, what to include, and how to plan around the date.

Source code on a computer monitor

Why test before launch

Fixing an authorisation flaw in staging costs a pull request. Fixing it after customers have used it can mean a disclosure, a support load and lost trust.

What to include

Scope the parts that change who can see or move what:

  • New API endpoints and the roles that call them.
  • Login, SSO and account changes.
  • Payment, refund and payout flows.
  • New integrations, webhooks and file uploads.

Timing

Book the test for a feature-complete staging build, and leave time to fix and retest before the release date. Tell us the release date in your proposal request.

Need this done?

Tell us what needs testing and when. We reply within 1 business day.

Request a proposal
Ready to test?

Tell us what needs testing and by when.

You receive a written proposal with scope, method, timeline and a fixed price. We reply within 1 business day.