Skip to content

Legacy Application Security

See where critical software is exposed, and get a prioritized plan to fix it.

For applications your business still depends on, even when the original team, framework or vendor support is gone. We assess the code and what an attacker can reach. Then we patch what’s urgent, replace risky components, and modernize the entire platform when that’s what it needs.

What we assess

One internet-reachable application: its source code, its dependencies, and everything an attacker can reach.

What you get

Validated findings, a prioritized plan, and the engineering to carry it out: patches, component replacements or a modernized platform.

How to start

A conversation about the application, then written scope and approvals before any testing.

Assessment

Start with where it's exposed.

Old applications often hide their weak points in code nobody has read in years. We read it first, then prove from outside which weaknesses an attacker can actually reach.

In the code

  • Where sign-in, permission and tenant checks live, and where they're missing
  • Routes and background jobs that bypass those checks
  • Dependencies that are deployed, reachable and past end of support

From outside

  • Exposed admin, debug and partner interfaces
  • Sign-in, password reset and session handling
  • APIs, file handling and server-side fetches

In the plan

  • Each finding ranked by business impact
  • A recommended response: patch, replace or modernize
  • Which fixes to make first, and which can wait

Same process and approvals as our Penetration Testing: nothing is tested until you approve it in writing. Internal-only systems are not included.

Patch or modernize

When a patch is enough, and when it isn’t.

The plan recommends one of three responses for each finding. We carry out any of them, or hand the plan to your team.

01

Patch

The flaw is contained to one place, the code can be changed and tested safely, and the component is still supported.

Example
A missing tenant check on one route.

02

Replace a component

The same kind of flaw keeps coming back from one component, or the component is past end of support, or fixing it in place costs more than replacing it.

Example
A hand-built session handler behind three findings.

03

Modernize the platform

The risk is systemic: the flaws trace back to the architecture, or the framework can't be updated safely. And the business case and scope support the work.

Example
An unsupported framework under every route.

Sample plan

A plan engineers and budget owners can both use.

Every line links back to validated findings and evidence, so the order of work is defensible.

Exposure assessment · Prioritized planFictional · not client data

Broker portal, built 2014

Java web app · framework past end of support · internet-facing

OrderWhat we foundBusiness impactResponse
Fix firstPassword reset can be retried without limitAccount takeover for any brokerPatch
Fix firstValid service credential in an old mobile buildDirect access to stored documentsRotate and remove
Fix nextIn-house session handling behind 3 findingsSessions survive logout and role changesReplace component
PlanWeb framework past end of supportFuture flaws won't be patched upstreamModernize
PlanError pages reveal stack tracesHelps attackers map the systemHarden
Password reset can be retried without limitAccount takeover for any brokerFix firstPatch
Valid service credential in an old mobile buildDirect access to stored documentsFix firstRotate and remove
In-house session handling behind 3 findingsSessions survive logout and role changesFix nextReplace component
Web framework past end of supportFuture flaws won't be patched upstreamPlanModernize
Error pages reveal stack tracesHelps attackers map the systemPlanHarden

Order weighs what an attacker gains against how easily they get it. Modernization items include the risk of waiting.

What’s included

From the first assessment to a modernized platform.

The assessment

Where every engagement starts
  • Source-assisted review and testing from outside
  • Validated findings with evidence and severity
  • A prioritized plan: patch, replace or modernize
  • Confidential report and letter of attestation
  • Retesting as agreed in scope, under your written approval

Implementation

When you need it
  • Patches for the weaknesses that matter
  • Replacing risky components
  • Modernizing the entire platform

Each piece of work starts with its own written scope. Your team reviews and deploys every change, and retesting is as agreed in scope.

FAQs

Before you start.

Does it have to be internet-facing?
Yes. We assess what an external attacker can reach. Internal-only systems are outside this service.
Do you need the source code?
Yes. Read access or a source export, for the code that's actually deployed.
We can't change the code safely. Can you still help?
Yes. The assessment changes nothing, and the plan shows what's safe to patch. When the code has to change, we do the engineering.
Will you rebuild it?
When the risk is systemic and the business case supports it, yes: we modernize the entire platform. Most legacy apps need targeted fixes first.
Who does the work?
AI agents do much of the review and testing, inside limits you approve. A named tester of record is responsible for the report and signs the letter of attestation.
How is our data handled?
We agree where evidence is stored, who can access it and how long it's kept before testing starts.

Discuss a legacy app.

Tell us what it does, roughly how old it is, and what prompted the question. A practitioner replies with next steps, or a straight answer that we're not the right firm.