Fix and Break
A long list of findings hides a useful fact: many of them have the same fix. Upgrade one base image and hundreds of findings can disappear. These two centers are about spending your effort where it counts.
Fix Center
Fix Center answers one question: what fixes the most findings with the least work, starting from the highest risk?
| Fix type | What it means |
|---|---|
| Base image | Move to a newer base image. |
| Upgrade | Upgrade a dependency. |
| Secret rotation | Rotate an exposed secret. |
| Code change | Change your code. |
| Config change | Change a setting. |
| IaC pull request | Change infrastructure as code through a pull request. |
Each fix carries an effort of low, medium or high, and moves through a status such as recommended, pr_open, in_progress and done. You can also accept or dismiss one.
Break Center
Break Center is coming soon. You can join early access per product from the page.
Break Center will prove which findings an attacker could really exploit. A proven finding sits at the last code-to-exploit stage, which ends the argument about whether it is worth fixing.
Try this next
Open Fix Center and take the top item with an effort of low. Removing the most risk for the least effort is what this page is for.