Cybersecurity software vendors

Companies that sell software and services to protect networks, devices, identities and data. It has no schema of its own: companies here are mapped on the Software & SaaS schema, and what it does not cover is recorded as gaps.

Baseline: Software & SaaS v2
Inherited from: Software & SaaS
Mapped on the schema: 6 of 101 placed here
Primitives: 58 in 8 parts
Last updated: 2 Nov 2026

What the registry holds here

Cybersecurity software vendors and below · public parts only

With public findings: 101
Public parts: 211
Distinct sources: 193
Last change: 3 Nov 2026

Organizations by public parts

Counts of what public research has found and sourced, each part with its source on the organization’s profile. They say what is known, not how much of the industry exists.

Deepen this industry

Focused research on the organizations with the fewest mapped parts in cybersecurity software vendors; what it finds is public for everyone.

Norton1 part
YesWeHack1 part
Cylance Inc.1 part
Clavister1 part
Anonymizer1 part

How automatable each primitive is, estimated from the 19 organizations mapped in public on the Software & SaaS schema, which this industry inherits: the share of those with the primitive that run it on software. Estimate from public data: the share of mapped organizations that run this on software. Not a recommendation.

LevelAll58 High6 Medium32 Low20

Primitive	Layer	Automation	Peers on software	Software parts named most
Ideal customer and positioning Demand: winning customers	Decisions	LowEstimate	0 of 14 on software	—
Pipeline generation Demand: winning customers	Process	MediumLayer only	3 of 19 mapped; too few to read	—
Sales Demand: winning customers	People	LowEstimate	0 of 5 on software	—
Packaging and pricing Demand: winning customers	Decisions	LowLayer only	1 of 19 mapped; too few to read	—
Quotes and order forms Demand: winning customers	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Subscription agreements Demand: winning customers	Decisions	LowLayer only	3 of 19 mapped; too few to read	—
Product management Supply: making or delivering the offer	Process	HighEstimate	9 of 11 on software	AI-Powered (8), Facial Recognition (3), Surveillance Drones (3)
Sprint and capacity planning Supply: making or delivering the offer	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Procurement Supply: making or delivering the offer	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Suppliers and partners Supply: making or delivering the offer	People	LowLayer only	2 of 19 mapped; too few to read	—
Running the service Supply: making or delivering the offer	Process	MediumLayer only	2 of 19 mapped; too few to read	—
Testing and QA Supply: making or delivering the offer	Process	MediumLayer only	1 of 19 mapped; too few to read	—
Code, infrastructure and licences Supply: making or delivering the offer	Data	MediumLayer only	2 of 19 mapped; too few to read	—
Provisioning Supply: making or delivering the offer	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Product roadmap Supply: making or delivering the offer	Decisions	LowLayer only	1 of 19 mapped; too few to read	—
Engineering delivery Supply: making or delivering the offer	Process	MediumLayer only	1 of 19 mapped; too few to read	—
Releases and change communication Supply: making or delivering the offer	Process	MediumLayer only	4 of 19 mapped; too few to read	—
Uptime and incidents Supply: making or delivering the offer	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Implementation Customers: keeping them	Process	MediumLayer only	1 of 19 mapped; too few to read	—
Customer support Customers: keeping them	People	LowLayer only	0 of 19 mapped; too few to read	—
Customer success Customers: keeping them	People	LowLayer only	0 of 19 mapped; too few to read	—
Customer data Customers: keeping them	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Renewals Customers: keeping them	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Onboarding and activation Customers: keeping them	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Churn and expansion Customers: keeping them	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Invoicing Money: getting paid and paying	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Collections and receivables Money: getting paid and paying	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Payments and payables Money: getting paid and paying	Process	MediumLayer only	1 of 19 mapped; too few to read	—
Payroll Money: getting paid and paying	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Revenue recognition and close Money: getting paid and paying	Software	HighLayer only	0 of 19 mapped; too few to read	—
Plan and burn Money: getting paid and paying	Decisions	LowLayer only	0 of 19 mapped; too few to read	—
Cash and treasury Money: getting paid and paying	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Subscription billing Money: getting paid and paying	Software	HighLayer only	0 of 19 mapped; too few to read	—
Unit economics Money: getting paid and paying	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Cloud and hosting costs Money: getting paid and paying	Data	MediumLayer only	1 of 19 mapped; too few to read	—
Org structure People: who does the work	People	LowLayer only	3 of 19 mapped; too few to read	—
Hiring People: who does the work	Process	MediumLayer only	3 of 19 mapped; too few to read	—
Onboarding and training People: who does the work	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Performance and pay People: who does the work	Decisions	LowLayer only	1 of 19 mapped; too few to read	—
Scheduling and capacity People: who does the work	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Policies and culture People: who does the work	Decisions	LowLayer only	1 of 19 mapped; too few to read	—
Core system of record Systems: tools and data	Software	HighLayer only	0 of 19 mapped; too few to read	—
Communication tools Systems: tools and data	Software	HighLayer only	0 of 19 mapped; too few to read	—
Integrations Systems: tools and data	Software	HighLayer only	0 of 19 mapped; too few to read	—
Metrics and board reporting Systems: tools and data	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Data management Systems: tools and data	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Security and access Systems: tools and data	Decisions	LowLayer only	1 of 19 mapped; too few to read	—
Product analytics Systems: tools and data	Data	MediumLayer only	1 of 19 mapped; too few to read	—
Licences and registrations Control: rules the company runs under	Decisions	LowLayer only	0 of 19 mapped; too few to read	—
Regulatory compliance Control: rules the company runs under	Decisions	LowLayer only	2 of 19 mapped; too few to read	—
Insurance and risk Control: rules the company runs under	Decisions	LowLayer only	0 of 19 mapped; too few to read	—
Legal and contracts administration Control: rules the company runs under	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Health, safety and environment Control: rules the company runs under	Decisions	LowLayer only	0 of 19 mapped; too few to read	—
Data protection and security assurance Control: rules the company runs under	Decisions	LowLayer only	2 of 19 mapped; too few to read	—
Strategy and goals Direction: deciding where it goes	Decisions	LowEstimate	0 of 8 on software	—
Governance and decision rights Direction: deciding where it goes	Decisions	LowEstimate	0 of 11 on software	—
Management cadence Direction: deciding where it goes	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Learning and improvement Direction: deciding where it goes	Process	MediumLayer only	2 of 19 mapped; too few to read	—

The rule, the same for every industry: with 5 or more organizations having the primitive, 50% or more of them on software is high, 20% or more medium, below that low. With fewer, the level rests on the primitive's layer alone and says "Layer only". Software parts are counted once per organization; a detected technology is named by its product. See the blueprint for which organizations run each.

LevelAll58 High6 Medium32 Low20

Primitive	Layer	Automation	Peers on software	Software parts named most
Ideal customer and positioning Demand: winning customers	Decisions	LowEstimate	0 of 14 on software	—
Pipeline generation Demand: winning customers	Process	MediumLayer only	3 of 19 mapped; too few to read	—
Sales Demand: winning customers	People	LowEstimate	0 of 5 on software	—
Packaging and pricing Demand: winning customers	Decisions	LowLayer only	1 of 19 mapped; too few to read	—
Quotes and order forms Demand: winning customers	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Subscription agreements Demand: winning customers	Decisions	LowLayer only	3 of 19 mapped; too few to read	—
Product management Supply: making or delivering the offer	Process	HighEstimate	9 of 11 on software	AI-Powered (8), Facial Recognition (3), Surveillance Drones (3)
Sprint and capacity planning Supply: making or delivering the offer	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Procurement Supply: making or delivering the offer	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Suppliers and partners Supply: making or delivering the offer	People	LowLayer only	2 of 19 mapped; too few to read	—
Running the service Supply: making or delivering the offer	Process	MediumLayer only	2 of 19 mapped; too few to read	—
Testing and QA Supply: making or delivering the offer	Process	MediumLayer only	1 of 19 mapped; too few to read	—
Code, infrastructure and licences Supply: making or delivering the offer	Data	MediumLayer only	2 of 19 mapped; too few to read	—
Provisioning Supply: making or delivering the offer	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Product roadmap Supply: making or delivering the offer	Decisions	LowLayer only	1 of 19 mapped; too few to read	—
Engineering delivery Supply: making or delivering the offer	Process	MediumLayer only	1 of 19 mapped; too few to read	—
Releases and change communication Supply: making or delivering the offer	Process	MediumLayer only	4 of 19 mapped; too few to read	—
Uptime and incidents Supply: making or delivering the offer	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Implementation Customers: keeping them	Process	MediumLayer only	1 of 19 mapped; too few to read	—
Customer support Customers: keeping them	People	LowLayer only	0 of 19 mapped; too few to read	—
Customer success Customers: keeping them	People	LowLayer only	0 of 19 mapped; too few to read	—
Customer data Customers: keeping them	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Renewals Customers: keeping them	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Onboarding and activation Customers: keeping them	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Churn and expansion Customers: keeping them	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Invoicing Money: getting paid and paying	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Collections and receivables Money: getting paid and paying	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Payments and payables Money: getting paid and paying	Process	MediumLayer only	1 of 19 mapped; too few to read	—
Payroll Money: getting paid and paying	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Revenue recognition and close Money: getting paid and paying	Software	HighLayer only	0 of 19 mapped; too few to read	—
Plan and burn Money: getting paid and paying	Decisions	LowLayer only	0 of 19 mapped; too few to read	—
Cash and treasury Money: getting paid and paying	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Subscription billing Money: getting paid and paying	Software	HighLayer only	0 of 19 mapped; too few to read	—
Unit economics Money: getting paid and paying	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Cloud and hosting costs Money: getting paid and paying	Data	MediumLayer only	1 of 19 mapped; too few to read	—
Org structure People: who does the work	People	LowLayer only	3 of 19 mapped; too few to read	—
Hiring People: who does the work	Process	MediumLayer only	3 of 19 mapped; too few to read	—
Onboarding and training People: who does the work	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Performance and pay People: who does the work	Decisions	LowLayer only	1 of 19 mapped; too few to read	—
Scheduling and capacity People: who does the work	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Policies and culture People: who does the work	Decisions	LowLayer only	1 of 19 mapped; too few to read	—
Core system of record Systems: tools and data	Software	HighLayer only	0 of 19 mapped; too few to read	—
Communication tools Systems: tools and data	Software	HighLayer only	0 of 19 mapped; too few to read	—
Integrations Systems: tools and data	Software	HighLayer only	0 of 19 mapped; too few to read	—
Metrics and board reporting Systems: tools and data	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Data management Systems: tools and data	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Security and access Systems: tools and data	Decisions	LowLayer only	1 of 19 mapped; too few to read	—
Product analytics Systems: tools and data	Data	MediumLayer only	1 of 19 mapped; too few to read	—
Licences and registrations Control: rules the company runs under	Decisions	LowLayer only	0 of 19 mapped; too few to read	—
Regulatory compliance Control: rules the company runs under	Decisions	LowLayer only	2 of 19 mapped; too few to read	—
Insurance and risk Control: rules the company runs under	Decisions	LowLayer only	0 of 19 mapped; too few to read	—
Legal and contracts administration Control: rules the company runs under	Data	MediumLayer only	0 of 19 mapped; too few to read	—
Health, safety and environment Control: rules the company runs under	Decisions	LowLayer only	0 of 19 mapped; too few to read	—
Data protection and security assurance Control: rules the company runs under	Decisions	LowLayer only	2 of 19 mapped; too few to read	—
Strategy and goals Direction: deciding where it goes	Decisions	LowEstimate	0 of 8 on software	—
Governance and decision rights Direction: deciding where it goes	Decisions	LowEstimate	0 of 11 on software	—
Management cadence Direction: deciding where it goes	Process	MediumLayer only	0 of 19 mapped; too few to read	—
Learning and improvement Direction: deciding where it goes	Process	MediumLayer only	2 of 19 mapped; too few to read	—