Skip to content
Book a call

Home / Frequently asked questions

15 questions, answered properly

Frequently asked questions

What a penetration test is, what you get at the end, what it costs, and what we need from you to start. If your question is not here, ask us directly — we answer these all day.

Questions and answers

What exactly is an application penetration test?

A penetration test is a hands-on security assessment where experienced testers attack your application the way a real attacker would - looking for ways to reach data or functionality they should not be able to reach. It is not a scan. Automated tools find known patterns; the findings that matter in a real application are usually logic and authorization flaws that no scanner can recognise, because nothing is malformed - the request is perfectly valid, it simply should not have been answered.

What can you test?

Web applications, REST APIs and mobile applications (iOS and Android) - including the backend services behind them. That is the whole of what we do; we are specialists rather than a general security firm.

How long does a test take?

Testing itself runs from a few days for a single application to a few weeks for a large or multi-tenant platform, and the proposal fixes the dates before anything is signed. Once the scope is agreed and the order is signed, testing starts within five business days, and the report is delivered within three business days of the end of testing.

You do not wait for the report to see results: findings appear in your workspace as they are confirmed, and anything critical is reported the moment we find it. If a date is driving you — an audit, a customer security review, a launch — ask for Express: a committed start and report date for a fixed surcharge, quoted with the proposal. If your auditor or customer needs evidence before the full report is finished, we issue a signed letter of attestation that the test was performed, with a summary of its findings.

What do you need from us to start?

A description of the application and what matters most about it, an environment to test against (staging that mirrors production is ideal), and credentials for each user role. Roles matter more than anything else: most serious findings come from what one role can do to another's data, so testing with a single account hides exactly the issues you most want found.

Will testing disrupt our production environment?

We prefer to test against a staging environment for that reason. Where production testing is necessary, we agree the boundaries with you in advance - what is in scope, what techniques are excluded, and a contact who can reach us immediately. Destructive testing is never done without explicit written agreement.

What do we actually receive at the end?

A report written for the people who have to fix the problem. Every finding includes what it is, how to reproduce it step by step, the real business impact, and a concrete remediation - not a scanner description and a CVSS number. We also walk your team through it, and we are happy to defend any finding to the developers who wrote the code.

How do you rate severity?

By what an attacker can actually achieve in your application, not by a generic score. A theoretically 'medium' issue that exposes another customer's data is treated as what it is. We would rather tell you that a finding is not exploitable than pad a report - and we will say so plainly when that is the case.

Do you retest after we fix the issues?

Yes. A finding is not closed until it has been verified as fixed, and retesting of reported findings is part of the engagement rather than an upsell. It is also the point at which many teams discover a fix was incomplete.

Who actually does the testing?

Experienced application security specialists - the same people throughout the engagement. You are not handed to a junior after the kick-off call. Our team has included researchers who built tools the industry still uses and who went on to found security companies.

Can you help our developers fix what you find?

Yes. We will explain findings to the development team, review proposed fixes, and answer questions while remediation is underway. Having spent years teaching developers how attackers break applications, we know where reports usually lose their reader - so ours are written to be acted on.

What does a penetration test cost?

Our prices are published and fixed for the scope we agree: Focused $4,900 (one application or API, one or two roles), Professional $10,300 (an application and its API, several roles, business logic) and Platform $22,700 (multi-tenant isolation, or several systems together). Anything outside them - mobile, devices, source-assisted review, a programme across the year - is quoted from the same rate card. Every tier includes the report, the debrief and the retest of every finding. What moves a system between tiers is almost always the role model and the tenancy, not the number of pages. See the pricing page, or tell us about the system and we will confirm the tier - including telling you if you do not need a test yet.

Can you help with compliance requirements?

Yes - our testing and reporting are regularly used to satisfy customer security reviews, regulatory expectations and certification requirements. Tell us which framework or customer questionnaire you are answering and we will make sure the report addresses it.

How do you handle our data and the findings?

Confidentially, under NDA, as standard. Findings, evidence and reports are treated as sensitive material - they are effectively a map of how to attack you. We are happy to sign your agreement rather than insist on ours.

Do you use automated tools or AI?

Both, as accelerators - never as a substitute for a human. We use our own platform, CybeRapid, to take the repetitive work out of an engagement so that more of our testers' time goes on the parts that need judgement: attack strategy, business context and deciding what actually matters to you. The testing is human-led, enhanced by proprietary technology.

How do we get started?

Get in touch with a short description of the application and what worries you about it. We will come back with scoping questions, a clear proposal, and a realistic timeline - and if we are not the right fit, we will say so.

Still have a question?

Tell us what the system does and what worries you. If a penetration test is not what you need yet, we will say so.

Ask us directlySee the test cases