Security operationsAnalysis
SecurityScorecard's ten risk factors sorted by what closes a finding, 125 products counted in TechBag's guides, and the 2022 vendor list re-checked, as of September 2026.
In 2022 we published a list that matched each of SecurityScorecard’s ten risk factors to products TechBag sold, 26 vendors in all. It answered a real question, the one every IT head asks after seeing a C or a D on a supplier portal: what do I buy to move this grade? The honest answer is that, for nearly half the factors, nothing. This piece sorts the ten by what actually fixes them, counts the products that exist for the rest, and checks what happened to the 2022 list.
SecurityScorecard defines each factor by what its scanners see from the outside. Network Security is open ports such as SMB and RDP, and insecure or misconfigured TLS certificates. DNS Health is open resolvers and the SPF, DKIM, DMARC and DNSSEC records. Cubit Score is critical configuration issues such as exposed administrative control panels. Application Security is vulnerabilities, misconfigurations and missing best practice on publicly visible web applications.1 Every item on those four lists is a setting: a port that should be closed, a record that should be published, a login page that should not face the internet, a header the web server should send.
Four factors are settings you change; four need a product running on the estate
SecurityScorecard's ten risk factors, sorted by what closes a finding, TechBag reading of the vendor's definitions
Fixed in configuration
Needs a product on the estate
Source: SecurityScorecard, How Does Scoring Work? (factor appendix); TechBag classification · as of 30 September 2026
The remaining two, Hacker Chatter and Social Engineering, measure discussion of your company in underground forums and the corporate accounts and marketing lists that are publicly findable.1 They are worth reading. They are not a shopping list. Since Scoring 3.0 in 2024, factors no longer carry weights of their own; the grade is built from more than 200 issue types weighted by how strongly each correlated with breach.2 The factor is now the label on a finding, which is a further reason to fix findings rather than buy for factors.
Application Security is the one configuration factor that sits on the border. Most of its findings, such as a missing security header or a server announcing its version number, are one line in a web-server configuration. Finding them across every subdomain the business has forgotten about is harder, and that is where a scanner earns its licence: it finds; the configuration change fixes. The same is true of Cubit Score’s exposed admin panels, which often sit on a subdomain someone set up for a project and never retired.1
For the factors that do need software, the choice is wide. On 30 September 2026 TechBag’s six decision guides that map to the ten factors listed 125 products by SKU. Endpoint protection, which answers both Endpoint Security and IP Reputation, held 36 of them from 20 vendors.6 The RMM and patch guide held 20 from 12 vendors,5 and the identity guide that covers MFA held 18 from 10.7
Endpoint protection has the most products to choose from; network security, a configuration factor, has the fewest
Products listed by SKU in each TechBag decision guide, mapped to the SecurityScorecard factor it answers, 30 September 2026
Source: TechBag decision guides, counted from the PRODUCTS list in each guide's source at the last commit of 30 September 2026 · as of 30 September 2026
A crowded shelf changes the buying question. For patching, the grade rewards cadence, how quickly updates land on the services the scanner can see, so the test in a proof of concept is reach: does the agent patch the internet-facing servers, including Linux, and the third-party applications on them, not only Windows laptops? For information leak, the fix is not detecting leaked passwords but making them worthless, which is MFA on every external login.
IP Reputation deserves its own warning. SecurityScorecard runs a network of sinkholes that capture malware calling home and maps the infected IP address back to an organisation.1 Behind an office firewall, every laptop leaves through a small pool of shared public addresses, so the finding names the office, not the machine. Only endpoint telemetry can say which laptop made the call, and that is the real argument for an EDR agent with searchable history over a signature antivirus: when the rating flags a host, the agent is how you find it, clean it and show the finding closed. Ask any vendor on the shortlist to demonstrate exactly that, starting from a public IP address and a timestamp.
Endpoint Security works the same way from the other side. The scanner sees the browser and operating-system versions that devices reveal when they connect to the internet, and grades how exploitable they look.1 An agent that keeps browsers current moves this factor faster than any detection feature, which is why patch reach and endpoint protection should be bought, or at least tested, together.
The DNS Health factor checks for the records that stop someone sending email as your domain: SPF, DKIM and DMARC.1 Publishing them is a change at your DNS host, and DMARC has been a published standard since March 2015.3 The order matters, because a DMARC policy set straight to reject will bounce legitimate mail from a payroll or marketing platform nobody remembered was sending on your behalf.
Getting DMARC to enforcement is four record changes, done in order over weeks, not a product
The sequence for publishing email authentication on a domain, per the DMARC specification
SPF
List every service allowed to send as the domain, including the payroll and marketing platforms.
DKIM
Turn on signing at each sender and publish its public key in DNS.
DMARC p=none
Publish a monitoring policy with a report address and read the aggregate reports for a few weeks.
Quarantine, then reject
Tighten the policy once every legitimate sender passes; spoofed mail then stops at the receiver.
Source: RFC 7489, Domain-based Message Authentication, Reporting and Conformance (DMARC) · as of 30 September 2026
The original post named 26 vendors across the ten factors. Sixteen have a TechBag intel hub as of 30 September 2026, with dated prices and the India facts. Comodo’s enterprise business now trades as Xcitium, renamed in 2022,8 and SolarWinds has been private under Turn/River Capital since 16 April 2025.9 Kaspersky has been barred from new sales in the United States since 20 July 202410; it remains on sale in India, and TechBag’s endpoint guide lists it with a price.6
Sixteen of the 26 vendors the 2022 post named now have a TechBag intel hub; three changed name, owner or market
Share of the 26 vendors recommended in the July 2022 post, status on 30 September 2026
61.5%
With a TechBag intel hub
16 of 26 vendors
11.5%
Renamed, sold or barred from new US sales
3 of 26: Comodo to Xcitium, SolarWinds to Turn/River, Kaspersky
Source: TechBag estate at the last commit of 30 September 2026; Xcitium and SolarWinds hubs; US BIS · as of 30 September 2026 · The two groups overlap: Xcitium and SolarWinds have hubs
The ten without a hub are Automox, PDQ, Patch My PC, Miradore, IPM+, Sumo Logic, SecurityScorecard itself, AppSealing, OneSpan and Authentic8. Some of the 2022 mapping was also wrong on its own terms: Jira, an issue tracker, was filed under patching; Datadog, an observability platform, under IP reputation; and the Authentic8 entry carried Proofpoint’s product description word for word.
Sources
Related on TechBag: the companion note on what a SecurityScorecard grade means, and the vulnerability management guide for the scanners that find application and exposed-panel issues before a rating does.
Disclosure. TechBag is a software reseller: it earns a margin when a reader buys through it, including from vendors named here. The analysis is TechBag’s own; no vendor paid for or saw this piece before publication. Facts are labelled reported, TechBag count or our view.