Application Security

From 60,000+ ignored findings to zero open Critical or High in eight months

Client
Large insurance company
Service
Application security program
Timeline
Eight months to the result
Result
Zero Critical or High open
The challenge

What did the client need?

A large insurance company with hundreds of custom applications first hired ioSENTRIX for a penetration test. The issues we found pointed to design and architecture flaws, and to an application security program that was not working.

Engagement details

Client
Large insurance company
Estate
Hundreds of custom applications, many on-premises and legacy
Scope
Testing tools, AppSec processes, SDLC and developer training
Start
A penetration test that exposed design and architecture flaws
Timeline
Eight months to the headline result, within a three-year roadmap
Result
Zero Critical or High open
Delivered by
ioSENTRIX application security team
Our approach

How did ioSENTRIX approach it?

More tooling would have added more noise. The turnaround came from tuning what was there, building the processes around it and training developers on the organisation’s own top risks.

The roadmap also added secret, infrastructure-as-code and dependency scanning, application classification and data-handling standards, design review, threat modelling and manual code review, with quarterly business reviews for leadership.

What we found

What did ioSENTRIX find?

Tools that cried wolf, a program that did not exist, and both now fixed.

Theme · ToolingFinding 1

Scanners produced noise, not fixes

The company relied only on static and dynamic application security testing (SAST and DAST). Both were poorly configured, so false positives and legacy debt buried real issues, and developers ignored more than 60,000 reported vulnerabilities.

Business impact. Real risks were lost in the noise, and the tools had lost the trust of the people meant to act on them.

Theme · ProcessFinding 2

There was no program to act on results

There was no working vulnerability management or risk acceptance process. Exceptions in the governance system had fallen out of step with the scanners, leaving a build-up of outdated exceptions.

Business impact. Nobody could say which risks had been accepted, by whom, or which needed fixing first.

The path from scanner noise to zero Critical or High
Program path · from noise to signal
  1. 1Gap analysisweak points found
  2. 2Tools tunedfalse positives cut
  3. 3Programs addedreview, risk, training
Outcome: Zero (Critical or High open in eight months)
The impact

What changed as a result?

Its scanners had produced more than 60,000 open vulnerabilities that developers ignored, about 10% of them false positives. We ran a gap analysis, built a three-year roadmap and started a risk reduction campaign. More than 35% of the Critical findings were closed with platform-level fixes. Within eight months, no Critical or High vulnerabilities remained outstanding.

60K+
open vulnerabilities at the start
0
Critical or High outstanding after eight months
35%+
of Critical findings closed by platform-level fixes

What changed after the program?

What changed across the application estate
AreaBefore the programAfter eight months
Open vulnerabilitiesMore than 60,000 reported issues that developers ignoredNo Critical or High vulnerabilities open
ToolingPoorly configured SAST and DAST, buried in false positivesTuned SAST and DAST, about 10% of findings confirmed false positives; secret, IaC and dependency scanning added
ProcessNo vulnerability management or risk acceptance; stale exceptionsVulnerability management, risk acceptance and application security review programs
PeopleSecurity seen as noise by developersTraining on the organisation’s top 10 risks and reviews for high-risk apps

✓ Verification: Outcome measured across the estate.

Key insight

The scanners were finding plenty. Nobody trusted them enough to act.

Lessons

Lessons for security leaders

01

Tune before you buy

Untuned scanners produced 60,000+ findings nobody trusted. Fixing the configuration did more than a new tool would.

Finding 1
02

Build the program around the tools

Findings need owners, risk acceptance and review, or exceptions go stale and risk goes unseen.

Finding 2 · OWASP SAMM v2: Implementation and Verification business functions
03

Fix the platform, not each finding

More than 35% of the Critical findings were closed with platform-level fixes, such as OWASP ESAPI, instead of one by one.

Approach
Next step

Drowning in scanner findings? See a sample program gap analysis or book a strategy session.

Service
Application security
Explore the service

Details in this case study are anonymised and generalised. Methods that could harm other products are withheld.

FAQ

Frequently asked questions

What did ioSENTRIX do in this case study?

A large insurance company with hundreds of custom applications first hired ioSENTRIX for a penetration test. The issues we found pointed to design and architecture flaws, and to an application security program that was not working.

What was the most serious issue?

Scanners produced noise, not fixes. Real risks were lost in the noise, and the tools had lost the trust of the people meant to act on them.

What happened after the engagement?

Within eight months, no Critical or High vulnerabilities remained outstanding, as part of a three-year roadmap.

Which ioSENTRIX service does this case study cover?

Application security, delivered by the ioSENTRIX application security team.

Which standards does this align with?

OWASP SAMM v2: Implementation and Verification business functions. These are cited as alignment guidance, not a compliance claim.

How to get started

Ready to strengthen your security? Fill out our quick form, and a cybersecurity expert will reach out to discuss your needs and next steps.
DecorativeDecorative