feat: add new ave rule records - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type of Change
Description
AVE Record(s)
Checklist
For AVE record submissions
records/AVE-PENDING.jsonbehavioral_fingerprintis clear and actionabledetection_methodologyis specific and reproducibleindicators_of_compromisehas at least 2 entriesowasp_mappingreferences valid ASI identifiers (ASI01–ASI10)cvss_ai_scoreis justified in the PR descriptionresearcherfield contains my correct name and attributionFor schema changes
schema-changelabelSPEC.mdupdatedrecords/TEMPLATE.jsonupdatedFor all PRs