Help Center
Go back to application
Help Center
Go back to application
Platform Terms GlossaryContacting Support and Reporting Bugs
Task Management
Task Management explained Creating Tasks Setting up Task NotificationsGiving permissions to team members
Organization
Working together in KertosInviting UsersCreating rolesAssigning System AccessCreating Departments and Assigning Users
Integrations
Discovery
Tasks
Device Management
Human Resource Information Systems
Inventory
Inventorization of vendorsInventorization of systemsInventorization of assetsEU AI Act: Inventorization of AI use cases
Risks
Managing risks
Trust Center
Setting up your trust center
Incidents
Reporting incidents
KAIA
KAIA explainedPrinciples of AI at Kertos
Interacting with KAIA
Compliance
Frameworks explainedManaging & implementing controlsCreating & managing policiesCompleting & assigning trainingsGuidanceDetermining Control Applicability
Privacy Management
Creating a RoPACreating TOMsCreating DPIAs
Data Subject Requests
API Reference
Ingress API Docs for DSRs Webhook API Docs for DSRs
Auto Checks
Auto Checks explainedAuto Checks: AWS Auto Checks: AzureAuto Checks: GCPAuto Checks: GitHubEnabling Auto Checks by Reconfiguring the Azure IntegrationEnabling Auto Checks by Reconfiguring the GCP IntegrationEnabling Auto Checks by Reconfiguring the AWS Integration
AWS Auto Checks Detailed Explanations
Azure Auto Checks Detailed Explanations
GitHub Auto Checks Detailed Explanations
Ensure secret scanning is enabled to detect sensitive dataEnsure code owner approval is required for owned code changesEnsure at least two approvals are required before merging codeEnsure branches are deleted automatically after mergingEnsure unresolved conversations block mergesEnsure force push is disabled for all branchesEnsure admins are subject to branch protection rulesEnsure a CODEOWNERS file exists in the repositoryEnsure inactive repositories are archivedEnsure all required status checks pass before mergingEnsure linear history is enforced on the default branchEnsure branch protection is enforced on the default branchEnsure the default branch cannot be deletedEnsure vulnerability scanning is enabled for repository dependenciesEnsure public repositories include a SECURITY.md fileEnsure all organization members have MFA enabledEnsure only signed commits are accepted

Ensure admins are subject to branch protection rules

Framework Reference: A.8.3 (Information Access Restriction) Integration: GitHub – Branch Protection

Why this matters

Administrators have elevated permissions and can override most repository restrictions by default.
If branch protection rules do not apply to admins, they can merge or push code directly to protected branches without reviews or checks, bypassing security and quality controls.

Enforcing branch protection for administrators ensures that:

  • All contributors, regardless of role, follow the same review and merge process
  • Critical branches (like main or production) remain protected from unreviewed changes
  • The repository maintains consistent compliance with secure development standards

Without this safeguard, even well-intentioned administrative actions can introduce untested or insecure code.

What this check does

This check verifies that “Include administrators” is enabled in the branch protection rules for all protected branches.
When active, this setting enforces the same restrictions—such as required reviews, status checks, and merge rules—on administrators as it does on other users.

How to fix it

From the GitHub Web Console

Go to your repository on GitHub.

  1. Navigate to Settings → Branches.
  2. Under Branch protection rules, click Add rule or edit an existing one.
  3. Scroll to the bottom of the rule configuration.
  4. Check Include administrators to apply all protection rules to admin users.
  5. Click Save changes.

Once enabled, administrators will be required to meet all protection criteria before merging or pushing to the protected branch.

Exceptions

  • Admins can still change or remove the protection rule itself if they have repository admin rights.
  • This control only applies to branches covered by existing protection rules.
  • Organizations using mandatory review policies through GitHub Enterprise may already enforce this globally.

Further Resources

Was this article helpful?

Powered by Product Fruits