Learn how to use the ROI calculator to estimate the remediation time and labor costs you'll avoid by preventing leaked secrets.
Organization owners and security managers
The calculator is available in organizations on GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server (For GitHub Enterprise Server, from version 3.20 only).
You can use the ROI calculator to estimate the cost avoided by preventing leaked secrets with push protection. This information can help you:
Push protection is a paid feature which is available with GitHub Secret Protection. For more information, see Choosing GitHub Secret Protection.
On GitHub, navigate to the main page of the organization.
Under your organization name, click Security.
In the sidebar, under "Security", click Assessments.
On the top right corner of the banner, click Get started.
In the dropdown, select Estimate push protection savings.
Review the non-editable value for "Preventable leaks" (P). If 0, a baseline value (such as 70) is shown for modeling purposes.
Enter or adjust the average developer annual compensation (C), in USD.
Enter or adjust the time to remediate each leaked secret (T), in hours. We recommend you use an average remediation time that reflects steps for revoking, rotating, and validating secrets, as well as notifying your teams or customers:
Review the outputs from the Return on investment panel:
Did you successfully use the ROI calculator to estimate the cost savings of using push protection on your organization?
No
Next, review the results to understand their implications and determine the appropriate scope for rolling out push protection in your organization. Keep the following information in mind as you interpret your results.
The calculator does:
The calculator does not:
If you run into problems using the calculator, use the following table to troubleshoot.
(Secrets prevented) × (Time to remediate) × (Hourly rate)
Salary ÷ 2080
resources