Skip to content

security(PS-1386): add .gitleaksignore for remediated historic gitlab-pat finding - #100

Open
brathina-spectro wants to merge 1 commit into
mainfrom
security/PS-1386-gitleaksignore
Open

security(PS-1386): add .gitleaksignore for remediated historic gitlab-pat finding#100
brathina-spectro wants to merge 1 commit into
mainfrom
security/PS-1386-gitleaksignore

Conversation

@brathina-spectro

@brathina-spectro brathina-spectro commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Remediation for PS-1386 — Gitleaks detected a gitlab-pat in discovery-maas/config-stg/os_ubuntu.yaml:84 on the (unmerged) maas-tf branch.

Remediation performed

  • Token validated & confirmed inactive: GitLab personal_access_tokens/self revocation call returned 401 Unauthorized — the token is expired/revoked and cannot authenticate. No rotation needed; the config was never merged to main or deployed from this repo.
  • Branch maas-tf deleted from origin — the only ref whose history contained the token (commits 8725331 and ccbe3be). Verified no other branch or PR ref contains it; main never did.
  • This PR adds the Gitleaks fingerprints to .gitleaksignore so historic scans do not re-flag the remediated finding.

Follow-up

The two dangling commits remain accessible on GitHub by direct SHA until GitHub Support runs a GC — a support request is being raised as part of ticket closure.

🤖 Generated with Claude Code

…-pat finding

The gitlab-pat flagged by Gitleaks existed only on the maas-tf branch,
which has been deleted from origin. The token itself is inactive
(GitLab API self-revocation returned 401 Unauthorized). Fingerprints
are ignored so historic scans do not re-flag the remediated finding.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant