โ† Back to dashboard ๐Ÿ”’ Premium โ€” subscriber access

Master OT Exposure Scorecard

File: pipeline/data/ot_master_scorecard.csv Date: 2026-04-20 (scorecard regenerates daily โ€” see current version via the scorecard request form) Rows: 24,687 organizations (as of 2026-04-20; grows with each scraping pass)

Versioning: The CSV itself is regenerated with each pipeline run. Scores and rankings shift as new court data arrives. This README documents the methodology and scoring formula, which is stable across versions.

What this is

A flat CSV ranking every organization in our OT-connected universe by a composite priority score. Enables downstream filtering, triage, and designation prioritization.

๐Ÿ”’ Premium brief โ€” full access

This brief's evidentiary detail, specific targets, and designation recommendations are available to vetted compliance teams, law firms, and government analysts โ€” as single-brief purchases or under a portfolio monitoring retainer. The teaser above shows the headline methodology; the full document includes case-number citations, target INNs, SDN-adjacency numbers, and recommended secondary-designation scope.

Already subscribed? Open the full brief with your analyst credentials. Otherwise, subscribe to portfolio monitoring for the full library, or commission this brief on its own.

Read the full brief โ†’ See access options Request by email
Basis and limitations. Findings in this brief are derived from public records โ€” kad.arbitr.ru arbitration filings, EGRUL registry extracts, zakupki.gov.ru procurement contracts, and official sanctions lists โ€” and from algorithmic scoring described in the methodology. Scores are triage outputs, not legal determinations. Court co-litigation measures litigation frequency with listed parties, not culpability; procurement links may reflect arm's-length commerce. Named entities may dispute factual errors via derek.linz@linzalytics.com (subject "Dispute request"); the review process and timelines are on the methodology page, and material corrections are logged at /intel/corrections.html with dates.