← Breach analysis by the Dual Vulnerabilities framework

SolarWinds Orion supply-chain compromise (SVR/APT29, 2020)

2020 · United States · J - Information and communication · State-sponsored supply-chain attack via trojanized software updates

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

State-sponsored supply-chain attack via trojanized software updates

Dual vulnerability type

Expertise to Leadership

Evidence coverage: 4/6 stages, weight 29/60

Decisive stage: entry (tie-break: pre-breach condition) · Alternative: Expertise to Execution

Why this classification

(1) Strategic expectation: SolarWinds treated Orion as its crown-jewel product (45% of 2020 revenue, per the SEC complaint), its public Security Statement promised enforced passwords, least-privilege access and a tested secure development lifecycle, and a vendor whose update channel reaches federal agencies is expected to protect its build environment and act on its own risk findings. (2) In practice: SVR actors logged in with a compromised employee VPN account on 30 January 2019 (per investigators Wired interviewed) and stayed undetected for nearly two years; using compromised employee credentials they reached the Orion development environment, planted the SUNSPOT injector in the build system and had trojanized, SolarWinds-signed Orion updates distributed to roughly 18,000 customers between March and June 2020; the campaign was found by FireEye investigating its own breach (FireEye contacted SolarWinds on 12 December 2020), and CISA issued Emergency Directive 21-01 the next day. (3) Why Expertise to Leadership rather than merely weak security: the unacted-on knowledge sat with experts - a former employee's claimed 2017 warning to executives, the 2018 internal presentation on undetectable intrusion, and repeated 2018-2020 internal assessments describing a very vulnerable state and outstripped remediation capacity - yet the remedies SolarWinds itself disclosed after the breach (strictly enforced MFA, privileged access management, a redesigned, separated build pipeline) show these were not decided, resourced or enforced at the decision level before the intrusion; the chain broke where expert knowledge should have moved leadership decisions. The entry vector itself is not load-bearing (SolarWinds narrowed initial access to three candidate methods and excluded a known unpatched vulnerability); the classification rests on the pre-breach condition at the entry stage, which wins the tie-break against the load-bearing detection stage (an Expertise to Execution read: two-year dwell ended by an external victim) as the stage furthest before the breach moment, and the Strategy to Leadership pattern in the disputed Security Statement (secondary DV pattern; the court sustained it only as a viably pled claim and the case was dismissed without liability in November 2025) loses to the pre-breach condition under the pre-breach-wins rule. RM07 (Expertise to Leadership lens): warnings about the state of security and undetectable intrusion circulated internally from 2017 to 2020 without becoming decision-level action - the SEC alleges the head of security failed to resolve the issues or, at times, sufficiently raise them further within the company (causal role: Obscuring). RM08 (Expertise to Leadership lens): engineers reported the volume of security issues had outstripped the capacity of Engineering teams to resolve, yet the resourcing and enforcement measures the company implemented only after the breach were not funded or prioritised before it (causal role: Enabling). RM34 (Expertise to Leadership lens): detection capability was not built up despite the 2018 expert warning that an intruder could act without being detected until it is too late, so a nearly two-year presence in the company's own environment was discovered by an outside victim rather than by SolarWinds (causal role: Obscuring). RM44 (Expertise to Leadership lens): the company kept up a public Security Statement claiming enforced password policy, least-privilege access and a tested secure development lifecycle while internal presentations described a very vulnerable state of security - a specific discrepancy the court found viable enough to proceed to discovery (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

Row's three source URLs (CISA ED 21-01, Google/Mandiant SUNBURST technical details, Wired untold story) were all opened and used; SVR attribution is stated on the CISA ED 21-01 page (April 2021 update) and the FireEye post notes UNC2452 was merged into APT29. Legal status of the SEC material: SEC v. SolarWinds & Timothy G. Brown was filed 30 Oct 2023; on 18 July 2024 the court dismissed most claims, sustaining only the Security Statement misrepresentation claim and rejecting the post-SUNBURST disclosure claims as relying on hindsight and speculation (InformationWeek, opened); on 20 Nov 2025 the SEC dismissed the whole case with prejudice, with no liability established (SEC Litigation Release LR-26423, opened). The SEC's internal-assessment quotes are therefore allegations, not findings; they are cited as primary documents and the response stage is scored primary-open accordingly. Later filings (Joint Statement of Undisputed Facts) reportedly record SEC acknowledgement that several Security-Statement practices were in fact implemented - seen only in law-firm analyses, not independently opened, and given no weight here. Year = 2020, the year of the Orion code compromise the row describes (trojanized builds Mar-Jun 2020; ED 21-01 of 13 Dec 2020); initial intrusion into SolarWinds' corporate network predates it (30 Jan 2019 per investigators quoted by Wired; SolarWinds' own investigation states only at least nine months before its October 2019 test run, exact date undetermined). The 2017 executives-warning claim rests on a single former employee as reported by Wired (one-sided). Related row 911 (informationisbeautiful, same victim and incident): its case file does not exist in cases-run500 and no result-911.json exists in the output directory, so there was nothing to open or align with. incident_id and other fixed data-source columns are not carried by this cyberdefensemagazine row and remain null; nothing in the case file mismatches the stated victim SolarWinds. Unattended run: no action requiring consent was needed; only public sources were read. Link check: sec.gov blocks automated access (HTTP 403); the page was opened and read during research.