Add DAST API route coverage evidence gates#1709
Open
yanziwei wants to merge 1 commit into
Open
Conversation
4 tasks
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.
Skill Improvement ($50-150 Bounty)
Skill Modified
Skill name: dast-config
Skill path:
skills/devsecops/dast-config/What Was Wrong
The skill required OpenAPI import for API scanning, but it did not require proof that the imported specification matched deployed runtime routes or that each operation was actually exercised during the scan. A DAST run could therefore pass after importing a stale or partial OpenAPI file while missing runtime-only, admin, auth-blocked, WAF-blocked, or partially imported endpoints.
What This PR Fixes
1.0.1.Test Cases Added/Updated
Validation run locally:
Bounty Tier
Bounty Info
Closes #1708