> 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/iac-security/iam/appsec-git-6.md).

# GitHub repository defined in Terraform does not have GPG signatures for all commits misconfiguration

## GitHub repository defined in Terraform does not have GPG signatures for all commits misconfiguration detected in code

### Rule Details

|                        |                         |
| ---------------------- | ----------------------- |
| Cortex AppSec Rule ID  | APPSEC\_GIT\_6          |
| Category - Subcategory | IAM - Overly Permissive |
| Provider               | OTHER                   |
| Severity               | LOW                     |
| Framework              | Terraform               |

### Impact

Requiring signed commits on GitHub is a security practice that ensures every commit is signed with a GPG or S/MIME signature, verifying the identity of the commit author and ensuring that the commit hasn't been tampered with after it was signed. This rule ensures that branch protection rules enforce a requirement for signed commits.

When branch protection rules are configured to require signed commits, it prevents unverified commits from being pushed to the protected branches, thus safeguarding the codebase against unauthorized modifications.

### How to Fix

To comply with this rule, you must enable the requirement for signed commits in your GitHub branch protection rules.

### By setting the `require_signed_commits` attribute to `true`, you enforce that all commits to the protected branch must be signed, thus upholding the integrity and authenticity of your codebase. \[source,go]

resource "github\_branch\_protection" "example" { repository\_id = github\_repository.example.node\_id pattern = "main"

## Enforce all commits to be signed

* require\_signed\_commits = true

## ... other branch protection settings ...

### }


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/iam/appsec-git-6.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.