Original announcement: · Reporting prepared on the publication date above.
What to know
- GitHub added detection for Cloudflare Access service tokens. The important step after an alert is rotation and scope review, not just deleting a line of code.
The new detector
GitHub announced on November 12 that secret scanning can identify Cloudflare Access service tokens in repositories. The supported secret type is named cloudflare_access_service_token. GitHub distinguishes partner detections in public repositories, which can be reported to the issuer, from user alerts in public or private repositories. The exact alert behavior depends on repository settings and the secret-scanning features available to the account.
Why this matters for a server team
Service tokens often let automation reach protected dashboards, staging environments or internal APIs. A token copied into a Git repository may remain exposed in history even after the latest commit removes it. First find out what the token can access, when it was created and which jobs use it. Revoke or rotate it at Cloudflare, update the secret store and verify that the deployment still works.
Review whether the automation truly needs that scope. A job that deploys one website should not share a credential with unrelated infrastructure. Put expiry and ownership in your inventory so a forgotten token does not remain active for years.
Keep the next token out of the repository
Store credentials in a managed secret store, keep logs from echoing them and use a short lifetime where possible. Pull requests from untrusted code should not receive production secrets. A failed scan is not proof that no secret was committed; detectors cover specific patterns and may not identify a transformed or custom key.
For deployments to a cloud VPS, our GitHub Actions security guide covers permission boundaries and review gates. Use the official GitHub notice to confirm current detection support.
Sources & further reading
Primary sources supporting this article. The practical recommendations are Kiava’s general guidance and should be adapted to your project.
Your experience. The next chapter.
Tried this guide, or have a question? Add your experience to the conversation.
This conversation starts with you.
A useful question or a short experience can help the next reader.





Discussion 0
Newest first