Summary
The paper asks the question if the audio deepfake (or deepfake speech) detection is reliable? To answer this question, it evaluates four deepfake detectors and uses different attack types specific to the nature of access to the model under evaluation. The paper draws insights from their experiments revealing that infact audio deepfake detectors are vulnerable and even simple attacks deteriorate their performance, making them highly unreliable. The analyses discussed in the work underscore the poor quality of current deepfake detectors.
Strengths
- The problem of unreliable deepfake detectors is of primary concern to users, such as fact-checkers and investigators, who want to rely on their performance out-of-the-box. The paper hits at the core problem with deepfake detectors.
- The paper is overall clear to read and provides several results to ground their insights on.
- The presenting of takeaways and key findings makes the paper accessible for readers.
Weaknesses
As this paper asks an evaluation question, **it needs to back it with substantive evaluations**. I suggest the following improvements:
- The complete evaluation is performed on 100 samples from 3 text-to-speech (TTS) datasets. Essentially basing all analysis on 300 samples. There are newer speech-to-speech datasets, such as DECRO [1]. Moreover, audio deepfake datasets are easy to create. If we have 100 speakers then we can create 100 * 99 (9,900) by inferring a speech generator, such as FREEVC, QuickVC, Suno-AI's Bark, TorToiSE, CoquiTTS. Subsequent filtering to retain high quality sample should be explored.
- If the datasets were in any form skewed, randomly sampling from them would carry forward those biases. A demographically and phonetically-diverse set of samples would give representation to practical edge cases.
- While white-box access to commercial deepfake detectors is harder to obtain, include them into black-box and model agnostic evals. Examples are resemble.ai, elevenlabs.io. In such case SimBA might not work, as confidence score is generally not given.
**A general lack of discussion**:The paper lists its insights but fails to make readers confident to believe what they are reading. For example, In 3.3, "ASSIST-L, being smaller, may form smoother decision boundaries, leading to better generalization and robustness against perturbations." First, the language is hand-wavy as no evidence is given, and second, this insight itself is surprising.
[1] Transferring Audio Deepfake Detection Capability across Languages, WWW'23. https://github.com/petrichorwq/DECRO-dataset
Questions
**Addition of the following information would help bolster reader confidence:**
- Description of how the human ratings were computed. Did you use a standard like P.808 for obtaining Mean Opinion Scores (MOS)? if not, why? Who were the raters?
- Description of the measure of the dataset being evaluated? Did the deepfake samples selected for evaluation fool humans? What was the baseline?
- Can authors defend their views in conclusion about Security by obscurity: "This underscores the critical need to restrict public access to SSD models and internal workings." What do the authors mean? Should the community not publish their works? How will anybody audit such systems then?
- Expand discussion of above discussed concepts by moving some of the plots to appendix.
**Stretch goal:**
- While limiting to a language is an understandable constraint, evaluating multi-lingual deepfakes might lead to novel insights.