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 code owner approval is required for owned code changes

Framework Reference: A.8.25 (Secure Development Lifecycle) Integration: GitHub – Branch Protection

Why this matters

Requiring code owner approval ensures that subject-matter experts review and approve any changes made to the parts of the codebase they own.
This helps maintain code quality, accountability, and compliance with secure development practices.

Without mandatory reviews from code owners, unverified changes could bypass critical oversight, introducing security or stability risks.

What this check does

This check verifies that:

  • A CODEOWNERS file exists in the repository, defining ownership for files or directories.
  • A branch protection rule is configured with the “Require review from Code Owners” option enabled for the protected branch (e.g., main).
  • If either the CODEOWNERS file is missing or the branch rule does not require code owner reviews, the check will fail or return “Unable to verify.”

How to fix it

From the GitHub Web Console

  1. In your repository, create or confirm a CODEOWNERS file in one of the supported locations:
  • .github/CODEOWNERS
  • CODEOWNERS (root directory)
  • docs/CODEOWNERS
    (GitHub Docs – File location and syntax)
  1. Navigate to Settings → Branches.
  2. Under Branch protection rules, create or edit the rule for your main or protected branch.
  3. In the “Pull request reviews” section, enable Require review from Code Owners.
  4. Save the rule.

After this is configured, GitHub will require at least one code owner to approve any pull request that modifies files they own.

Exceptions

  • The requirement only applies if a CODEOWNERS file exists and maps the changed files.
  • Admins can bypass this rule unless “Include administrators” is enabled in the branch protection settings.
  • If multiple owners are listed for a path, approval from any one of them satisfies the requirement.

Further Resources

Was this article helpful?

Powered by Product Fruits