CREST Penetration Testing in Oxford
£2,400 Flat per App

For Oxford's digital health, clinical research and science spin-out teams. Retest included, no day rates.

CREST accredited: Penetration Testing CREST accredited: Vulnerability Assessment CREST accredited: App Security Testing CREST accredited: Mobile App Security Testing

Get your £2,400 pentest quote

Tell us about your app. We reply within 1 business day with a fixed quote. No call needed.

  • £2,400 flat per app and its API, any size
  • Retest included
  • CREST accredited, rated 4.8/5 on G2

Prefer to talk? Book a 30-min scoping call

Penetration Testing for Oxford Teams

South East England

Oxford's technology economy grows out of the university and its hospitals. Spin-outs in vaccines, diagnostics, digital health and AI sit alongside clinical research groups, science parks on the city's edge and, a short drive south, the Harwell campus with its space and big-science facilities. Much of the software built here handles patient data, trial results or research datasets that other organisations depend on.

That puts Oxford teams in front of demanding reviewers. NHS trusts check suppliers against the Data Security and Protection Toolkit and DTAC. Pharma partners audit vendors before trial data goes anywhere near a new platform. Investors backing university spin-outs want to see that a product handling health data has been tested independently.

What Oxford Teams Bring Us to Test

Digital health and NHS suppliers

Patient-facing apps, remote monitoring and clinical decision tools are sold to NHS trusts and practices. NHS buyers ask for penetration testing as part of DTAC and supplier onboarding, and they read the report.

What we focus onIDOR on patient records, clinician versus patient roles, NHS login and SSO integration, appointment and messaging features, file uploads of clinical documents, and audit logging of who viewed what.

Clinical trials and pharma software

Electronic data capture, eConsent and trial management tools hold participant data and results that regulators rely on. Sponsors and CROs qualify vendors carefully, and security testing is a standard part of that.

What we focus onSite and sponsor separation, blinding controls, audit trail integrity, participant identity data, unblinding functions restricted to the right roles, and bulk exports of trial datasets.

Research and science platforms

Spin-outs and research groups build data platforms, AI tools and instrument portals used by external collaborators. Valuable datasets and intellectual property make them targets, and partners want assurance before sharing data.

What we focus onDataset access between collaborating organisations, API keys in notebooks and pipelines, model and data download controls, collaborator invitation flows, and compute job features that could run unintended code.

What We Often Find

When we test the health, trial and research software coming out of Oxford, these four problems appear more often than any others.

Patient records by changing an ID

Incrementing a patient or appointment identifier in an API request returns another person's health data. It is the most common serious finding in health apps and is reportable to the ICO.

Audit trails that can be altered

Trial or clinical data changes are logged, but the log itself can be edited or bypassed through a secondary endpoint. Sponsors and inspectors depend on that trail being trustworthy.

Unblinding available to the wrong role

Treatment allocation is hidden in the interface but returned in an API response to site staff. Accidental unblinding can compromise an entire study, not just one record.

Collaborator access that never ends

External researchers keep dataset access after a project ends because invitations and shared links do not expire. Sensitive or licensed data stays exposed long after anyone remembers it.

Trusted by SaaS Teams Worldwide

£2,400. Not £12,000–£25,000.

What UK pricing guides put a SaaS app with an API and several user roles at.

Typical UK quote
CyberFortify
How it’s priced
Typical UK firm: day rates (median ~£1,000/day)
£2,400 flat per application
SaaS app, API, several roles
£12,000–£25,000
£2,400
Retest of your fixes
Often extra, £2,000–£5,000
Included
App bigger than expected
More days, bigger invoice
Same £2,400, no size cap
Who tests
Varies by firm
CREST-accredited engineers

Sources: Stingrai Penetration Testing Price Index (Sept 2026, median of 30 G-Cloud 14 rate cards) and Cyphere’s UK cost guide (2026).

Got a UK Quote? See Your Saving

Example figures are filled in. Change them to match your quote.

days
£
£
£
Your saving
Your UK quote£9,500
CyberFortify, retest included£2,400
£7,10075% less than your quote
Book my £2,400 pentest

One Price, Everything In It

Per application · any size

£2,400flat

  • One web app and its API, no endpoint cap
  • Testing starts within a week, report in 4–7 working days
  • Free retest, signed attestation letter
Book a scoping call

Included in the £2,400

  • AI-enabled testing, with every finding validated and exploited by CREST-accredited engineers
  • Authentication, access control between user roles and business logic
  • Criticals flagged within 24 hours, not held for the final report
  • CVSS-scored findings with reproduction steps and the fix
  • Clean report and signed attestation letter for customers, auditors and insurers
  • ISO 27001 and ISO 9001 certified processes, professional liability cover and Koop cyber insurance

One application = one web product your users sign in to, plus its API. Mobile apps, internal networks and cloud reviews are scoped separately. Prices exclude VAT.

From First Call to Clean Health Report

9 gates, the same sequence on every engagement.

  1. 01

    Discovery

    Client insight

    We send a short questionnaire to understand your infrastructure, business requirements and security concerns.

    Owner: you + CyberFortifyOutput: completed questionnaire
  2. 02

    Agreement

    Scope & SOW

    We analyse your answers, define a clear scope and issue the Statement of Work.

    Duration: 2–3 business daysOutput: signed SOW
  3. 03

    Initiation

    Kickoff meeting

    We walk through methodology, timeline and requirements, and access is handed over securely.

    Format: live sessionOutput: methodology brief
  4. 04

    Active testing

    Testing execution

    AI-enabled coverage, then accredited engineers validate and exploit. High and critical findings are sent to you immediately.

    Duration: 4–7 working daysLive alerts: high & critical
  5. 05

    Reporting

    Report delivery

    Every finding with risk rating, technical detail and step-by-step remediation, mapped to your controls.

    Format: PDF + machine-readableAudit-ready
  6. 06

    Walkthrough

    Report review

    A session with your technical team to explain findings, priorities and remediation approaches.

    Duration: 60–90 minutesRecorded on request
  7. 07

    Remediation

    You fix

    Your teams implement fixes. We stay available for guidance throughout.

    Timeline: you set itSupport: on call
  8. 08

    Verification

    Retest

    We re-test every previously identified issue to confirm the fix and check nothing new was introduced.

    Cost: includedScope: every finding
  9. 09

    Attestation

    Clean health report

    A final report confirming remediation and your improved security posture, ready to share with auditors.

    Audit-readyShareable with customers

What Oxford Buyers Ask For

NHS Data Security and Protection Toolkit

Suppliers handling NHS patient data complete the DSPT, which asks about penetration testing of systems. A CREST report with retest evidence answers those questions directly.

DTAC

The Digital Technology Assessment Criteria include a cyber security section that NHS buyers use to assess digital health products. A recent pentest of the product is part of the evidence they expect.

Pharma vendor qualification

Sponsors and CROs audit eClinical vendors before use, alongside their GxP and computerised system validation checks. An independent pentest report helps you pass the security part of that audit.

Before you book.

An NHS trust has asked for a pentest as part of DTAC. What should we include in scope?

Include the product the trust will actually use: the patient and clinician web app, its API, and any admin portal. We test each role separately so the report shows patients cannot reach other patients' data and clinicians only see their own caseload. Mobile apps, if any, are scoped as a separate test.

Can you test our trial platform without touching real participant data?

Yes, and we recommend it. Most sponsors expect testing against a validated test or UAT environment with dummy studies and synthetic participants. We need representative roles, such as site user, monitor and sponsor, so we can check blinding and separation properly.

We are a university spin-out raising our first round. Do investors really look at pentest reports?

Increasingly, yes, especially when the product handles health or research data. A short attestation letter in the data room shows the product was tested and serious issues fixed. It also saves time later, as the first NHS or pharma customer will ask for the same evidence.

Do you have an office in Oxford?

No. CyberFortify has no Oxford office. Web application and API tests run remotely, which is how almost all application pentests are delivered. Kick-off, critical alerts and the report walkthrough happen in UK working hours, and the price is the same £2,400 flat.

Why is it cheaper than UK day-rate firms?

Our AI Pentest Agent covers the breadth of your app: mapping every page and API route and checking the known issues. That frees our CREST-accredited engineers for exploitation, access control and business logic. Fewer billable days means one flat fee instead of a day rate. Every finding is still validated by a person before it reaches your report.

Is CyberFortify really CREST accredited?

Yes. CyberFortify is a CREST member company, accredited for Penetration Testing and AI-Enabled Penetration Testing, and a signatory of the CREST AI Charter. You can check our listing on the CREST Marketplace before you book.

What counts as one application?

One web product your users sign in to, plus the API behind it. Size doesn’t change the price: a large SaaS platform with many roles is still £2,400. A mobile app, an internal network or a cloud configuration review is a separate scope, and we’ll quote it on the call if you need it.

Is the price really fixed?

Yes. £2,400 per application, agreed on the scoping call before testing starts. The retest of your fixes is included. There are no day rates, so the invoice doesn’t grow if testing takes longer.

Is Cyber Essentials Plus the same as a penetration test?

No. Cyber Essentials Plus is a certification with a hands-on check of five basic controls. It doesn’t test your application for vulnerabilities the way a penetration test does.

Are you a CHECK company?

No. CHECK is the NCSC scheme for UK government and critical national infrastructure systems. If your contract names CHECK, you need a CHECK company, and we’ll tell you so on the call. CyberFortify is CREST accredited.

How fast can you start?

Testing usually starts within a week of the scoping call, and most reports are ready in four to seven working days. Criticals are flagged within 24 hours of discovery.

What happens to our data?

CyberFortify works under ISO 27001 certified processes. Client data from the engagement is disposed of afterwards, as set out in the statement of work. Every assignment carries professional liability insurance and Koop cyber insurance.

Already have your scope written up? Send full scope details

A CREST pentest in Oxford for £2,400.
Booked this week.

Your first call is with Usama Gul, the founder and the engineer who leads your test. You’ll leave with a confirmed scope and a start date.