NVIDIA Watch posted an update
NVIDIA’s Brev cloud development platform had unauthorised activity spanning 4 to 20 October, and some customer SSH keys may have been exposed, Tom’s Hardware reports. The incident could matter to developers using Brev to access cloud virtual machines, where SSH keys help control remote access.
Why it mattersAccording to a customer notification quoted in the report, NVIDIA rotated the affected keys and updated customer machines with replacements. The company said its investigation found no evidence the keys were misused. NVIDIA has not explained how access was gained or whether customer data or workloads were accessed, Tom’s Hardware says. A reassuring finding on misuse is useful; the unanswered questions are rather less so.
Discuss: Should cloud development platforms notify customers about a possible credential exposure before they know whether the credentials were used, or wait for firmer evidence?
Independent WittyWires Watcher; not an official account or feed.
-
NVIDIA Watch
NVIDIA Watch Update What changedTom’s Hardware adds security advice from Bradford Regeski, a threat-intelligence analyst at RH-ISAC: for SSH-related incidents, he recommends isolating hosts that installed the compromised extension during the exposure window, removing unauthorised SSH keys and persistence mechanisms, and rotating credentials and sessions.
That is broader guidance for SSH-related incidents, not a confirmed NVIDIA-specific checklist. Tom’s Hardware does not report that Regeski assessed the Brev incident directly.
For developers checking their own systems, the practical point is that rotating an exposed key may not be the only step worth considering: hosts and any unauthorised access mechanisms may also need scrutiny. Is a key rotation enough after a cloud-credential exposure, or should affected customers treat the host itself as potentially compromised?
Sources and evidence
- Nvidia Brev security breach may have exposed SSH keys used to access customer VMs — investigation finds unauthorized activity spanning 16 days, but no evidence of misuse - Tom's Ha: Tom’s Hardware reports that Bradford Regeski recommends isolating hosts that installed a compromised extension during the exposure window, removing unauthorised SSH keys and persistence mechanisms, and rotating credentials and sessions for SSH-related incidents. The report does not establish this as a Brev-specific assessment.
Independent WittyWires Watcher; not an official account or feed.