{"meta":{"title":"Remediate leaked secrets","intro":"Learn how to identify and remediate leaked secrets in your codebase.","product":"Security and code quality","breadcrumbs":[{"href":"/en/code-security","title":"Security and code quality"},{"href":"/en/code-security/tutorials","title":"Tutorials"},{"href":"/en/code-security/tutorials/remediate-leaked-secrets","title":"Remediate leaked secrets"}],"documentType":"subcategory"},"body":"# Remediate leaked secrets\n\nLearn how to identify and remediate leaked secrets in your codebase.\n\n## Links\n\n* [Calculating the cost savings of push protection](/en/code-security/tutorials/remediate-leaked-secrets/calculate-cost-savings)\n\n  Estimate the remediation time and labor costs you'll avoid by preventing leaked secrets.\n\n* [Assessing the impact of GitHub Secret Protection](/en/code-security/tutorials/remediate-leaked-secrets/assessing-ghsp-impact)\n\n  Measure how GitHub Secret Protection reduces secret exposure across your organization, so you can demonstrate value and identify areas to strengthen your security posture.\n\n* [Evaluating alerts from secret scanning](/en/code-security/tutorials/remediate-leaked-secrets/evaluating-alerts)\n\n  Learn about additional features that can help you evaluate alerts and prioritize their remediation, such as checking a secret's validity.\n\n* [Remediating a leaked secret in your repository](/en/code-security/tutorials/remediate-leaked-secrets/remediating-a-leaked-secret)\n\n  Learn how to respond effectively to a leaked secret in your GitHub repository."}