Your vendor's vendor had the bad week
Free weekly email
This went to subscribers on November 17. Get the next one.
One email every Tuesday: what changed in security and compliance that week, and what it means if you sell to enterprise buyers.
Free. Unsubscribe in one click, and replies reach Jacob directly. Read the latest issue or browse the archive.
Most of what moved this week came down to credentials somebody else was holding on your behalf. Three separate incidents, different vendor categories, the same root cause underneath each one. The other two items are the FTC reminding everyone that privacy copy is a legal statement, and a patch drop large enough to be worth ten minutes of your time.
Attackers used Qubole's trusted AWS access to get into customer accounts
Source: The Hacker News
Wiz reported that an attacker broke into AWS accounts belonging to multiple customers of Qubole, a data lake platform owned by Idera, between October 14 and October 26, stealing stored secrets and data. The attacker used credentials for an AWS account that Qubole's platform uses to reach into those customer accounts. How the attacker obtained those credentials has not been disclosed.
This is the vendor risk that no SOC 2 report in your evidence folder will catch, because the problem is not the vendor's controls, it is the role you handed them inside your own account. I would spend an afternoon enumerating every cross-account role in your AWS organization, checking which ones have external IDs and condition keys, and cutting the permissions down to what the vendor actually calls. Collecting a vendor's audit report and filing it is vendor management theatre when that vendor can assume a role in your production account.
A stolen Fireworks key ended up inside a Cursor extension
Source: The Hacker News
Cursor said the compromise of Anthropic's official Claude Code extension on its extension marketplace traced back to an access key Cursor had issued to Fireworks AI. According to Cursor's update, the key was exposed as a result of the breach at Fireworks, and the attacker used it to copy data from a read-only resource. Fireworks has been at the centre of several disclosures in the past two weeks, including notifications involving Uber driver data.
Developer tooling is now part of your production security story, and most teams cannot produce a list of which AI vendors hold a credential issued by them. If you answer a US security questionnaire by saying no customer data reaches AI services, go verify that against what your engineers have actually installed in their editors before an auditor or a buyer does it for you. Short expiry on issued keys and a real rotation record are the only things that would have limited this.
Malicious workflow spreads across tens of thousands of GitHub repos
Source: Infosecurity
Researchers identified a malicious workflow affecting tens of thousands of GitHub repositories, including repositories owned by Uber. The activity is being described as a supply chain attack on the build pipeline rather than on any single package.
CI is production for a SaaS company of your size, and it is usually the least governed system you own. Pick one repository and try to answer three questions from memory: who can modify a workflow file, what secrets that workflow can read, and whether any third-party action is pinned to a tag instead of a commit hash. If that takes longer than ten minutes, your SDLC answers in the next security review are going to be fiction, and a sharp reviewer will find the gap.
Five more states join the FTC's case over health privacy claims
Source: FTC
The FTC filed an amended complaint adding Arizona, Florida, Nebraska, Ohio and Wisconsin as co-plaintiffs in its lawsuit against telehealth provider Hims and Hers, alongside Utah and California. The complaint alleges the company shared sensitive health information with third-party advertising platforms while telling users its services kept that information private, and that it misled users about billing and cancellation.
Read the allegation structure rather than the industry. A company said something about privacy in its marketing, its tracking stack did something else, and now seven states and a federal regulator are on the filing. Swap health data for transaction data and this is a fintech case. The usual cause is an advertising pixel that a growth team added to pages behind the login, which nobody in engineering reviewed, and which contradicts the privacy page your US buyer's counsel is reading.
Another four-digit Patch Tuesday, with an Outlook zero-day in it
Source: Krebs on Security
Microsoft released fixes for almost 1,100 vulnerabilities across Windows and supported software, including 63 rated critical and a zero-day in Outlook. Adobe, Apple, Google and Mozilla shipped updates in the same window.
I would not read much into the total count, which has been inflating for a while and says more about how Microsoft bundles than about your risk. The Outlook zero-day is the part that matters, since that is a laptop fleet problem and your fleet is where most security reviews find the soft spot. Your policy almost certainly promises a patch window for critical issues, so this is a good week to check whether you can produce evidence that endpoints actually met it.
If you only act on one thing from this issue, make it the inventory of credentials and roles you have handed to outside parties. That list is almost always longer than the people who maintain it think.
Jacob
Free weekly email
Get the next issue on Tuesday
One email a week from Jacob Masse: the security and compliance stories that changed something that week, and what each one means if you sell software to enterprise buyers. Five stories, a take on each, five minutes to read.
Free. Unsubscribe in one click, and replies reach Jacob directly.