# Upcoming deprecation of security-related organization API fields

DevFeed: [Upcoming deprecation of security-related organization API fields](<https://devfeed.tech/articles/upcoming-deprecation-of-security-related-organization-api-fields-71924.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-03-24-upcoming-deprecation-of-security-related-organization-api-fields>)

Author: Allison

Published: 2026-03-24T21:11:01Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [deprecation](<https://devfeed.tech/tags/deprecation.md>), [github](<https://devfeed.tech/tags/github.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [security-product](<https://devfeed.tech/tags/security-product.md>)

## AI overview

GitHub will remove seven security-related fields from its organization REST API endpoints on April 21, 2026. Organizations should migrate to GitHub Code Security configurations and update scripts and integrations that use the fields.

## Source excerpt

On April 21, 2026, we're deprecating and removing the following fields from the get an organization and update an organization REST API endpoints: advanced_security_enabled_for_new_repositories dependabot_alerts_enabled_for_new_repositories dependabot_security_updates_enabled_for_new_repositories dependency_graph_enabled_for_new_repositories secret_scanning_enabled_for_new_repositories secret_scanning_push_protection_enabled_for_new_repositories secret_scanning_validity_checks_enabled...