Control regarding fuzzing
Open
Nobody has claimed this yet.
criteria
enhancement
- Dominant language
- Go
- Stars
- 166
- Forks
- 44
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 13
Description
In discussing #302 in this week's meeting, we agreed that it is worth entertaining a proposal to add a control for:
Fuzzing/SAST/DAST/etc. scanners - We speak to the need to remediate SCA and SAST scan results, but don't actually advocate for scanning (and nothing on fuzzing). Is this something we should add?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #302 and the proposal quoted here, then review the meeting decision referenced in this issue. The work is to determine whether the baseline should advocate for fuzzing, SAST, DAST, or related scanning and to define the control if so.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100