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

docs: add dyana mitigation tool to relevant entries #531

Merged
merged 1 commit into from
Jan 14, 2025

Conversation

GangGreenTemperTatum
Copy link
Collaborator

@GangGreenTemperTatum GangGreenTemperTatum commented Jan 14, 2025

PR Checklist 🚨

It is intended that only defined "vulnerability entry leads" should be able to create PR's (See CODEOWNERS and Core Team)

If you are not a CODEOWNER for the entry of artifact, please see our Issues and Discussions boards

Proposed changes

Dyana provides a safe, easily adoptable and approachable methodology for any developers or engineers to verify numerous elements of their supply-chain from multiple model formats, programming language dependencies and even down to executable files.

I strongly believe this tool is a great open-source contribution that can be adopted by the OWASP foundation in general due to its multi-faceted use-cases and lightweight, flexible approach and serves multiple use-cases - including, but not limited to:

  • OWASP Top 10 for LLM Applications project, including the OWASP LLM and GenAI Security Landscape
  • OWASP Application Security Verification Standard (ASVS)
  • OWASP OWASP LLM Security Verification Standard (LLMSVS)
  • CycloneDX - @OWASP CycloneDX SBOM/xBOM Standard

Types of changes

Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have x-referenced the appropriate issue this addresses within the projects board
  • I have applied the relevant labels this PR addresses

Further comments

CC @jsotiro for vis (of LLM03)
Related links:

https://pypi.org/project/dyana/0.0.2/
https://www.linkedin.com/posts/dreadnode_meet-dyana-a-new-open-source-tool-from-dreadnode-activity-7284984127064260608-aLS-?utm_source=share&utm_medium=member_desktop
CycloneDX/tool-center#3

@GangGreenTemperTatum GangGreenTemperTatum added llm-03 Relates to LLM Top-10 entry #3 llm-04 Relates to LLM Top-10 entry #4 labels Jan 14, 2025
Copy link

👋 Thanks for your pull request! Please ensure appropriate labels are applied for review routing.

@GangGreenTemperTatum GangGreenTemperTatum merged commit 5f5e40c into main Jan 14, 2025
8 checks passed
@GangGreenTemperTatum GangGreenTemperTatum deleted the ads/add-dyana-mitigation-tool branch January 14, 2025 17:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
llm-03 Relates to LLM Top-10 entry #3 llm-04 Relates to LLM Top-10 entry #4
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant