A generic supplier score grades a supplier's whole external surface, so every customer sees the same rating. A connected score keeps only the findings on assets that link the supplier to you, found by passive discovery with evidence. Use generic for due diligence, connected for remediation.
A connected supplier score grades a supplier only on the parts of its infrastructure that are digitally connected to your organization. A generic score, or security rating, grades the supplier's whole external surface, so every customer sees the same result. The connected score keeps the findings that can reach you and drops the ones that can't.
When I demo this, I use a large hosting provider. On the generic view, it carries a little over 5,000 findings. Nobody is going to work through 5,000 findings, and nobody knows where to start with them. Then I switch on the connected view, and 41 are left. Those 41 sit on the assets my demo organization actually uses. The other findings are real, they just belong to parts of the hosting company I never touch.
We added the connected score in version 7.1 of the ThingsRecon platform, next to the generic score we already had. It builds on Digital Proximity, which maps how closely each supplier is technically connected to you. Proximity finds the connections, and the connected score grades the findings on them. Below is how the two scores differ in practice, and where the connected score runs out of sight.
What does a generic supplier score measure?
A generic score measures a supplier's whole external surface: hygiene findings across its domains, certificates, exposed services and configurations. In our platform, it also takes in business intelligence such as financial status. Every customer of that supplier sees the same grade, because the score describes the supplier on its own and says nothing about how it reaches you.
That's useful, and we kept it. The generic score is the right view when you're comparing vendors in the same bucket during due diligence. It's also what security rating platforms have sold for years, so most teams already have processes built around it. When a customer wires our scores into their vendor management workflow, I expect them to keep the generic score in the field it already lives in, and add the connected score as a second field.
Why does a generic score lead to the wrong remediation requests?
Because the findings you send to a supplier get picked from its whole surface. A team takes the criticals from the generic report and asks the supplier to fix them. The supplier fixes them and looks better on paper, while a weakness on the asset you actually connect to may never make the list, and nobody knows it's there.
In a recent demo, the prospect's existing security rating tool had sent them a generic report with around 24,000 issues across their suppliers, with nothing to say why any of them mattered to that organization.
The next steps are predictable: filter by severity, send the list, check at the next scan cycle whether it was fixed. Each step works as designed. The selection at the start is where it goes wrong, because it was made without context.
We wrote about the breach version of this in Your supplier got an A. So why were you breached?, and Robin made the wider case for scoring the connection in Risk follows the connection.
What changes when you switch to the connected score?
The findings get filtered down to the assets that link the supplier to you, and the supplier's position in your list moves with them. Suppliers embedded in live services climb. Suppliers whose findings sit on infrastructure you never use drop down the list, even when their generic grade is poor.
In the demo above, the connected view takes the hosting provider from 5,000+ findings to 41. The rest sit on components, domains, URLs or hostnames my organization doesn't use. Now I have a list I can work with, and every item on it shows the relationship that links me to it. That relationship can be a script, a header, an API call, or a page hosted on the supplier's infrastructure.
The question the team asks changes too. With the connected view open, they ask how this supplier is affecting them, which is the question their board will ask anyway. It's also the version of the conversation you can take to the supplier: for us to keep working together, this specific thing on this specific asset needs fixing.
How does ThingsRecon decide that a supplier is connected to you?
ThingsRecon Supply Chain Intelligence runs passive discovery from the outside, starting from your domains, and records every relationship we observe between your assets and a supplier's infrastructure. That includes:
- Embedded JavaScript
- Headers
- API endpoints
- Hosting
- DNS
- Registrars
Each relationship is stored with the evidence that produced it, so you can see why we think the connection exists. These are the same relationships Digital Proximity uses to score how close a supplier sits to you.
We also separate direct from indirect impact. If your application calls a supplier's API endpoint, a finding on that endpoint affects you directly. If we find an outdated library on the supplier's own marketing website, that's indirect. It's worth knowing about, but the supplier may never fix it and it isn't in the path of your data.
The platform marks each finding on that basis, letting you know what needs to be fixed now and what can wait. The same logic extends to the providers behind your suppliers, or fourth-parties.
Where does business intelligence come into the score?
Business intelligence now feeds the supplier score alongside cyber hygiene. It covers financial status, geopolitical associations, compliance signals and OSINT from news sources. Each data point shows a confidence percentage and its sources, so you can check where a value came from before you act on it.

The larger the company, the more data points we can collect about it. We also handle corporate structures. When the service you use belongs to a larger group, revenue and headcount roll up to the parent, while the hosting locations that matter for geopolitical risk stay with the specific service you depend on. That distinction matters when the parent is headquartered in one country and the servers holding your data are in another.
What can't a connected score see from the outside?
It can't see connections that never touch the public internet. A site-to-site VPN or a file sent over a private channel won't show up in passive discovery. A supplier holding sensitive data through one of those routes can look unconnected from the outside, even when losing it would hurt.
One approach we're exploring is to bring in the business context customers already hold, such as questionnaire answers about the data a supplier handles. That would let the platform weigh a supplier you depend on even when the scanner can't see the link.
Switch your top 20 suppliers to the connected score
If you're a ThingsRecon customer, open Supply Chain Intelligence, switch your top 20 suppliers to the connected score and look at what moved. The ones that climb are the suppliers your business runs on. If you're not a customer yet, send us your domain and we'll map your connections in a working session.





