3 ms·
It's a technology problem, not a people problem. We have simply made technology where it is too easy to eventually make a simple mistake. For one obvious, simp
by hn_throwaway_99 3y ago
It's a technology problem, not a people problem. We have simply made technology where it is too easy to eventually make a simple mistake.
For one obvious, simple example, most tech is optimized for "Make it easy to access all data from anywhere" as opposed to "require affirmative consent for connections to all new locations". It is surprisingly difficult to lockdown most systems, whether they be laptops or server networks, with that easy rule. Just look at folks who use Little Snitch - it can be difficult to use this effectively because so many apps need to talk to so many different servers that it can just be exhausting attempting to determine if a new connection is malicious or not.
Similarly, look at some recommended settings for a "secure" Content Security Policy on the web. There are a boatload of different options that are recommended to be set, because the original defaults (e.g. "Sure, you can load me in an iframe of any other site!") are so insecure.
As a consequence of this, it's very difficult for any (a) organization that can't afford top-notch security folks or (b) organizations that are so large, with a potentially huge history of acquisitions over time, with a giant surface area where all you need is one "chink in the armor", to prevent breaches.
- SloopJon 3y agoThis is every bit as much a people problem as a technology problem. When I read the headline, I didn't even understand what there possibly was to breach at OWASP. > OWASP collected resumes as part of the early membership process, whereby members were required in the 2006 to 2014 era to show a connection to the OWASP community. OWASP no longer collects resumes as part of the membership process. Why did OWASP retain this information ten years after they stopped the practice?
- Eisenstein 3y agoProbably because no one made the decision to delete it, and the person responsible for the system that it was on wasn't going to delete data without a strict order to do it. I think it is more of an 'organizational' problem, in that organizations don't have data retention and deletion policies.