The Compliance Brief for SOC 2 buyers
Every Tuesday, the stories from the past week that change something for a company buying or holding a SOC 2 report, with a plain take on each.
Most of what reaches a SOC 2 buyer's inbox is vendor marketing. The Compliance Brief is the other thing: what happened that week to companies like yours and to the vendors in your own report, and what a customer's security reviewer is going to ask about it next.
Below are the stories from recent issues that bear on SOC 2: vendor and subprocessor breaches, what auditors are looking at, and the contract terms customers are starting to write. Each one links to the full take.
Free weekly email
Get the next issue on Tuesday
Join the list and the next issue arrives Tuesday morning. Or read a few below first.
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.
Latest on SOC 2 audits, auditors and vendor reviews
- Attackers used Qubole's trusted AWS access to get into customer accounts
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. - A stolen Fireworks key ended up inside a Cursor extension
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. - AI governance budgets are up and nobody feels more in control
DNSFilter's shadow AI report found 74.5% of respondents had a larger security budget than a year earlier, with 40.3% naming AI security and governance as the destination for the next incremental dollar and 25.5% naming cloud security. - Seven in ten breach victims were exposed through somebody else's supplier
Kroll's Data Breach Outlook 2026 reports that nearly seven in ten people affected by breaches it handled were exposed through an outside supplier rather than the company they dealt with directly. - Navigate360 shows how a bad breach response loses the contracts
Multiple Ontario Crime Stoppers organizations have suspended their use of Navigate360's tip management platform following its data breach and what the reporting describes as an unacceptable incident response. - Everyone knows the security questionnaire is theatre
SecurityWeek argues that the process gating nearly every B2B deal is a self-assessment that the sender does not trust and the receiver accepts anyway. - Most breach victims last year were breached through someone else
Kroll found that 69 percent of data breach victims over the past year were affected through a third-party breach. - Unauthenticated RCE in PHP, exploited already
Two critical PHP vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619 and nicknamed php2shell, allow an unauthenticated attacker to take full control of an affected server.
Every issue on GetSOC2
- Issue 15: Attackers used Qubole's trusted AWS access to get into customer accounts
- Issue 14: AI governance budgets are up and nobody feels more in control
- Issue 13: Seven in ten breach victims were exposed through somebody else's supplier
- Issue 12: Most breach victims last year were breached through someone else
- Issue 11: Regulators are naming the service provider, not only the customer
- Issue 10: ASOS breach started with a connected marketing platform
- Issue 9: Frontline Education breached through someone else's software
- Issue 8: Your AI agents are logging in as humans and SOC 2 cannot tell
- Issue 7: Revolut handed over customer data to someone pretending to be a government
- Issue 6: Trezor's supplier breach keeps growing, and it was never Trezor's system
- Issue 5: McKesson tells the SEC it was hit through third-party applications
- Issue 4: McKesson breach came through third-party applications
- Issue 3: Defence contractors do not believe their own CMMC scores
- Issue 2: A year-long campaign is quietly draining Salesforce and ServiceNow tenants
- Issue 1: LexisNexis pulled products offline over a third-party vendor incident
Every issue in full, including the stories outside SOC 2 audits, auditors and vendor reviews, is in the archive on traztech.ca. Issues with nothing on SOC 2 audits, auditors and vendor reviews are listed there and not here.
Questions
How often does The Compliance Brief arrive?
Once a week, on Tuesday morning. Each issue covers the past week in five stories or so, with what happened and a short take on what it means for companies buying a SOC 2 audit.
What does it cost?
Nothing. It is written by Jacob Masse, Principal at TrazTech Inc., which operates GetSOC2. There is no paid tier.
Will signing up here send me anything else?
No. The form on this page adds you to The Compliance Brief and nothing else. Downloading a checklist elsewhere on the site is a separate signup, and it says what it sends before you give an address.
How do I stop it?
Every issue ends with a one-click unsubscribe link, and it is honoured immediately. Replying to any issue also reaches Jacob directly.
Free weekly email
Get it every Tuesday
One email a week on SOC 2 audits, auditors and vendor reviews. Free, and one click to leave.
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.