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]: Include MLOps vulnerabilties somewhere in the Supply Chain Security category #188

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

Comments

@mik0w
Copy link
Collaborator

mik0w commented Nov 17, 2023

Type

Suggestions for Improvement

What would you like to report?

Context
One of the parts of the supply chain in modern ML systems is MLOps software - like i.e. MLFlow, Prefect etc. Those systems are vulnerable to classic web based attacks and they seem to be "misconfured by default". I've described it here: https://hackstery.com/2023/10/13/no-one-is-prefect-is-your-mlops-infrastructure-leaking-secrets/ or here: langflow-ai/langflow#1145

Suggestion for improvement
I'd suggest including MLOps-related vulnerabilities in the ML06 (or maybe in some other categories as well? I am open for suggestions).

Code of Conduct

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

sagarbhure commented Nov 28, 2023

In my view it should be in ML06, However is should be better renamed with ML from AI supply chain i believe to keep ourself distinct, How would you recommend adding these in the existing ML06, keeping the attacks generic to other packages

@shsingh
Copy link
Collaborator

shsingh commented Dec 18, 2023

Hi @mik0w I definitely think we should look at including the ecosystem of MLOps software. I am not sure that it all falls within supply chain though. Keen to hear your thoughts on this.

@shsingh
Copy link
Collaborator

shsingh commented May 1, 2024

Hi @mik0w I agree we should look at renaming this from the current "AI Supply Chain"... the renaming was done as feedback (ref: #85 ) but in the cleanup perhaps we could have chosen something more apt. I think "Machine Learning Supply Chain Attacks" is more apt.

What are your thoughts?

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