Vulnerability Assessment · Service

From findings to fixed.

A report only helps once its findings are closed. We work with your developers to plan the fixes, answer their questions and confirm the result with a retest.

Overview

What this covers

A security report can be hard to act on. Findings are rated, but your team still has to decide what to fix first, how to fix it in your particular codebase, and whether the fix actually worked. Without that follow-through, reports end up filed and the same issues appear again in the next assessment.

Fix guidance, a walkthrough and a retest are part of every assessment we run, and remediation support is also available on its own for reports produced by other providers. We go through each finding with your developers, explain why it matters in your context, agree a fixing order based on severity, likelihood and effort, and answer questions as the work goes on.

When fixes are in place, we retest each one and confirm in writing whether it is closed, partly closed or still open. Where the same type of issue keeps appearing, we suggest changes to development practice, such as a shared validation library or a review checklist, that stop it recurring.

Deliverables

What you get

Prioritised fix plan

An agreed order for addressing the findings, based on severity, likelihood, business impact and the effort each fix needs.

Walkthrough call

A session with your developers to explain each finding, the fix and how to check it.

Ongoing questions

Answers to your team's questions while they work through the fixes, within the period agreed in the scope.

Retest report

Written confirmation of the status of each retested finding: closed, partly closed or still open, with evidence.

Prevention notes

Suggestions for development practices that stop recurring categories of issue.

Approach

How we run it

  1. 01

    Review the report

    We read the findings, or revisit our own, and confirm which are in scope for remediation support.

  2. 02

    Plan with your team

    On a call, we agree the fixing order and who is responsible for each item.

  3. 03

    Support the work

    Your developers make the fixes, and we answer questions and review proposed approaches as needed.

  4. 04

    Retest

    We test each fix and record whether the issue is closed.

Questions

Before you ask.

Can you fix the issues for us?

Our role is to guide and verify, so your team keeps ownership of its code and systems. If you need hands-on development help, tell us and we will discuss what is possible within the scope.

Can you work from another provider's report?

Yes. We will review the report first and confirm in the scope which findings we can retest. Retesting another provider's findings needs the same written authorisation as a new assessment.

What if a fix only partly works?

The retest report will say so, explain what remains and suggest what to change. A further retest can be agreed.

Is the retest included in the price of an assessment?

A retest of fixed issues is part of each assessment. What it covers, and any timing limits, are set out in the scope and quote.

Talk to us about remediation support

Tell us what you want tested. We will reply with a proposed scope, the authorisation we need, and a quote.