Nvidia's CSO Left in August; No Evidence Ties Exit to Chip Probe

Nvidia's chief security officer left in August after seven years at the company, and roughly two and a half months later Jensen Huang's exit pushed the same question into every headline: where was Nvidia's security team? Yahoo Finance raised it this week while assembling reporting on David Reber's departure, his replacement, and a U.S. probe into a Singapore data-center company called Megaspeed.

The honest answer is that nobody outside the company knows. No public evidence in the available reporting ties the security leadership change to Megaspeed, and it's unclear whether the team even knew about the government's scrutiny. Nvidia, Reber, and his successor all declined to answer questions.

What is actually on the record?

Three stories collided in recent weeks, and readers naturally stitch them into one narrative. The verified facts are narrower:

• Departing chief: David Reber, CSO and head of product security — seven years at Nvidia, four as CSO.
• Reason given: Health. Reber cited a young-onset Parkinson's diagnosis he received more than two years earlier. He worked through most of his CSO tenure with the condition.
• Replacement: Saša Zdjelar, whose background runs 17 years at ExxonMobil, one year at Salesforce, and several years at ReversingLabs, a software supply-chain and malware-analysis firm.
• CEO timing: Huang reportedly left about two and a half months after Reber.
• Probe subject: Megaspeed, a Singapore data-center company that U.S. investigators reportedly suspect of funneling Nvidia chips to China — a reported suspicion, not a legal finding, with no charges shown in the available material.
• Company comment: None. Nvidia, Reber, and Zdjelar did not respond to questions.

Two details deserve emphasis. The health explanation is specific and came from Reber himself, making it the best-documented fact in the whole sequence. And the absence of any public link to Megaspeed is itself a finding — the dramatic reading has no support so far.

Why the health disclosure matters

The timeline is worth sitting with. A diagnosis more than two years old means Reber chose to step down in August after managing the condition through most of his time as CSO. The simplest explanation for a senior executive's departure is the one the executive gave, and no evidence has contradicted it. Linking a medical departure to an unrelated corporate scandal risks implying something unfair and unproven.

What does a CSO actually own at a chip giant?

Reber's dual remit matters here. Product security — how chips, firmware, and drivers resist tampering, and how the company responds to researchers' findings — sits at the intersection of corporate protection and customer trust. Failures there show up as CVEs and advisories, not export probes.

Deciding whether a customer in Singapore is a safe buyer typically belongs to export-compliance and legal functions, not the security team. A CSO rarely sits in the room where customer-eligibility decisions get made, and security leaders often learn about regulatory trouble through counsel. The reporting doesn't say how Nvidia divides those duties. The open issue is about knowledge, not causation: what did the security function know, and when?

What does this change for AI infrastructure buyers?

Buyers commit to clusters, software stacks, and supply contracts that run for years. Losing a CSO and a CEO within a quarter raises a practical question: how stable is the team that patches the products they depend on? There's no evidence product security has weakened — this is about diligence, not alarm. Procurement teams should ask Nvidia for continuity statements, patch cadence, and named contacts. There's an indirect risk, too: if investigators tighten scrutiny on chip routes through third countries, even fully legitimate customers could face new certification demands and slower deliveries.

Investors get their next hard data point on Nov. 17, when Nvidia reports earnings. A board statement on the security function, a permanent leadership structure, or any disclosure about internal risk-flagging would move sentiment. None of that has happened publicly, so forecasting a price reaction would be guesswork.

What to watch next

Until new facts land, the best-supported summary stays short. A security chief left for health reasons. A veteran from energy and software security took his place. A separate probe into chip routing continues. And no public evidence ties those threads together.