Deep dive: the Equifax breach
Equifax, 2017 · facts checked 2026-10-04
The facts
- GAO reported that on March 10, 2017, unknown individuals scanned Equifax for an Apache Struts flaw US-CERT had flagged two days earlier, and found the online dispute portal running a vulnerable version. (GAO)
- GAO said Equifax shared the US-CERT warning internally, but an outdated recipient list kept it from the staff responsible for patching the portal, and a later scan missed the flaw. (GAO)
- GAO said attackers who got into the portal from May 13, 2017 found unencrypted usernames and passwords, which let them reach 48 unrelated databases beyond the portal's own three. (GAO)
- According to GAO, the attackers ran about 9,000 database queries and moved stolen data out in small pieces over ordinary encrypted web traffic, going unnoticed for about 76 days. (GAO)
- GAO said an expired digital certificate had kept a monitoring tool from inspecting encrypted traffic; once it was updated, staff spotted the intrusion, which Equifax detected on July 29, 2017. (GAO)
- Equifax announced the incident on September 7, 2017, saying in a release filed with the SEC that it potentially affected about 143 million US consumers. (Equifax (SEC filing))
- The FTC announced in July 2019 that Equifax would pay at least $575 million, and possibly up to $700 million, to settle with it, the CFPB and 50 states and territories over a breach affecting about 147 million people. (FTC)
- GAO said Equifax's own review traced the breach to weaknesses in four areas: spotting the vulnerable system, detecting the attack, separating databases, and data governance, including protection of stored credentials. (GAO)
The panel
Jordan Pike AI host
GAO reports that on March 10, 2017, unknown individuals scanned Equifax for an Apache Struts flaw US-CERT had flagged two days earlier, and found the online dispute portal running a vulnerable version. GAO said Equifax shared the US-CERT warning internally, but an outdated recipient list kept it from the staff responsible for patching the portal, and a later scan missed the flaw.
Jordan Pike AI host
GAO said attackers who got into the portal from May 13, 2017 found unencrypted usernames and passwords, which let them reach 48 unrelated databases beyond the portal's own three. According to GAO, they ran about 9,000 database queries and moved stolen data out in small pieces over ordinary encrypted web traffic, going unnoticed for about 76 days. GAO also said an expired digital certificate had kept a monitoring tool from inspecting encrypted traffic; once it was updated, staff spotted the intrusion, which Equifax detected on July 29, 2017.
Jordan Pike AI host
Equifax announced the incident on September 7, 2017, saying in a release filed with the SEC that it potentially affected about 143 million US consumers. The FTC announced in July 2019 that Equifax would pay at least $575 million, and possibly up to $700 million, to settle with it, the CFPB and 50 states and territories over a breach affecting about 147 million people. GAO said Equifax's own review traced the breach to weaknesses in four areas: spotting the vulnerable system, detecting the attack, separating databases, and data governance, including protection of stored credentials.
Jordan Pike AI host
This is a breach everyone knows by name, so let's take it in order and ask what a defender can learn at each step. If you run a security team, a compliance team or a board, this one is for you. Sam, start at the front door.
Sam Kowalski AI analyst
The first lesson is ownership. A warning went out, but per GAO an outdated recipient list meant the people who patch the portal never saw it. That's a process failure, not a technology failure: a patch is only as fast as the list that carries the alert. Then a later scan missed the flaw, so the safety net had a hole too. You should be able to answer "where do we run this component, and who owns each system" without calling a meeting.
Nadia Haddad AI analyst (guest)
Notice the order in GAO's account: scanning first, access to the portal later. That gap was the window defenders had. And GAO says Equifax's own review points to data governance, including protection of stored credentials. Not legal advice, but "did you know what you held, and did you protect it" is the question any organisation should be able to answer before someone else asks it.
Sam Kowalski AI analyst
Once inside, the portal became a stepping stone. Passwords sitting unencrypted opened the way to far more databases than the portal's own. That's the classic pattern: the first foothold is rarely the prize, and stored credentials are the map to it. Segmentation and proper secrets handling are what keep a compromised web application a contained incident instead of a company-wide one.
Sam Kowalski AI analyst
Detection is where this one stings. Data left in small pieces over ordinary encrypted web traffic, which is exactly what an inspection tool exists to catch, and an expired certificate kept that tool blind. The house view is that every breach has indicators beforehand, and here the tool existed but failed quietly. Treat certificates on your security tooling as monitored assets, and test that your tools see what you think they see.
Jordan Pike AI host
You get one budget line. Where does it go: patch process, separating databases, or detection? Nadia, you first.
Nadia Haddad AI analyst (guest)
Governance and inventory first, because everything else hangs off knowing what you hold and who owns it. GAO's four areas make a decent checklist for a board. And a board needs exposure in business terms: which customers' data, which regulators, and how quickly you can tell them. The notification clock starts earlier than companies think.
Sam Kowalski AI analyst
I'd push back a little. No inventory is perfect, and here even a scan missed the flaw. So I put detection first as the safety net: assume something gets through, and make sure you'd see data leaving. And check how far back your logs go. "No evidence of compromise" means nothing if the logs don't cover the period, so assume access began earlier than your disclosure date.
Nadia Haddad AI analyst (guest)
Fair, and they aren't mutually exclusive. I'd add one thing: decide in advance who tells regulators and customers, and how fast. The time between detecting an intrusion and announcing it is not something to improvise.
Jordan Pike AI host
So: Monday morning? One action each.
Sam Kowalski AI analyst
Pick the tool you rely on to inspect encrypted traffic and confirm its certificates are current and that it sees what you think it sees. Then check that your alert distribution lists match who actually patches each system, and find out how long your logs are kept.
Nadia Haddad AI analyst (guest)
Ask for a map of where credentials and sensitive data are stored and who owns each location. Then put one page in front of your board in business terms: which customers, which regulators, which obligations, and who makes the call to notify.
Jordan Pike AI host
The short version: a warning that missed the right people, passwords stored in the clear, and a monitoring tool that couldn't see. None of it exotic, all of it fixable. Thanks, Sam and Nadia.





