2 ms·

Being charitable, I think the more likely explanation is that CTOs/CFOs do not understand how easily these things can happen, and how much data can be exposed b

Being charitable, I think the more likely explanation is that CTOs/CFOs do not understand how easily these things can happen, and how much data can be exposed by a "small" mistake. One line of code can expose 30,000,000 records. That's hard to get your head around if you are not a programmer.

icantdrive55 9y ago
It's not that hard. You don't need to be a Programmer to understand security. They just don't care because consumers don't seem to care with their information. I wish technical people made it to CEO/CFO. They're supposedly bad with business, and people? I've bever understood the process of hiring the head honchos. My college sweetheart is a big wig in the valley. Besides being WASPy, and having a spotless resume; I wouldn't trust her to feed my dog. I look back on her cheating her way through college, and the Star Trek ensamble she proudly sports now--and just don't get it. But---these are the one's in charge?
__s 9y ago
We get around this by limiting our databases to only 1000000 records per codebase. Then we duplicate the codebase 30 times (with tweaks) for 30000000 records.. but at least in the retrospective we'll say there was 30 lines of code at fault, not just 1
jumelles 9y ago
A few years ago, sure - but now, after countless breaches? Cyber attacks are regularly in the news these days.
djsumdog 9y ago
From the description, this wasn't one line of code, this was a major design oversight. Either nobody is security conscious on the dev team handling their mobile/web services, or it's just one guy with no code review on major components, or people who complained were tuned out, ignored, placed in low priority, or some other totally irresponsible managerial action. You have to have a lot of bad process in place for something like this to get in.

2 ms·

Being charitable, I think the more likely explanation is that CTOs/CFOs do not understand how easily these things can happen, and how much data can be exposed b

by ams6110 9y ago

icantdrive55 9y ago
It's not that hard. You don't need to be a Programmer to understand security. They just don't care because consumers don't seem to care with their information. I wish technical people made it to CEO/CFO. They're supposedly bad with business, and people? I've bever understood the process of hiring the head honchos. My college sweetheart is a big wig in the valley. Besides being WASPy, and having a spotless resume; I wouldn't trust her to feed my dog. I look back on her cheating her way through college, and the Star Trek ensamble she proudly sports now--and just don't get it. But---these are the one's in charge?
__s 9y ago
We get around this by limiting our databases to only 1000000 records per codebase. Then we duplicate the codebase 30 times (with tweaks) for 30000000 records.. but at least in the retrospective we'll say there was 30 lines of code at fault, not just 1
jumelles 9y ago
A few years ago, sure - but now, after countless breaches? Cyber attacks are regularly in the news these days.
djsumdog 9y ago
From the description, this wasn't one line of code, this was a major design oversight. Either nobody is security conscious on the dev team handling their mobile/web services, or it's just one guy with no code review on major components, or people who complained were tuned out, ignored, placed in low priority, or some other totally irresponsible managerial action. You have to have a lot of bad process in place for something like this to get in.