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 branch protection is enforced on the default branch

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

Why this matters

The default branch (for example, main or master) is typically the source of production deployments and represents the most critical part of your codebase.
Without branch protection, contributors—including admins—can push or merge changes directly, bypassing review, testing, or CI/CD validation.

Enforcing branch protection on the default branch ensures that:

  • All commits to the primary branch are reviewed and verified
  • CI/CD status checks and quality gates must pass before merge
  • Direct pushes, force pushes, or unreviewed merges are prevented

Without this control, untested or unauthorized code changes could be introduced, increasing the risk of instability and security incidents.

What this check does

This check verifies that the repository’s default branch is covered by at least one branch protection rule.
A valid rule should enforce restrictions such as required reviews, passing status checks, or restricted pushes.

How to fix it

From the GitHub Web Console

  1. Go to the repository on GitHub.
  2. Navigate to Settings → Branches.
  3. Under Branch protection rules, click Add rule.
  4. In the Branch name pattern field, enter your default branch name (for example, main).
  5. Configure desired protections such as:
    • Require pull request reviews before merging
    • Require status checks to pass before merging
    • Include administrators
    • Require conversation resolution before merging
  6. Click Create or Save changes.

Once created, the default branch becomes protected, and direct pushes or unreviewed merges will be blocked.

Exceptions

  • Admins can still modify or delete the protection rule unless organization policies restrict it.
  • Repositories using automated pipelines may need to whitelist service accounts for merges.
  • Branch protection must be configured per repository—it is not inherited organization-wide by default.

Further Resources

Was this article helpful?

Powered by Product Fruits