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

[FEEDBACK]: Sync attack names between LLMT10 and MLT10 where appropriate #187

Open
1 task done
kapsolas opened this issue Nov 16, 2023 · 2 comments
Open
1 task done
Assignees
Labels
issues/general General issues issues/triage Issues that need further analysis

Comments

@kapsolas
Copy link

Type

Suggestions for Improvement

What would you like to report?

I would like to make the suggestion that we consolidate the terms used in the LLM and ML top 10 documents.

Many of the top 10 items in each are closely related or even the same.
Where possible, the same term should be used (i.e. Model Theft vs Model Stealing, Data Poisoning Attack vs Training data Poisoning).

Thanks!

Code of Conduct

  • I agree to follow this project's Code of Conduct
@kapsolas kapsolas added issues/general General issues issues/triage Issues that need further analysis labels Nov 16, 2023
@shsingh
Copy link
Collaborator

shsingh commented Dec 18, 2023

Hi @kapsolas apologies for the delay in responsing.

Will definitely look to changing "Model Stealing" to "Model Theft".

In terms of "Data Poisoning v Training data poisoning" I would like to defer to @yodap-dg

Typically in research papers it is referred to as "Data Poisoning" and I agree that the use case is largely around the training data itself.

What are your thoughts @yodap-dg?

@yodap-dg
Copy link

Hi @shsingh

Yes, I agree. It should be Data Poisoning is the term, which is widely used.
with regards to Model Theft, LLM10 is defined as Model Theft. @kapsolas

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issues/general General issues issues/triage Issues that need further analysis
Projects
None yet
Development

No branches or pull requests

3 participants