5 ms·
95% of companies on the planet do not have the necessary resources or expertise to run a robust authentication infrastructure, and this one hack (which we reall
by paxys 5y ago
95% of companies on the planet do not have the necessary resources or expertise to run a robust authentication infrastructure, and this one hack (which we really know nothing about at this point) doesn't change that fact.
If you are in the 5%, great! You are probably set already.
If you are not, overreacting isn't going to help anyone. There's no need to start writing user login code tonight.
- 9dev 5y ago> If you are not, overreacting isn't going to help anyone. There's no need to start writing user login code tonight. I agree. That being said, there's no need to write login code yourself. Trust on the existing, tested, proven OSS solutions and libraries available, if you decide to not rely on a provider like Okta.
- hutzlibu 5y ago"Trust on the existing, tested, proven OSS solutions and libraries available, if you decide to not rely on a provider like Okta. " Can you recommend some?
- 9dev 5y agoYes. Keycloak, for one: https://www.keycloak.org https://www.keycloak.org I've also heard good things about Hydra: https://www.ory.sh/hydra/ https://www.ory.sh/hydra/ Depending on your needs, an SSO proxy like Vouch works well for internal services: https://github.com/vouch/vouch-proxy https://github.com/vouch/vouch-proxy There's also an abundance of libraries for different programming languages to implement authentication or authorisation, lots of them battle-tested by thousands of services. It's not like providing secure services is impossible without Okta.
- ddaalluu2 5y agoYes but I'm having trouble with the client side. Especially Cordova or Capacitor. In a hybrid app with keycloak in the back it's just not working. I tried the cordova-native keycloak adapter but it's just not working. Pure Vue or Angular no issues. Flutter issues because AppAuth is not very well documented and it's even worse for Android Java or Kotlin. Security or auth should be treated as the president of the 1st class citizens, instead it's a mess. On the backend everything is fine, but frontend is in a really bad state.
- paranoidrobot 5y ago> There's no need to start writing user login code tonight. I think it's worth pointing out that replacing Okta for most people isn't just doing login +MFA stuff. Sure, there's that part of it - but a lot of the value in going with Okta in particular is that so many third parties support integrating with them in ways that other Identity providers are just not supported. Account lifecycle stuff (via SCIM) is often limited to just Okta support for products. There's also the account lifecycle stuff so that HR doesn't have to tell you when they hire someone, they just add them into the HR system and all the things flow out from that. Similarly when someone leaves, you can have those workflows go and disable/delete their accounts.
- Nextgrid 5y agoBut Okta is just hosted SAML or OIDC. The same can be achieved with self-hosted Keycloak. In fact, a third-party’s “Okta integration” should work out of the box with Keycloak or any other IdP.
- jiveturkey 5y agoIt's not just that. The most important part of Okta is the directory integration, not the SSO part. For small companies that have never acquired anyone, it doesn't matter. It also makes user lifecycle someone else's problem. Very important. As a medium and larger sized company, when you have to tell your customers your homegrown IAM was pwned, you're in for a world of hurt. When you're just in the boat with everyone else who got popped, it's an easily recoverable incident.
- ownagefool 5y agoIf you have any sort of footprint, it's pretty much expected you'd have protective monitoring so you can articulate what these pwned accounts have actually achieved on your infrastructure. It doesn't really matter who runs your auth service, if the auth service getting pwned results in a reportable attack, you're in for a world of hurt. The next step is to articulate why this isn't your fault and that you did everything you reasonbly could have done to not get pwned. Do you have evidence to support you did your due dilligance on your provider?
- Nextgrid 5y agoIt still raises the bar for the attacker. Now they explicitly need to seek out and target the company. Even if breaking into any single company might now be easier, breaking into all of them is much more difficult than if they used a single point of failure like Okta.
- int0x2e 5y agoWhile it feels that way, in my experience, it is very easy to break into 10 poorly secured systems compared to just 1 properly secured and monitored one. Okta may have messed up here, and there's no doubt they're a large target, but they're still a much harder target to breach compared to anything 99% of companies will be able to set up (unless you're a Fortune 50 company perhaps, and even then - it may not be cost effective even if you can make it work). Expect to have 50+ engineers and other technical staff to be anywhere nearly as secure with a custom solution. A roll-your-own solution with a small crew supporting it can never compete.
- Nextgrid 5y agoThe amount of effort they invested into breaching Okta is probably way more they'd invest in breaching any single company's SSO. If "LAPSUS$" is after big companies with significant IP they can hold ransom for millions of dollars, it's most likely not even worth their time to find let alone attack your small company's on-prem SSO even if it was a single shell command away, so you'd still be more secure.
- paskozdilar 5y ago> 95% of companies on the planet do not have the necessary resources or expertise to run a robust authentication infrastructure Wait, what exactly makes this problem so fundamentally hard? What stops someone from just releasing a software system that solves the authentication infrastructure problem in a general way (e.g. as Kubernetes did for cloud orchestration)?
- TremendousJudge 5y agosame problem as centralization, it's a very attractive target for attacks, and if it's broken, you are compromised too
- paskozdilar 5y agoI don't understand the centralization argument. If anything, software solutions should make systems less centralized, since anyone will be able to run their own auth infrastructure on their own hardware. If you mean that a single codebase could be an attractive target for attacks, it's still not a problem since the Free Software community loves having a dozen of competing implementations of the same thing just for the sake of it :)
- TremendousJudge 5y agoSorry, I don't mean that the actual system is centralized, as in everybody pings back to the same server or organization, but that it shares a similar vulnerability with having the same codebase running in local hardware. And this isn't even solved by having standard protocols, open source implementations as you mentioned -- only mitigated. OpenSSL was exploited too.
- gbloeb 5y agoEconomic incentives and strongly held technical opinions like those of paxys occupying staff+ positions at every participant in modern computing. We’ve deluded ourselves as an industry into believing that computers are too hard to build operate for anyone but Marvel’s Avengers of the Bay Area. That lie underpins the entire market capitalization of public cloud and it’s amazing how little clothing that lie actually wears in the end. Kubernetes doesn’t go after it, either; it complicates your system so exponentially that it drives the same lie. All Kubernetes does is assign a workload to a machine and hook crap up to it. That problem was solved in the 1960s by systems that don’t take multiple FTEs just to operate itself. When you look at Kubernetes in this light there’s a moment of clarity waiting regarding why it exists in the first place, and why it will never in a millennium replace Borg. In 2010, I joined a social media startup. I was the only operations employee on the team of nine who had ever touched an actual server with my hands. We’re on the third or fourth generation of systems people now who’ve never heard anything except the cloud-native drum and how they’ll never be qualified to run their fingers along the faceplate of the computers running their business. paxys is sharing a derivative of that because it is a strongly held industry belief and a safe language to speak in this market. It just doesn’t make it true, and that’s a powerful realization, but that’s not something most people are ready to hear and truly understand. You’re asking the absolutely right questions. You’re just asking an industry that gave up on itself so long ago that kids born after UTAH2000 can vote now.
- menomatter 5y agowhat about having an extra in house level of security? Something that does not require the overhead and maintenance of Identity Management System? Not sure what that would look like though.