deepakprab

Tracking and mapping where your sensitive data goes is challenging and manual approaches always fall short. This is a very unique unique approach to preventing sensitive data leakage.

We (BoxyHQ) are an SSO and Directory Sync vendor like WorkOS and they are spot on with the details of the SAML vulnerabilities. We have guarded against these attacks so our customers don't have to but plenty of companies still roll out their own implementations, not all of them securely.

It's just riddled with vulnerabilities but most of them are now well known and mitigated.

OpenID was meant to be the successor but popularity wise SAML is still the champion with enterprises.

SCIM doesn't really have a successor afaik. Azure AD I think doesn't do password sync, I am not sure who twisted Okta's hands to get this implemented.

Great suggestion, SAML SSO should really become commodity and made available to all tiers. Enterprise tiers are clearly dictated RFP/Security Questionnaires, there's no bigger admin hassle than that.

Indeed, one common interface for the sync that captures all the nuances of multiple identity providers implementing the SCIM protocol. Thanks IvoSolveoYCSS19.

I'd love to join the conversation. My email is deepak at boxyhq.com

I agree, something like 80 SaaS apps on average per enterprise apparently. I like to call it Death by SaaS! ;)

Which bits specifically? :)

You have to look at it from the perspective of the Enterprise and you'll see that everything you list as risks is exactly what helps them mitigate their other critical risks: - Lets them centralise access, provisioning and de-provisioning becomes simpler

- It lets them tick a bunch of compliance related checkboxes

- The stats on average number of SaaS apps used in enterprises is something like 80 apparently, you can imagine the insanity of managing access to all these

- The single point of failure is never usually a big concern compared to the centralised access they get on the back of SSO