At a glance
- 31% of breaches in Verizon’s 2026 report began with an exploited vulnerability, overtaking stolen credentials for the first time.
- 48% involved a third party, so suppliers’ systems are now part of every organisation’s own exposure.
- Only 13% of UK businesses had carried out a penetration test, while the gap between a flaw being published and being used is now measured in hours.
For most of its nineteen-year history, the Verizon Data Breach Investigations Report told the same story. Attackers got in by stealing or guessing the credentials of people who already had access.
The 2026 edition broke that pattern. Exploiting a known vulnerability was the way in for 31% of breaches, overtaking stolen credentials for the first time.
Automated tools have narrowed the gap between a flaw being disclosed and being used from months to hours. Yet the UK Government’s Cyber Security Breaches Survey 2025/2026 found that only 13% of businesses had carried out a penetration test, and 18% a vulnerability audit.
Why the Shift Matters
A stolen password belongs to a person. A vulnerability belongs to the system, exists whether or not anyone has made a mistake, and stays open until someone patches or reconfigures it.
Weaknesses like these are all visible from the outside:
- an unpatched server
- a forgotten test environment
- an exposed login page
- a misconfigured cloud service
The people scanning for them are rarely looking for one organisation in particular. They are looking for whoever has not yet closed the door.
Your Suppliers Are Part of Your Exposure
48% of breaches involved a third party. An organisation’s exposure no longer stops at the systems it runs itself.
Any of these can be the route in, and none appears in an internal review:
- a client portal built by an agency
- a booking platform hosted by a provider
- a network managed by an outsourced IT firm
In November 2026, Singapore Airlines, Cathay Pacific and Japan Airlines each reported passenger booking data exposed through a breach at Amadeus, the booking platform they share. Singapore Airlines was the only one that said its own IT systems were not breached.
What a Vulnerability Assessment Is and What It Finds
A vulnerability assessment is a technical review of networks, servers, and applications. It identifies known vulnerabilities, outdated software, and weak configuration.
Each finding is ranked by risk, so the team knows what to fix first. It is usually the right starting point, because it shows the full extent of what is exposed.
What a Penetration Test Adds
An assessment tells an organisation what is wrong. A penetration test shows what those weaknesses would allow, by testing them under controlled conditions from the internet and from inside the network.
The difference is often in how findings combine. Weaknesses that look moderate on their own can link into a route that none of them suggests individually.
Illustrative example, not a real case. An assessment of a mid-sized professional services firm returned a long list of medium-rated findings and nothing critical. Testing showed that three of them connected:
- A staging site left online after a website rebuild still accepted a default administrator password.
- The administrator panel exposed a list of internal hostnames.
- The internal network had no separation between staff systems and the document store.
Together, they formed a direct path from the internet to client files. The firm closed all three within a week.
Choosing How Far to Go
Every engagement is offered at three levels:
- Essential: identifies and ranks vulnerabilities and configuration weaknesses, with a summary of how exposed the organisation is.
- Standard: controlled testing of selected weaknesses to confirm which pose a real risk, with the impact each could have.
- Advanced: a full, scoped test that links weaknesses and follows realistic attack paths, with the report independently reviewed before release.
One retest is included at every level.
Each engagement begins with what an attacker could learn about the organisation from the outside, drawing on Futurum’s background in intelligence and investigations. It runs under signed Rules of Engagement that set out what will be tested, when, and by whom.
Nothing that could take systems offline is used. Testing stops if a system shows any sign of strain.
What a Useful Report Looks Like
A test is only as useful as what the organisation can do with it afterwards. A useful report includes:
- an executive summary for management on what was found and what it means for the business
- a full technical report, with each finding rated from Critical to Informational, supported by evidence and the steps to fix it
- a prioritised order for remediation
- immediate notification to a nominated contact if something critical is found during testing
- a debrief where management and technical teams agree what to fix first
- a retest and closure report, because a list of findings on its own does not show that anything has changed
When Organisations Commission Testing
Testing is usually prompted by a specific requirement or change:
- a customer, insurer, auditor or regulator asks for evidence of independent testing
- a new website, client portal or application is about to go live
- a move to cloud hosting or a change of IT provider
- a merger or acquisition that brings in unfamiliar systems
- a security incident in the organisation or its sector
- an annual review, or a tender that requires a recent test
Where none of these apply, regular testing is still worthwhile. Systems change constantly, settings drift and new vulnerabilities are published, and the gap between publication and attack is now measured in hours.
Just look at the recent Binance security breach story – it really does happen to the least expected, biggest firms out there.
If you would like to talk through where testing should start for your organisation, we are happy to have a confidential conversation.
