> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-206.md).

# Default branch does not require signed commits

## Rule Details

|                       |                   |
| --------------------- | ----------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_206 |
| Category              | IAM               |
| Severity              | LOW               |

## Impact

Unsigned commits in GitHub present significant risks, including compromising code integrity and introducing uncertainty regarding authorship. If an attacker gains unauthorized access to a developer's account, they could impersonate the developer and make malicious code commits undetected. The absence of signed commits makes it exceedingly difficult to distinguish between fraudulent and legitimate commits.

## Recommended Solution - Buildtime

It is recommended configuring a rule requiring the use of signed commits on the default branch:

1. In GitHub, browse to the repository **Settings** > select **Branches** under **Code and automation**.
2. Select **Add a branch protection rule** (or edit an existing one) on the relevant branch > Check the **Require signed commits** under **Protect matching branches** > **Create**.

To create a branch protection rule refer to <https://docs.github.com/en/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule#creating-a-branch-protection-rule>.

For additional information about signed commits refer to <https://docs.github.com/en/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-signed-commits>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-206.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.