Secret detection UX: easier remediation for secrets
Problem to solve
We are introducing "Perform secret detection on full history", "Secret" is critical and the triage process is different, the following site: https://rtyley.github.io/bfg-repo-cleaner/ provide some examples of how to fix Secrets. How can we help gitlab users to triage secret easily and safely?
Target audience
- Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney
- Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha
- Sidney, Systems Administrator, https://design.gitlab.com/research/personas#persona-sidney
- Sam, Security Analyst, https://design.gitlab.com/research/personas#persona-sam
JTBD: When protecting my project against secret leaks, I want to quickly react to found secrets so that I can be assured my companies keys are safe from bad actors.
Proposal
Design
Edited by Taylor McCaslin