3 ms·
> In short: SSO is a core security requirement for any company with more than five employees. Which kinda gives the game away, right? It’s not that SSO is a lu
by Spivak 7y ago
> In short: SSO is a core security requirement for any company with more than five employees.
Which kinda gives the game away, right? It’s not that SSO is a luxury feature but that it’s an IMMEDIATE signal that you’re dealing with an org that can afford to pay.
It’s absolutely a security feature but that doesn’t mean it should be free for any reason other than I don’t want to pay for it. So I wish them the best in bullying the companies into giving me free things. We just dropped $100k on a security product last week so I’m in the market for freeing up room in the budget.
- wmf 7y agoThe complaint isn't that companies are charging money, it's that companies don't include SSO in their base paid tier. We're talking about customers who are already paying money for a service but they're still not getting SSO.
- baddox 7y agoI mean, I was going to point out that that sentence massively compromises the validity of the author's argument, because I've been in companies with more than five employees for which this was definitely not a core security requirement. It's one thing to say that some feature is actually adopted as a security requirement at many companies and that SaaS vendors who don't offer that feature will lose out on those companies as customers. It's another thing to say that SaaS vendors are failing to meet a massive market requirement, and that companies on the other side of that market are also failing to "realize" and adopt that requirement. In other words, unless I saw evidence that a larger portion of 6-person companies demanded this feature, it seems reasonable to assume that the market simply doesn't want this feature, and SaaS vendors aren't doing anything particularly stupid by not offering the feature.
- femiagbabiaka 7y ago> I mean, I was going to point out that that sentence massively compromises the validity of the author's argument, because I've been in companies with more than five employees for which this was definitely not a core security requirement. no, it was a core security requirement whether or not it was accepted as such. but it turns out that saving money wins out over security until you get owned OR you're making enough money to not care.
- baddox 7y agoI think that's a dangerous game with words. The argument boils down to claiming that customers absolutely need a feature but aren't aware of it, and SaaS vendors absolutely need to offer that feature but aren't aware of it.
- femiagbabiaka 7y agothis is the state of corporate security! remember, until about 5-6 years ago 2fa and HTTPS were another couple of examples of things people thought were unnecessary.
- Spivak 7y agoI think the strongest evidence that SSO isn’t a core security requirement is the fact that people aren’t demanding that every site support “login with $social.” SSO is net good for security and is a quick way around a lot of red tape in certain regulatory domains but the value prop has always been, and still is, largely administrative. Having a human manage the accounts of hundreds of people with 10+ logins each services each costs real money compared to adding an account once to AD and dropping them in the group with the rest of their team which is why companies, rightly, feel they can charge a pretty penny for the privilege. Small companies can afford rolling accounts by hand but then you grow and then you have to decide if it’s worth spending the employee hours or the cash.
- danaris 7y ago> I think the strongest evidence that SSO isn’t a core security requirement is the fact that people aren’t demanding that every site support “login with $social.” The very last thing I want from my bank, insurance company, or what have you is for them to be handing over information about every login I make to Google or Facebook.
- tptacek 7y agoThat's self-reinforcing. SSO is an immediate signal that your org can afford to pay because SSO is so expensive, and SSO is expensive in part because the entire ecosystem is expensive enough to make IDP per-seat licenses a smaller fraction of the overall bite. SSO isn't optional; startups of basically all sizes should be using it, almost from the jump. It's not a thing you're supposed to invest in when you finally hit, like, 100 employees or something; it's as important for a 5-person team as a 20-person team. I get the concept of price discrimination and have no on-spec moral qualm with it. But charging extra for SSO is no different than charging extra for MFA; in fact, MFA as a feature is harder to deliver than SAML.
- windowsworkstoo 7y agoSo much this - I'm so glad to see this site as it mirrors an exact complaint I have - with hosted directories becoming so popular, wanting SSO should hopefully slowly stop becoming a signal that you are a big org with lots of money to spend. When my org tries to buy a new SaaS I try to get them to only budget/consider it at the lowest level that gives them SSO - if they can't afford that, then they can't want it enough...it works sometimes...
- statictype 7y ago>startups of basically all sizes should be using it We've routinely deployed our softare to customers who pay us 7 figures. We have literally had to enable SSO only twice in the last 5 years. There's a difference between _should_ and _actually does_.
- tptacek 7y agoI agree. But part of that is because the whole ecosystem of SAAS services charges 2-3x just to enable it.
- statictype 7y agoPerhaps. From our experience SSO is synonymous with “ADFS”. So maybe we’re biased there. It never occurred to me that SSO would be used by smaller orgs so we never bothered putting that into our base pricing.
- beering 7y agoHaving set up a lot of SAML2 SSO integrations, I'm definitely going to put SAML2 in an enterprise tier. My sanity is not worth dealing with SAML2 for customers who are trying to get by with some $100/month subscription plan. In fact, Raygun's policy (according to this list) sounds like something I would do: add support for a couple common ones like Google and Facebook, make all the other SSO setups require an Enterprise plan. * note: I dealt mostly with higher-ed. Don't know if they're more or less competent compared with corporations.
- Spooky23 7y agoIf you have compliance requirements it’s always a cost saver vs vetting and legal work required. If I need to use your SaaS’s identity system, you cannot afford to do business with me, because my company will bury you in red tape and liability.
- harikb 7y agoI think “afford to pay” is different from “let us price gauge so high the customer rethinks whether they really need it”. Charging 3 or 5 times is highway robbery.
- Benjammer 7y ago>that doesn’t mean it should be free for any reason other than I don’t want to pay for it Not the thesis of the article, this is taking down a straw man. The actual article says this: >If companies claim to “take your security seriously”, then SSO should be available as a feature that is either: >1. part of the core product, or >2. an optional paid extra for a reasonable delta, or >3. attached to a price tier, but with a reasonably small gap between the non-SSO tier and SSO tiers. >Many vendors charge 2x, 3x, or 4x the base product pricing for access to SSO, which disincentivizes its use and encourages poor security practices.