about
Data Poisoning Won't Save You from Facial Recognition (arxiv.org)
4 points by belter on Jun 29, 2021 | hide | past | pdf | 1 comment on HN

In plain words: Tools like Fawkes and LowKey add tiny invisible changes to your posted photos so facial recognition mislabels your future pictures. But trainers who adapt or use newer techniques can defeat or spot those altered photos, so the protection fails once photos are scraped.

Abstract · Data Poisoning Won't Save You From Facial Recognition

Data poisoning has been proposed as a compelling defense against facial recognition models trained on Web-scraped pictures. Users can perturb images they post online, so that models will misclassify future (unperturbed) pictures. We demonstrate that this strategy provides a false sense of security, as it ignores an inherent asymmetry between the parties: users' pictures are perturbed once and for all before being published (at which point they are scraped) and must thereafter fool all future models -- including models trained adaptively against the users' past attacks, or models that use technologies discovered after the attack. We evaluate two systems for poisoning attacks against large-scale facial recognition, Fawkes (500'000+ downloads) and LowKey. We demonstrate how an "oblivious" model trainer can simply wait for future developments in computer vision to nullify the protection of pictures collected in the past. We further show that an adversary with black-box access to the attack can (i) train a robust model that resists the perturbations of collected pictures and (ii) detect poisoned pictures uploaded online. We caution that facial recognition poisoning will not admit an "arms race" between attackers and defenders. Once perturbed pictures are scraped, the attack cannot be changed so any future successful defense irrevocably undermines users' privacy.

Evani Radiya-Dixit, Sanghyun Hong, Nicholas Carlini, Florian Tramèr
arXiv:2106.14851 · cs.LG, cs.CR · submitted Jun 28, 2021 · updated Mar 14, 2022
abstract · pdf · html · ICLR 2022

add comment on HN