
Ominously, 31 minutes before Cloudflare acknowledged the problems with its global network, it had also reported problems with its support portal.
“Our support portal provider is currently experiencing issues, and as such customers might encounter errors viewing or responding to support cases. Responses on customer inquiries are not affected, and customers can still reach us via live chat (Business and Enterprise) through the Cloudflare Dashboard, or via the emergency telephone line (Enterprise). We are working alongside our 3rd party provider to understand the full impact and mitigate this problem,” it reported at 11.17 a.m. UTC.
While there’s no evidence to suggest that Cloudflare’s support portal problems were linked to the subsequent content delivery service outage, support portals have proven a weak link in several attacks on IT vendors in recent months. Discord saw customer data leaked after a breach at a third-party customer service provider. Salesforce has denied responsibility for security problems that saw a number of its customers compromised — and in several instances the finger is pointing to Salesloft Drift, a third-party AI chat tool service often integrated with it.
And in September Verizon reported that 71% of CISOs had been hit by a third-party security incident in the past year. Third-party risk management has become a key concern for enterprises, according to IDC.
It’s barely a month since another third-party service used by many IT departments caused widespread disruption: On October 20, a glitch in Amazon Web Services’ DynamoDB service triggered cascading outages in other AWS services and for the company’s customers.





















