Security · Cardiff & UK

Web application security review

A clear account of the risks in scope, and a practical route to fix them.

Starting price
From £1,500 + VAT
Best for
An existing website or PHP application needing a focused security review
Leaves you with
Prioritised findings, a remediation plan and clearly stated review limits
Scope & timing
All testing is authorised and bounded in advance. We agree environments, methods, data handling and reporting before access is granted.

A clear scope. A useful outcome.

A useful security review connects a technical finding to the application it affects. An outdated package, a missing permission check and an exposed configuration file are different problems with different fixes. We review the agreed parts of the application and its deployment, then explain what to address first and how to verify the change.

The work can cover PHP source and dependencies, authentication and access control, input handling, file uploads, secrets handling and deployment configuration. Scope follows the system and the decision you need to make. We make coverage and limitations explicit so a focused engineering review is not mistaken for a complete assurance of the business.

  • A written scope identifying the authorised systems, environments and review methods.
  • An application and dependency review focused on the agreed risk areas.
  • Findings with affected components, supporting evidence, impact and practical remediation guidance.
  • A prioritised implementation plan separating immediate fixes from longer-term work.
  • Optional scoped remediation and retesting, with a record of resolved and outstanding findings.

How the work runs.

  1. Set the review boundaryConfirm ownership and permission, the sensitive workflows and the environments available for review. Agree how evidence will be handled and which activities are excluded.
  2. Inspect the relevant pathsReview code, dependencies and configuration against the agreed questions. Follow authentication, permissions and data movement through the application rather than relying on a scanner score alone.
  3. Explain and prioritiseDocument findings with enough context for an engineer to act. Discuss severity in relation to exposure and business use, and distinguish confirmed issues from areas that need further investigation.
  4. Fix and retestWhere remediation is commissioned, implement the agreed changes and recheck the affected behaviour. Hand over remaining risks and ownership so the report leads to an actionable maintenance plan.

Agree the boundaries first.

  • This is a scoped engineering security review, not a penetration-test certification, regulatory sign-off or guarantee that every vulnerability will be found.
  • Continuous monitoring, third-party systems and specialist forensic investigation require separate scope and appropriate expertise.

Questions before we start.

Is this a penetration test?
The standard engagement is an agreed code, dependency and configuration review with bounded validation. If a procurement or compliance requirement calls for a particular independent penetration test or accreditation, tell us first so the required specialist scope is clear.
Can you fix the problems as well as report them?
Yes, remediation can be scoped after findings are reviewed. Each agreed fix has an acceptance check, and the handover distinguishes issues that were resolved from those still owned by your team or another provider.
Will testing happen on the live site?
We agree environments and methods before work starts. Staging is preferred where it represents the relevant behaviour. Any production activity must be explicitly authorised, with limits that protect users, data and availability.
Does a clean report mean the site is completely secure?
No. Findings are limited by the agreed scope, access and time of review. We state those limits and recommend maintainable checks and ownership for ongoing changes; a report is a record of reviewed evidence, not a permanent security guarantee.

Work directly with QDev

Tell us what needs to change.

Name, email and a project message are required.

10 to 2,000 characters. Include the goal, current state and any deadline.

We use your details to assess your enquiry and reply. Read our privacy note.

Security

Hacked website recovery

Assess recovery for a compromised PHP or WordPress site with QDev. Scope containment, evidence preservation, restoration, credential changes and hardening.

You leave with A documented recovery, agreed validation and a follow-up security plan

Price From £475 + VAT

Explore Hacked website recovery

Start with the facts.

Send the site, the hosting provider and what has changed. We'll reply with the next step and what it depends on.