Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delegated alert closures for secret scanning [GA] #1047

Open
glider-bot opened this issue Nov 20, 2024 · 0 comments
Open

Delegated alert closures for secret scanning [GA] #1047

glider-bot opened this issue Nov 20, 2024 · 0 comments
Labels
ga Feature phase: Generally available GitHub Advanced Security (GHAS) Product SKU: GitHub Advanced Security

Comments

@glider-bot
Copy link
Collaborator

Value Prop

Delegated alert closures help security teams with lower tolerance for risk by providing additional controls and visibility around alert closures. Enterprise teams with security, auditing, and compliance requirements can now control who can close alerts, when and how alerts can be closed, and who can approve this activity.

Expected Outcome

Delegated alert closures will 1) increase accountability across their development teams when it comes to addressing alerts, 2) prevent insecure activity (e.g. mistakes or malicious action internally), and 3) improve ability to manage alerts at scale, by making alert activity easier to govern.

@glider-bot glider-bot added ga Feature phase: Generally available GitHub Advanced Security (GHAS) Product SKU: GitHub Advanced Security security-products-gtm labels Nov 20, 2024
@glider-bot glider-bot moved this to Q2 2025 – Apr-Jun in GitHub Public Roadmap Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ga Feature phase: Generally available GitHub Advanced Security (GHAS) Product SKU: GitHub Advanced Security
Projects
Status: Q2 2025 – Apr-Jun
Development

No branches or pull requests

2 participants