From 1fc341aaa1b9a4af3c2fbf0229a1703f08645213 Mon Sep 17 00:00:00 2001
From: "compliance-pr-automation[bot]"
 <1425255+compliance-pr-automation-bot[bot]@users.noreply.github.com>
Date: Wed, 27 Aug 2025 10:37:02 +0000
Subject: [PATCH] [Compliance] - PR Template Changes Required

---
 .github/pull_request_template.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 48217eaa..52b1dde0 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -58,3 +58,17 @@ Example: If a change needs to be reverted, we will roll out an update to the cod
 <!--
 Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
 -->
+
+## PCI review checklist
+
+<!-- heimdall_github_prtemplate:grc-pci_dss-2024-01-05 -->
+
+- [ ] I have documented a clear reason for, and description of, the change I am making.
+
+- [ ] If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
+
+- [ ] If applicable, I've documented the impact of any changes to security controls.
+
+  Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.
+
+If you have any questions, please contact your direct supervisor, GRC (#team-grc), or the PCI working group (#proj-pci-reboot). You can also find more information at [PCI Compliance](https://hashicorp.atlassian.net/wiki/spaces/SEC/pages/2784559202/PCI+Compliance).