3 ms·
The challenge being, who else could possibly handle Cloudflare's requirements? I imagine the next step is to build their own, and that's obviously not an easy p
by Icathian 3y ago
The challenge being, who else could possibly handle Cloudflare's requirements? I imagine the next step is to build their own, and that's obviously not an easy pill to swallow.
- amluto 3y agoWhy not? Cloudflare already operates a system that can help customers to require SSO for access to their services — why not try to capture more of that vertical by becoming an IdP?
- whalesalad 3y agoThey already run their own zero trust infrastructure for customers, kinda surprised they are not dogfooding it. https://www.cloudflare.com/plans/zero-trust-services/ https://www.cloudflare.com/plans/zero-trust-services/
- mikey_p 3y agoDid you read the article? They are using zero trust and explained that it's why the scope of the security incident was extremely limited.
- jgrahamc 3y agoWe use our Zero Trust stuff extensively. In fact, we built it for ourselves initially.
- tomschlick 3y agoThey are, but they don't have management for user accounts, 2fa, etc. You setup a connection to something like Okta, Google Apps, O365, SAML, etc to be your persistent user db and cloudflare just enforces it. I wouldn't be surprised if they are working on first party IAM user support though.
- margalabargala 3y agoThere are good reasons not to dogfood critical services like that; it can make recovering from unexpected issues much harder if you introduce mutual dependencies. For example, if Slack devops team were to exclusively communicate over Slack, then a Slack outage would be much harder to resolve because the team trying to fix it would be unable to communicate.