Search results for: Security

GitHub security advisories support CVSS 4.0

Copilot Chat in GitHub.com is now contextually aware of GitHub Advanced Security alerts

Secret scanning non-provider patterns inclusion in recommended security configuration

Secret scanning non-provider patterns are included in security configurations

Retrieve the code security configuration currently applied to a repository via API

Code security configurations will replace feature enablement on the organization-level security coverage page on October 15

CSV exports for security alerts on the organization-level security overview dashboard

Introducing metered billing for GitHub Enterprise and GitHub Advanced Security

Validation on package name when submitting a new GitHub security advisory (GHSA)

Deprecation of enum field “detached” from the “get repositories associated with a code security configuration” endpoint

Deprecation of API endpoint to enable or disable a security feature for an organization

Security overview dashboards, secret scanning metrics and enablement trends reports are now generally available

Code security configurations are supported in the audit log

Code security configurations API now includes validity checks, enforcement, and removal

Filter repositories by configuration attachment failure reason in the code security configurations UI

Code security configurations are now GA

Code security configurations will be made generally available (GA) on July 10th, 2024. At that point, we will sunset the organization-level code security settings UI experience along with the API…

Secret scanning validity checks can be enabled through security configurations

Manage code security configurations via API

GitHub is committed to a secure software ecosystem and requires most developers who contribute code on GitHub.com to enable one or more forms of two-factor authentication (2FA).To ensure that all…

Let’s take a look at 10 key moments from the first decade of the GitHub Security Bug Bounty program.