Re:Planting Undetectable Backdoors in Machine Learning Models
by galcerte on Tuesday April 19, 2022 @04:29PM
(#31088607)
It sure looks like such models are going to have to undergo the same sort of scrutiny regular software does nowadays. No more closed-off and rationed access to the near-bleeding-edge.
[ Parent
| on HN ]
Re:Planting Undetectable Backdoors in Machine Learning Models
by joe_the_user on Tuesday April 19, 2022 @05:39PM
(#31089620)
Well, this show ML models should receive the scrutiny regular software. But of course regular software often doesn't receive the scrutiny it ought to. And before this, people commented that ML was "the essence of technical debt".
With companies like Atlassian just going down and not coming, one wonders whether the concept of a technical Ponzi Scheme and technical collapse might be the next thing after technical and it seems like the fragile ML would more accelerate than stop such a scenario.
Re:Planting Undetectable Backdoors in Machine Learning Models
by gmfawcett on Tuesday April 19, 2022 @05:44PM
(#31089689)
Wouldn't they deserve far more scrutiny? I know how to review your source code, but how do I review your ML model?
Re:Planting Undetectable Backdoors in Machine Learning Models
by galcerte on Tuesday April 19, 2022 @07:37PM
(#31090810)
By reviewing the source code of the model, reviewing the training data, and reviewing weight initialization, but the latter should be specified in the source code. Also making it abundantly clear that the libraries used to make the model were not tampered with, maybe hashing their files or doing some reproducible builds wizardry...
Edit: Now that I think about it, can't data poisoning happen when predicting, rather than just happening in the training phase? In that case, it's going to be complicated to work around that.