TrustCenter

Regulators are naming the service provider, not only the customer

October 20, 2026. From issue 11 of The Compliance Brief, 3 stories for Canadian companies answering customer security reviews.

Last reviewed 2026-10-20Written by Jacob Masse, TrazTech Inc.

Issue 11 of The Compliance Brief was published on October 20, 2026. 3 of its 5 stories bear on security reviews, vendor diligence and trust, and they are below in short form. The full issue, with every take in full, is on traztech.ca.

Source: DataBreaches.net

The New York and Connecticut attorneys general secured $2.7 million from Boston Children's Health Physicians and its IT company, XTIUM, over a 2024 data breach. Both the provider and the technology firm were held liable.

Our take, in short

I have been telling clients for two years that the vendor gets pulled in eventually, and here it is in black and white from two state AGs at once. If you process or host data for US customers, your exposure is no longer limited to whatever indemnity cap you negotiated, because a regulator is not a party to your MSA.

Read the full take on traztech.ca

ConnectWise breach shows how app identities get you into someone else's tenant

Source: BleepingComputer

ConnectWise shut off customer access to its Cloud Backup service, formerly SkyKick Cloud Backup, after attackers reached application identities and used them to compromise Microsoft 365 tenants. The service held the standing access needed to do its job, and that access became the attack path.

Our take, in short

Every SaaS product that asks a customer for an OAuth app registration is holding the same kind of key, and most teams I work with have never inventoried what their own app actually requests. Go look at the consented permissions in your Azure tenant this week, both the ones you granted to vendors and the ones your customers granted to...

Read the full take on traztech.ca

OpenCode breach is a lesson in holding other people's API keys

Source: The Hacker News

OpenCode said an intruder reached a legacy system on the night of October 16 and may have exposed third-party AI provider keys that users had saved in OpenCode Console. Console is the optional hosted service where a workspace stores its own OpenAI, Anthropic or Google key so the platform can call the model provider on the team's behalf.

Our take, in short

Two things here. Storing a customer's credential for another service is custody, and it deserves the same controls you would put around their production data, which in practice means envelope encryption, narrow scoping and a rotation path you can trigger in an afternoon.

Read the full take on traztech.ca

Also in issue 11

Outside security reviews, vendor diligence and trust, but in the same email:

Older: issue 10 All issues on TrustCenter Newer: issue 12