3 ms·
Dos and Don'ts of Machine Learning in Computer Security [pdf]
- drabadur 4y agoIs this a new trend or why is there no publishing date anywhere to be found in this paper?!
- kaiviti 4y agohttps://www.researchgate.net/publication/344757244_Dos_and_Don'ts_of_Machine_Learning_in_Computer_Security https://www.researchgate.net/publication/344757244_Dos_and_D...
- Aethylia 4y agoI feel like once I noticed usenix is an anagram of unisex, I can't stop reading it that way.
- MattPalmer1086 4y agoInteresting. As a non expert in machine learning, I would have assumed that most of those issues apply to any use of it. I'm not particularly seeing why security suffers here, other than the difficulty of getting good training sets. Good to see an analysis that shows these problems are there though and how to address them.
- MattPalmer1086 4y agoI guess one hypothesis is that security companies are just doing a really bad job of it in the rush to get products out of the door with the magic "machine learning" tickbox on it. That would not surprise me...
- sigmoid10 4y agoI work in ML research and you're correct that none of this is new or surprising. All pitfalls are common knowledge in the field and not specific to security. But the security industry is still lagging behind here and the paper does give some nice examples for how these pitfalls can easily be stumbled into if you are not careful during the creation of datasets, training and evaluation. Curiously though, their Android App risk example lists the origin of the app under spurious correlations, whereas in practice any careful human would also immediately rank an app from a random chinese store as a greater risk than one from the google play store. This is part of the problem: There is a large gap between academically worthwile discussions and the stuff that works in the real world.