All Topics
All Topics
Technology
Technology
AI
AI
Business
Business
Entertainment
Entertainment
News
News
Programming
Programming
Security
Security
Science
Science
Design
Design
Environment
Environment
Finance
Finance
Crypto
Crypto
Politics
Politics
Sports
Sports
Education
Education
Gaming
Gaming
Art
Art
Music
Music
Health
Health
Books
Books
Food
Food
Travel
Travel
Personal
Personal
Bluesky
Twitter

GitHub introduces workflow execution protections to control who can trigger Actions

By

Allison

2h ago· 2 min readenNews

Summary

GitHub has introduced Workflow Execution Protections in public preview for GitHub Enterprise, organizations, and repositories. This feature allows enterprise administrators to define an allow list that controls who can trigger GitHub Actions workflows and which events are permitted to run them. It addresses a security gap where attackers with repository access could modify workflow files to run malicious code, by letting administrators define rules that GitHub enforces.

Source

bskyGitHub introduces workflow execution protections to control who can trigger Actionsgithub.blog

Key quotes

· 3 pulled
This new capability lets enterprise administrators define an allow list that controls who can trigger GitHub Actions workflows and which events are permitted to run them, giving you predictable, secure workflow execution.
Previously, a workflow ran based on the workflow file in the commit that triggered it. An attacker with repository access could modify that file to run malicious code.
Workflow execution protections close that gap. Administrators define the rules and GitHub A
Snippet from the RSS feed
Workflow execution protections are now in public preview for GitHub Enterprise, organizations, and repositories. This new capability lets enterprise administrators define an allow list that controls who can trigger GitHub…

You might also wanna read

Comments

Sign in to join the conversation.

No comments yet. Be the first.