4 ms·
I feel like more often than not, organizations apply this logic to SaaSes that offers on-prem installations, and choose the on-prem over the hosted solution...
by BoorishBears 9y ago
I feel like more often than not, organizations apply this logic to SaaSes that offers on-prem installations, and choose the on-prem over the hosted solution...
only to leave the installation out of date with critical vulnerabilities and missing features that the hosted installation would be on top of.
- cortesoft 9y agoThere is nothing stopping an on-prem appliance from being able to automatically update. Of course, once you do that, you are again putting trust back into the third party, so you lose some of what you gained.
- BoorishBears 9y agoI don't think I've ever seen an on-prem application that self updated without manual intervention. I'm sure it exists, but it doesn't seem common. Probably because in general self-updating goes against the control on-prem is supposed to give enterprises, especially when they're afraid of breaking critical workflows.
- hueving 9y agoIf it's not exposed to the internet, an out of date on-prem is still better than everything on a massive centralized public vendor server that 5 nation states are hacked into.
- praneshp 9y agoIf 5 nation states hacked into the centralized public vendor they'll find a way to get into someone's on-prem version of the same, especially if they are the type to let it go very out of date.
- BoorishBears 9y agoGitLab had a permission escalation issue that I saw unpatched on an on-Prem install. Contractors accessing it via VPN (and even local employees) would have been able to access repos and actions they didn’t have permission to access. And it’s not like nation states can’t attack companies directly.
- hueving 9y agoNation states only attack companies they care about. That's the point. Once you have your info on slack, you share the fate with the million other companies that nation states might care about.