diff --git a/.github/workflows/security.yml b/.github/workflows/security.yml
index a29d346..dde5020 100644
--- a/.github/workflows/security.yml
+++ b/.github/workflows/security.yml
@@ -440,7 +440,16 @@ jobs:
           curl -fsSL "https://github.com/zizmorcore/zizmor/releases/download/v${VER}/zizmor-x86_64-unknown-linux-gnu.tar.gz" \
             | sudo tar -xz -C /usr/local/bin zizmor
           zizmor --version
-          bash .cc-security-rules/bin/run-zizmor.sh zizmor.sarif .
+          # Stage the script out of the workspace and drop the checkout before
+          # scanning. zizmor is pointed at "." and actions/checkout can only write
+          # inside the workspace, so leaving .cc-security-rules in place would put
+          # THIS repo's workflows into the consumer's scan — findings attributed to
+          # a build that does not own the file, and with zizmor-blocking a failure
+          # the consumer cannot fix. Keeps the scan scope identical to before the
+          # script was introduced.
+          cp .cc-security-rules/bin/run-zizmor.sh "$RUNNER_TEMP/"
+          rm -rf .cc-security-rules
+          bash "$RUNNER_TEMP/run-zizmor.sh" zizmor.sarif .
       - name: Upload SARIF
         if: always()
         uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a  # v7.0.1 (node24)
diff --git a/bin/test-run-zizmor.sh b/bin/test-run-zizmor.sh
index 9eaa2fc..8d7e7f0 100755
--- a/bin/test-run-zizmor.sh
+++ b/bin/test-run-zizmor.sh
@@ -87,9 +87,24 @@ check "unrelated failure is not retried"  "$(calls)" "1"
 WF="${ROOT}/.github/workflows/security.yml"
 if [ -f "$WF" ]; then
   check "the runner is actually called" \
-    "$(grep -c 'run-zizmor.sh zizmor.sarif' "$WF")" "1"
+    "$(grep -cE 'run-zizmor\.sh"? zizmor\.sarif' "$WF")" "1"
   check "zizmor is not invoked inline" \
     "$(grep -cE '^\s+zizmor --no-progress' "$WF")" "0"
+
+  # --- scan scope: the rules checkout must not become audit input -------------
+  # The script is delivered by checking this repo out into .cc-security-rules
+  # inside the consumer's workspace. zizmor is pointed at ".", so that checkout
+  # lands in the scan and the consumer gets findings for THIS repo's workflows
+  # attributed to its own build. Harmless while these workflows are clean;
+  # actively misleading the moment they are not, and with zizmor-blocking it
+  # would fail every consumer for a file they do not own. Stage the script out of
+  # the tree and delete the checkout before scanning.
+  check "the runner is staged out of the scanned tree" \
+    "$(grep -cE 'RUNNER_TEMP/run-zizmor\.sh"? zizmor\.sarif' "$WF")" "1"
+  check "the rules checkout is removed before scanning" \
+    "$(grep -c 'rm -rf .cc-security-rules' "$WF")" "1"
+  check "the runner is not invoked from inside the checkout" \
+    "$(grep -cE 'bash \.cc-security-rules/bin/run-zizmor\.sh' "$WF")" "0"
 fi
 
 echo "run-zizmor tests: ${pass} passed, ${fail} failed"