Sector · Industry

A formula does not lose value because the process moved to a new server.

Designs, formulas, production processes, and product engineering keep competitive value for decades. At the same time, much of the technology around them is operational: equipment that cannot stop, with a life cycle measured in many years and replacement that depends on the manufacturer.

Sector median · Critical industry87.5Critical
14,958companies
83.1–89.9Half of the cohort between p25 and p75
The comparison available

The industrial cohort is the largest on the operational ruler and occupies a middle position among the sectors with their own page: more exposed than technology, less than government and healthcare.

Internal dispersion is meaningful: size, degree of digitalization, and chain integration produce quite different positions within the same sector.The aggregates describe the cohort on the date the ruler was generated, with an anonymity floor. No company is identifiable in them.

Cohort distribution by band

  • Critical80.9%
  • High3.7%
  • Moderate0.2%
  • Minimal15.3%
Data shelf life

The relevant horizon here is competitive advantage, not contract term: a production process captured today and decrypted later would still be useful to a competitor if the product is still in production, and industrial products usually are.

Data the sector keeps for a long time

  1. Designs, formulas, and product specifications.
  2. Process parameters and production engineering.
  3. Supply contracts and long-term agreements.
  4. Unpublished research and development data.
What distinguishes the sector

Industry combines durable trade secrets with a rigid operational environment: the technology controlling production has availability constraints that office technology does not, and the decision to replace is rarely the operator's alone.

The sector's HNDL context. Risk here runs on two clocks. Intellectual property, which stays valuable for decades and therefore justifies capture today for later use. And the operational environment, whose cryptographic replacement depends on manufacturer, validation, and scheduled downtime, which makes the remediation timeline structural, not an internal decision.
  1. Trade secrets with long-term competitive value.
  2. Operational technology with continuous availability requirements.
  3. Equipment cycles measured in many years.
  4. Dependency on the manufacturer for any cryptographic change.

Typical dependencies

  • Equipment and control system manufacturers.
  • Integrators responsible for the operational environment.
  • A supply chain with direct digital integration.
  • Connectivity providers between plants and headquarters.

What applies

With an operational environment sensitive to interruption, the external readout is what fits, and the manufacturer chain is usually where prioritization pays off most.

01Exposure ReportA readout of the public surface, without touching the operational environment.In production
02Third-party assessmentRanking the manufacturer and integrator chain by exposure.In production
03Sector BenchmarkPosition against the industrial cohort, with percentile and band.In production
See the limits of this reading and what it is measured against

The limits of this readout

  • Collection does not reach isolated operational networks, which is where part of the risk lives.
  • The assessment is external and does not interact with industrial control systems.
  • The readout does not estimate cost, timeline, or feasibility of replacing equipment.
  • Sector medians authorize no conclusion about a specific company.

Boundary

Measurement ends at the technical change in the environment. Measuring exposure does not reduce it: reduction requires changing configuration, replacing certificates, switching negotiation policy, or migrating libraries. That work is carried out by the organization's own teams and suppliers. After the change, GWK re-collects public signals and recalculates IEQ on the same ruler, when contracted to do so.

Why measuring does not reduce exposure

What this comparison is measured against

Ruler generated
October 7, 2026
Population
80,182 companies
Sectors
15 sectors in the engine taxonomy
Anonymity floor
K = 30

Limits of the comparison

  • The ruler is a static reference base, not a continuous measurement: there is no automatic update between one run and the next.
  • Comparison is always against anonymous aggregates, never against another organization's individual result.
  • A public-mode result does not compare to a complete-mode result, because the two readings start from different kinds of evidence.

Start from the corporate surface

The external readout does not touch the operational environment and already shows corporate and chain exposure, which is where the prioritization decision usually starts.