Repository navigation
Secret scanning: Extend coverage to Actions logs #449
Description
Activity
- locked and limited conversation to collaborators
on Feb 9, 2022 This issue is being closed as outdated. For more information, please check out this Discussion post. Stay tuned for new additions to our refreshed public roadmap!
We wanted to provide more details on why we removed this from the roadmap. This effort is under review by the product team. This has been removed from the roadmap until we can provide a more accurate delivery estimate.
If you’re interested in this feature, please share your feedback in the GitHub community so we can track interest and consider it in the future.
Summary
Secrets can be found in code and non-code content. We'll begin scanning Actions logs for potentially leaked secrets to more thoroughly protect our Advanced Security customers.
Intended Outcome
A secret leaked in any content type poses a risk to our users. We're minimizing the risk of exposure by expanding our scope of scans to include Actions logs.
How will it work?
Advanced Security customers will be able to view any detections in Actions logs within the secret scanning UI.