WARDEN: Multi-Directional Backdoor Watermarks for Embedding-as-a-Service Copyright Protection

Anudeex Shetty, Yue Teng, Ke He, Qiongkai Xu
3/3/2024
cs.CRcs.CLcs.LG

No official code found. Best implementation: anudeex/WARDEN (9 stars, last commit 2024-08-26).

Abstract

Embedding as a Service (EaaS) has become a widely adopted solution, which offers feature extraction capabilities for addressing various downstream tasks in Natural Language Processing (NLP). Prior studies have shown that EaaS can be prone to model extraction attacks; nevertheless, this concern could be mitigated by adding backdoor watermarks to the text embeddings and subsequently verifying the attack models post-publication. Through the analysis of the recent watermarking strategy for EaaS, EmbMarker, we design a novel CSE (Clustering, Selection, Elimination) attack that removes the backdoor watermark while maintaining the high utility of embeddings, indicating that the previous watermarking approach can be breached. In response to this new threat, we propose a new protocol to make the removal of watermarks more challenging by incorporating multiple possible watermark directions. Our defense approach, WARDEN, notably increases the stealthiness of watermarks and has been empirically shown to be effective against CSE attack.

View on arXivView PDF

Code Implementations(1)

anudeex/WARDENCommunity100%

Code of our paper - "WARDEN: Multi-Directional Backdoor Watermarks for Embedding-as-a-Service Copyright Protection" (Accepted to ACL2024 (Main Proceedings)).

90Shell, PythonFeb 25, 20242 years ago

Similar Papers

Cite this paper

@article{shetty2024warden,
  title  = {WARDEN: Multi-Directional Backdoor Watermarks for Embedding-as-a-Service Copyright Protection},
  author = {Anudeex Shetty and Yue Teng and Ke He and Qiongkai Xu},
  year   = {2024},
  eprint = {2403.01472},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2403.01472v2}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2403.01472.svg)](https://codeofpaper.com/paper/2403.01472)

Discussion