5 ms·
I think the problem with this logic is it hinders a hundred people on a daily basis to prevent one person from doing something stupid once a year. That’s just
by Aeolun 6y ago
I think the problem with this logic is it hinders a hundred people on a daily basis to prevent one person from doing something stupid once a year.
That’s just not great ROI.
- RcouF1uZ4gsC 6y agoNever underestimate the damage one person doing something stupid once can do.
- bryanrasmussen 6y agoI actually think this whole one person doing one stupid thing per year argument is grossly underestimating the amount of stupid available. Stupidity is one of humanity's greatest renewable resources.
- taneq 6y agoIt's a great ROI if that one stupid thing a year is someone pushing your company's codebase and all your trade secrets to a public repo.
- Aeolun 6y agoBy the same logic it’s good to have your company located in an armored bunker underground on the off chance that someone nukes the city you are in. I realize the chances are a bit different, but it illustrates the point.
- notimetorelax 6y agoDepends on the impact of a single erroneous action. I’ve seen cases when folks would push to GitHub passwords (that should be kept in git to start with).
- bryanrasmussen 6y agoright, pushing github passwords leads to GDPR breach in end - anything preventing GDPR breach in the end is probably a great ROI.
- Maxion 6y agoDepends a lot on the company and what it's mission is, not every company needs to be able to move quickly on every front.
- DEADBEEFC0FFEE 6y agoAnyone who has spent a bit of time trying to calculate the lost productivity caused just the meetings needed to discuss breaches (internal, accidental), knows it's great ROI.
- corty 6y agoEveryone greatly overestimates ROI in their own area of expertise and greatly underestimates costs in the rest. You might be right in some special instance, but generally you are not. One example: Sending files via Email is a security problem. So you prohibit this via settings, virus scanners, appliances, etc. Now you've solved the emailed worm problem. However, you've just created a "how do we move files/data/screenshots/..." problem for the whole company. Now everyone will need their own special solution for everything, support will need a screenshot upload tool because you cannot just email them screenshots anymore, marketing won't be able to do images in mails anymore, external people won't have access to internal file shares, etc.
- DrAwdeOccarim 6y agoI appreciate you're giving an example, but this is pretty much solved at most big companies currently with OneDrive (or any other flavor of cloud storage). For external sharing, you just select if the link can be seen external to the org.
- astura 6y agoDoesn't SharePoint trivially solve all this?
- corty 6y agoFor external people likely not, usually Sharepoint would be behind some VPN and Firewall. Some cloud service like Dropbox might work if allowed (which it often isn't). And then there will often be the resulting sprawl of various services: this for secret internal stuff, that for external people, yet another thing for marketing, etc.
- 6y ago
- serioussecurity 6y agoI've seen individual engineers make a mistake that caused 100 engineer's salary worth of damage.
- alexchamberlain 6y agoI suspect we all have. The question is rather: how much would it have cost to prevent that mistake? The flip side is the insurance argument: given a big enough organisation, a mistake like that will happen, even if the probability of each individual mistake is very low. So assuming one of these will happen, what can you do to reduce the impact or to reduce the latency of fixing such a mistake?
- gjvc 6y agoI would love to know more about the details of this example :-)
- gwd 6y agoSo the company I work for made the front page of HN last year for a security breach. I won't go into details, but I will say one factor was a particular instance where security was overlooked for many years due to convenience. In response, the company has now sort of swung the other way: lots of things that have a perfectly valid reason and are reasonably safe have been forbidden or suddenly have needed to be justified in the face of extreme skepticism. That wasn't a case of a single engineer causing 100x engineers worth of damage, but it was the case where something made hundreds of people's jobs a tiny bit easier for two decades, then caused a massive public loss of face and who knows how much reputational damage. And I'd be willing to bet that a fair number of HN readers work at a company which has at least one system with similar properties (a bit more convenient, a bit less secure) to the one implicated in our security breach; but failure is a once-a-decade event, and their company isn't nearly that old yet. Would those engineers defend that setup using the argument from this article?
- dtech 6y agoWas it the Twitter internal account management tool?