News for hackers. Stuff that matters.
Re:The alarming state of secure coding neglect by CaptSpify on Wednesday May 03, 2017 @11:32AM (#14256561)
And this is why we see companies scooping up people's data and saving it with no regard to the individuals. We need to move to companies seeing that data as a liability, not an asset.
Re:The alarming state of secure coding neglect by iliketosleep on Wednesday May 03, 2017 @12:04PM (#14256970)
It should be both an asset and potential liability. There's no doubt that user info is valuable and can be an asset. But if a company is negligent with that info, perhaps they should be liable in some way.
Re:The alarming state of secure coding neglect by kudokatz on Wednesday May 03, 2017 @11:37AM (#14256634)
> We need to move to companies seeing that data as a liability, not an asset

this could lead to serious limitations on legitimate future progress including on anything built using statistical methods that require large training data sets.

Re:The alarming state of secure coding neglect by nkrisc on Wednesday May 03, 2017 @12:01PM (#14256940)
We choose to limit medical progress by restricting the experimentation that can be done on humans because we've deemed such protections worthy of the cost to progress.

If protecting personal information limits or slows some progress, so be it. Also it could still be done, just more carefully.

Re:The alarming state of secure coding neglect by claytonjy on Wednesday May 03, 2017 @11:44AM (#14256727)
That's certainly a concern given the way things are currently, but I'm hopeful concepts like Google's federated learning [1] will become increasingly popular, and a change to data-as-a-liability would help drive development and adoption of such approaches.

[1] https://research.googleblog.com/2017/04/federated-learning-c...

Re:The alarming state of secure coding neglect by FridgeSeal on Wednesday May 03, 2017 @08:35PM (#14261515)
I really, really like this approach to data, and there's so many advantages beyond the ones outlined there: if you could turn that collection approach into a universal/OS-level API you could have some kind of setup where user data by default stays on the device, then to use it, the app/app server has to request it explicitly (allowing the user easy and powerful, but granular control over who gets what data) and then user data is further protected by the other measures talked about in their paper.

Some level of public education is also required I think, to make people aware of the value/threat of just giving everything up every time someone asks for it.

Re:The alarming state of secure coding neglect by CaptSpify on Wednesday May 03, 2017 @11:40AM (#14256677)
too bad, so sad.

If companies were trustworthy with data, than that wouldn't be an issue. Why should they get a free lunch on my dime?

Re:The alarming state of secure coding neglect by Espressosaurus on Wednesday May 03, 2017 @11:44AM (#14256736)
And nothing of value was lost, except to marketers.
Re:The alarming state of secure coding neglect by mattgreenrocks on Wednesday May 03, 2017 @12:11PM (#14257075)
Yeah, cause they're doing so much with it now /s
Re:The alarming state of secure coding neglect by eeZah7Ux on Wednesday May 03, 2017 @12:48PM (#14257536)
I see very little evidence that personal data is useful for that. Can you name real life examples?

Most machine learning is done against anonymous dataset and works fine.

Re:The alarming state of secure coding neglect by chadgeidel on Wednesday May 03, 2017 @01:32PM (#14258068)
Machine learning can also de-anonymize that anonymous dataset. How does one protect against that? https://en.wikipedia.org/wiki/De-anonymization