The finding drawer
Open any finding to see everything you need to act:Remediation workflow
1
Open the finding and read the chain
The source-to-sink chain and the primary vulnerable step tell you exactly why
the path is exploitable. Validate it against your environment.
2
Decide the disposition
Set the status from the menu in the drawer’s header: keep it Open, move
it to In Progress, or mark it Accepted Risk or False Positive if
it doesn’t apply. Leave a note on Activity explaining why. See
False positives and context.
3
Fix the root cause
Apply the suggested patch or write your own. Prefer removing the unsafe pattern
over hiding the symptom. Use auto-fix PRs to ship
the patch in one click.
4
Track the work where your team lives
Create a Jira, Linear, ClickUp, or Shortcut ticket, or get a
Slack nudge, so remediation lands in your normal flow.
5
Confirm it's fixed
Merging a Gecko fix PR marks the finding Fixed. For fixes you ship
yourself, turn on Fix detection and re-scan the branch the fix merged
into. See Fix a finding and confirm it’s gone.
Prioritize by impact
Start with the worst paths
Auth bypass, secrets, remote execution, SSRF, and broad data exposure first.
Severity and confidence are right there to sort by.
Filter to what's actionable
Filter the Findings table by status, severity, type, repository, branch,
age, or date to build a focused worklist. The Default branch and
Pull requests tabs separate your backlog from findings on open PRs.
Use bulk actions
Select multiple findings to change status in bulk, or use Fix to open
one PR for findings from the same repository and scan.
Make it routine
The best teams treat remediation as a repeatable loop, not an exception.