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 only signed commits are accepted

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

Why this matters

Signed commits verify the identity of the contributor and ensure that code changes originate from a trusted source.
Unsigned or unverified commits can be spoofed, making it difficult to trace accountability or detect unauthorized modifications.

Requiring signed commits helps to:

  • Guarantee commit authenticity and author integrity
  • Prevent unauthorized or tampered code from entering production
  • Maintain an auditable and trusted commit history

Without this enforcement, malicious actors could impersonate valid contributors or inject unverified changes into critical branches.

What this check does

This check verifies that protected branches (especially the default branch) have the “Require signed commits” option enabled in their branch protection rule.
When active, GitHub will reject any commits that are not signed and verified with a GPG or SSH signature.

How to fix it

From the GitHub Web Console

  1. Go to your repository on GitHub.
  2. Navigate to Settings → Branches.
  3. Under Branch protection rules, click Add rule or edit the existing rule for the default branch (e.g., main).
  4. Scroll to Require signed commits and check the box.
  5. Click Save changes.

From this point forward, commits that are not signed and verified will be rejected when pushed or merged into the protected branch.

Exceptions

  • Only commits signed with verified GPG or SSH keys are accepted. Users must add and verify their signing keys in their GitHub account settings.
  • Admins can bypass this requirement unless “Include administrators” is also enabled in the branch protection rule.
  • Unsigned merge commits created via the web interface will also be rejected.

Further Resources

Was this article helpful?

Powered by Product Fruits