Attackers used Qubole's trusted AWS access to get into customer accounts
November 17, 2026. From issue 15 of The Compliance Brief, 2 stories for companies buying a SOC 2 audit.
Issue 15 of The Compliance Brief went to subscribers on November 17, 2026. 2 of its 5 stories bear on SOC 2 audits, auditors and vendor reviews, and they are below in short form. The full issue, with every take in full, is on traztech.ca.
Free weekly email
Get the next issue on Tuesday
One email a week: what changed in security and compliance, and what it means for companies buying a SOC 2 audit.
Free. One email every Tuesday from Jacob Masse, and nothing else: signing up here does not add you to any other sequence. One click unsubscribes.
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.
Our take, in short
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...
Read the full take on traztech.ca
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.
Our take, in short
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...
Read the full take on traztech.ca
Related on GetSOC2
- Complementary user entity controls (CUECs)
- Responding to a SOC 2 RFP
- SOC 2 auditor asking for too much evidence?
- The SOC 2 common criteria, CC1 to CC9
Also in issue 15
Outside SOC 2 audits, auditors and vendor reviews, but in the same email:
- Malicious workflow spreads across tens of thousands of GitHub repos
- Five more states join the FTC's case over health privacy claims
- Another four-digit Patch Tuesday, with an Outlook zero-day in it
Older: issue 14 All issues on GetSOC2
Free weekly email
Get it every Tuesday
The next issue goes out Tuesday morning. Read it in your inbox instead of finding it here a week later.
Free. One email every Tuesday from Jacob Masse, and nothing else: signing up here does not add you to any other sequence. One click unsubscribes.