Explore how we might allow users to test and validate security tool configurations before introducing them into their development workflow
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Recommendation from Secure - Audit of scanner configuration UI
Problem to Solve
The job statement below is documented in the secure & protect JTBD handbook page but none it GitLab's security tools currently satisfy this job. This issue is to explore how we might empower users to test and validate GitLab's security tools (including user-defined configuration options) before implementing them into their development workflow (i.e. demo scans).
When I am either enabling or configuring a security scan, I want to run a demo scan, So that I can validate my configuration before it is implemented
Proposal
To be determined...
Edited by 🤖 GitLab Bot 🤖