A review ofsoftware built elsewhere

Security and Stabilisation Review

For organisations running software built by another agency, an in-house team or an AI building tool. Our senior engineers review it, and you receive written findings in priority order.

Whynow

NCSC Annual Review 2026

The National Cyber Security Centre published its Annual Review 2026 on 3 November 2026.

“AI did not create these weaknesses. It is exposing them faster than ever before.”

NCSC Annual Review 2026, “Embedding cyber security into everything”

The Annual Review judges it highly likely that defenders and maintainers will face a race to shorten patch deployment timelines. It says organisations with legacy technology and limited resources may struggle to keep pace.

Read the Annual Review on the NCSC website →

Our own view

The Annual Review covers cyber security in general and does not discuss who built the software. In our experience, patching software quickly depends on knowing what it is made of, how it is hosted and whether a change can be tested before it goes live. This review looks at each of those.

What thereview looks at

The scope

Our senior engineers read the code and look at how the software is hosted and run. These are the areas they cover.

  1. 01

    Security weaknesses

    How people sign in, what each of them is allowed to do, and how data is stored and handled.

  2. 02

    Dependencies and updates

    The libraries and services the software is built on, which of them are out of date, and what bringing them up to date would involve.

  3. 03

    Hosting and access

    Where the software runs, who holds the accounts and the keys, and whether it could be moved.

  4. 04

    Tests

    What is covered by tests, what is not, and whether a change can be checked before it goes live.

  5. 05

    Documentation

    Whether someone new to the software could run it and change it from what is written down.

What youreceive

At the end

A written report, and a session where we walk you through it.

  1. 01

    An overall grade

    The report opens with a single grade for the overall quality of the software, such as a B or a C+, and the reasons behind it.

  2. 02

    An executive summary

    The main risks and our recommendations, written for the people who approve the work.

  3. 03

    Findings by area

    What we found in each of the five areas, in priority order, and where it sits in the software.

  4. 04

    Practical next steps

    What to do about each finding, starting with the changes that reduce the most risk.

  5. 05

    A debrief session

    We walk you and your team through the report, on Google Meet or in person depending on where you are, and answer your questions.

  6. 06

    The final report

    Anything that was unclear in the session is clarified in the report, and you receive the final version.

How itruns

  1. 01

    A free diagnostic call

    You tell us what the software does and who built it.

  2. 02

    Scope and price in writing

    We confirm what the review will cover and its fixed price before any work starts.

  3. 03

    The review

    Our senior engineers read the code and look at how the software is hosted and run.

  4. 04

    The report

    You receive the written report with its grade, findings and next steps.

  5. 05

    The debrief

    We walk you through it, answer your questions and issue the final report.

Theprice

Fixed, in writing

The review has a fixed price, agreed in writing before any work starts.

A price agreed in writing before it starts. No day rates, no meter running. Every paid step with us is priced this way.

We don't publish prices because a number without a scope is a guess, and guesses are how projects overrun. How the money works across the whole path is on How we work.

Afterthe review

Fixing what was found

If you want us to fix what the review found, that work is a build with its own price, agreed in writing before it starts.

We stabilise the software, get it properly tested and documented, and put it on the same footing as our own work.

From there it can move onto a twelve-month Sharpen agreement, sized to your roadmap and agreed before we start. What the agreement covers is set out on How we work.

Got your own engineers and infrastructure? We hand over cleanly and stay involved only as much as you want.

What comeswith it

  1. 01

    An outside view

    We did not build the software, so the review is an independent check on the work of your team or your supplier.

  2. 02

    Senior engineers

    Senior engineers carry out the review. On our own builds, they review every line before it ships.

  3. 03

    A fixed price

    Agreed in writing before any work starts, for the review and for any fixing that follows.

  4. 04

    Tested and secured

    Anything we fix is held to the standard of our own builds: secure, tested, able to carry real users and real data.

  5. 05

    An option to keep us involved

    After the review, and any fixing you ask us to do, we can stay involved for twelve months to keep the software secure and improving. It is a separate agreement and is not part of the review.

Start witha call

The review starts with a free 30-minute diagnostic call. Tell us what the software does and who built it. If the review is a fit, we confirm the scope and the fixed price in writing. If we don't think we can help, we'll say so and suggest where to look instead.

We use it to reply and set up the call.

The name is fine. A link is better.

One line is plenty.

We reply within one working day. Free, no obligation. We use your details to set up the call. No mailing lists. Privacy

Not ready for a call? Email us at hello@komododigital.co.uk and a human will reply.