← All permissions
Repository permission·secret_scanning_alerts:write
Secret scanning alerts: Write
Tier 2 · Medium
Why Tier 2
Closes secret scanning alerts, so a leaked credential can be marked as handled.
- Target
- Repository
- Plane
- DataCode security: Code scanning, Dependabot and secret scanning alerts, advisories, dismissals and bypasses.
- Granted by
- Fine-grained PAT, GitHub App
- Available on
- Every setup
What it unlocks
1 REST endpoint needs this permission. A few of them:
- PATCH /repos/{owner}/{repo}/secret-scanning/alerts/{alert_number}
Roles that include it
- T0OwnerThe organization and every repository in it
- T0All-repository adminEvery repository in the organization
- T1WriteOne repository
- T1MaintainOne repository
- T1AdminOne repository
- T1Security managerThe organization and every repository in it
- T1All-repository writeEvery repository in the organization
- T1All-repository maintainEvery repository in the organization
- T1Enterprise security managerEvery organization in the enterprise
Classic scopes that reach it
- T0repodocumented
- T1security_eventsdocumented
Attack paths
No attack technique, escalation or incident on ghtier goes through this yet.
Other levels
GitHub Docs: Repository permissions for "Secret scanning alerts"