Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analyses of defenses #6

Open
anishathalye opened this issue Jul 22, 2018 · 1 comment
Open

Analyses of defenses #6

anishathalye opened this issue Jul 22, 2018 · 1 comment

Comments

@anishathalye
Copy link

ML security, or any security field in general, is going to have cases where papers make a certain claim, and later, that claim ends up being invalidated. For example, we once thought MD4 was a secure hash function, but now it's known to be broken. This is a natural thing to happen in a security field: future analysis showing that a certain scheme is not secure.

For this reason, it might be a good idea for a resource that lists defenses against adversarial examples to also keep up-to-date with future analyses of those defenses, so that readers looking at this list do not mistakenly believe that a broken scheme is secure.

The list currently has a number of defenses that are known to have true robustness significantly below what is claimed in the paper (in most cases, the true accuracy is 0%). This includes:

Do you think the list could be organized so that it's clear to readers that while defense papers are interesting, for certain papers, later analyses have shown that the schemes can be circumvented? (robust-ml.org is one example of such an organization)

@yenchenlin
Copy link
Owner

yenchenlin commented Jul 22, 2018

Good idea! I will start to add up-to-date future analyses to the list two weeks later (after I finish my mandatory military service).

Also, as the number of papers related to adversarial examples has exploded over the past two years, I am thinking about writing an annotated bibliographies (also served as a suggested reading list) here for people new to the field to track the status.

Feel free to share your thoughts here! Will keep this issue open until the up-to-date analyses are added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants