In GHES 3.4, GitHub Advanced Security customers can retrieve commit details of secrets detected in private repository scans via the GitHub REST API. The new endpoint will surface the location of a secret's first detection within a file as well as the commit author.
Intended Outcome
Security teams often need more context on a detected secret to take appropriate action and secure their repos. Enabling these teams to better track exposed credentials with information on commit location facilitates a more efficient remediation process.
How will it work?
Enterprise customers upgraded to GHES 3.4 can access the new endpoint.
The text was updated successfully, but these errors were encountered:
Summary
In GHES 3.4, GitHub Advanced Security customers can retrieve commit details of secrets detected in private repository scans via the GitHub REST API. The new endpoint will surface the location of a secret's first detection within a file as well as the commit author.
Intended Outcome
Security teams often need more context on a detected secret to take appropriate action and secure their repos. Enabling these teams to better track exposed credentials with information on commit location facilitates a more efficient remediation process.
How will it work?
Enterprise customers upgraded to GHES 3.4 can access the new endpoint.
The text was updated successfully, but these errors were encountered: