Deep dive: the SolarWinds supply-chain hack
SolarWinds Orion, 2020 · facts checked 2026-10-04
The facts
- SolarWinds told the SEC that the malicious code entered Orion through a breach of its software build system, and that its source code repository did not contain it. (SolarWinds (SEC filing))
- GAO said that from February 2020 the attackers planted hidden code in a file that SolarWinds went on to include in its Orion software updates. (GAO)
- SolarWinds told the SEC that the tainted Orion updates were released between March and June 2020, and that fewer than 18,000 customers may have installed one. (SolarWinds (SEC filing))
- CISA said the actor used elevated Active Directory privileges to compromise SAML signing certificates, then forged tokens that services such as hosted email trusted, to collect data. (CISA)
- GAO said the security firm FireEye detected an intrusion into its own systems in November 2020 and later told SolarWinds that the Orion platform had been compromised. (GAO)
- On December 13, 2020, CISA issued an emergency directive telling federal agencies to take affected SolarWinds Orion products off their networks or shut them down at once. (CISA)
- In April 2021 the White House named Russia's foreign intelligence service, the SVR, as responsible, saying the hack gave it the means to spy on or possibly disrupt over 16,000 computer systems around the world. (White House)
- Announcing a May 2021 cybersecurity executive order, the White House pointed to SolarWinds as a recent incident and said the order would set baseline security standards for developing software sold to government. (White House)
The panel
Jordan Pike AI host
SolarWinds told the SEC that the malicious code entered Orion through a breach of its software build system, and that its source code repository did not contain it. GAO said that from February 2020 the attackers planted hidden code in a file that SolarWinds went on to include in its Orion software updates. SolarWinds told the SEC that the tainted Orion updates were released between March and June 2020, and that fewer than 18,000 customers may have installed one.
Jordan Pike AI host
CISA said the actor used elevated Active Directory privileges to compromise SAML signing certificates, then forged tokens that services such as hosted email trusted, to collect data. GAO said the security firm FireEye detected an intrusion into its own systems in November 2020 and later told SolarWinds that the Orion platform had been compromised. On December 13, 2020, CISA issued an emergency directive telling federal agencies to take affected SolarWinds Orion products off their networks or shut them down at once.
Jordan Pike AI host
In April 2021 the White House named Russia's foreign intelligence service, the SVR, as responsible, saying the hack gave it the means to spy on or possibly disrupt over 16,000 computer systems around the world. Announcing a May 2021 cybersecurity executive order, the White House pointed to SolarWinds as a recent incident and said the order would set baseline security standards for developing software sold to government.
Jordan Pike AI host
That is the whole timeline. Let's take it in order. Maya, the first step: why does it matter that the code was in the build system and not in the source repository?
Maya Okafor AI analyst
Because most review and scanning looks at the repository. If the tampering happens during the build, what was reviewed and what was shipped are no longer the same thing. No weakness class was disclosed in these facts, so this isn't a classic coding bug. It's a build integrity failure: nothing proved the output matched the input. And the file went out inside ordinary updates, which customers had every reason to install.
Maya Okafor AI analyst
A complete fix for this class isn't a better scanner on the repo. It's treating the build system as a crown jewel: locked-down access, builds you can reproduce and compare, and alerts when a build output differs from what the source should produce. A partial fix is cleaning up the one file and moving on. If the build environment stays open, the attacker's way in is still there.
Jordan Pike AI host
Rina, once an update is installed, what are the attackers actually after?
Rina Takahashi AI analyst
Identity. CISA's account is the telling part: elevated Active Directory privileges, then the SAML signing certificates. Whoever holds those can mint tokens that services trust, so hosted email sees what looks like a legitimate login. No password is guessed and nothing trips an alarm for a failed sign-in. The update was the door; the signing keys were the prize. For defenders, that means identity infrastructure deserves the same protection as the crown-jewel servers.
Jordan Pike AI host
Then discovery. How did it come to light?
Rina Takahashi AI analyst
Per GAO, a security firm noticed an intrusion into its own systems and traced it back to the platform. Customers did not find it first. That's a pattern worth sitting with: a trusted vendor channel is one of the hardest places to spot bad behaviour, because it looks like routine software. It also ties to a house view on this panel, which is opinion, not reporting: breaches usually have earlier indicators that were missed. And "no evidence of compromise" means little unless you know how long your logs go back.
Maya Okafor AI analyst
That's why log retention matters here. If your logs don't cover the window between the first tainted update and the discovery, you can't say you were clean. You can only say you can't tell. That's a very different sentence to give your board.
Jordan Pike AI host
Now the response. CISA told federal agencies to pull the products or shut them down at once. Is that the model for everyone else, or was it specific to that moment?
Rina Takahashi AI analyst
That directive was for federal agencies, so it's their instruction, not a universal deadline. But the logic carries over: when a trusted update channel is compromised, isolating first and investigating second is a defensible call. I'd also stress the attribution. The White House named the SVR. That is a government's claim, and the facts we have don't give a confidence level, so treat the name as the official position. It does matter for planning, though, because an intelligence service has the means to spy and possibly disrupt, and that shapes how patient you expect the intruder to be.
Maya Okafor AI analyst
My view is different on where to put the effort. Most organisations don't run a build system for a product like this, but they all consume updates. So I'd push hard on supplier questions: how do you protect your build, how would you know it was tampered with, and what do you tell us when it happens? A one-time questionnaire isn't enough. Ask for evidence.
Rina Takahashi AI analyst
I'd agree on the questions, but you can't audit your way out of this. You don't control the supplier's build, so your own controls come first: limit what update channels can reach, guard the signing certificates, and watch for tokens that don't match a real sign-in. Suppliers are slow to change. Your identity logging is something you can fix this quarter.
Maya Okafor AI analyst
Fair, though those are bridges. They reduce the damage; they don't remove the supply risk. Give each one an owner and an end date, and keep pushing suppliers in parallel. The executive order is a start on that: baseline standards for how software sold to government is built. Baselines help, but only if someone verifies them.
Jordan Pike AI host
So: Monday morning? Maya, one action each, then Rina.
Maya Okafor AI analyst
List every product in your estate that updates itself with privileged access, and ask each supplier how they protect and verify their build. Written answers, not reassurance.
Rina Takahashi AI analyst
Treat your SAML signing certificates and the accounts that can reach them as top-tier assets. Check how far back your identity and email logs go, and make sure someone is looking for forged-token patterns.
Jordan Pike AI host
Short version: a trusted update was the way in, identity was the real target, and a security firm spotting its own intrusion was how it came out. Check your suppliers, guard your signing keys, and keep your logs.





