redact-secret · Report

Service account token

glsa_ prefixed service account token.

Grafana
Detectors: grafana-service-account-token
Run 2026-10-07
Mode published · redact-secret 0.1.0-beta.14

Dossier verdictReady
Dossier evidence levelT1 · Provider-documented
Dossier researched2026-09-23

New pipelineAuthority

Built from the new pipeline

The new pipeline is the authority for credential qualification. These numbers are read from the qualification view derived from the official credential-eval run of the public-evidence-snapshot population. The regression and policy populations keep their own counts on the qualification pages and are not added in here.

Authority: new
Population: public-evidence-snapshot
Engine: credential-eval 0.1.0-alpha.16
Evidence: snapshot-2026.10.06.4
Run: sha256:4bec6e539482…
Recorded: 2026-10-07
Authorised for: @redact-secret/core@0.1.0-beta.14

Maintainer-reviewed (independent review pending)

598 fixtures of the 7,041 in evidence release snapshot-2026.10.06.4 carry this label. They are counted in the numbers on this page.

Passed the project’s own verification (source evidence, automated checks, recorded counter-arguments); not yet independently reviewed.

OpenRedaction default (all patterns): not measured in this run (optional)

The default (all-pattern) profile is slow and noisy for credential evaluation: personal data and resource identifiers dominate its findings, and its last official measurement took 7 minutes of scanner time on a population the credential profile scans in seconds (its methods run takes 40+ minutes), so it is a manual measurement and never blocks other scanners or core verification (#763). Its earlier results stay as history with their run identity; the credential profile is a separate scanner, never spliced with it.

Last measurement: policy-corpus@linux-x64 (configuration sha256:2451ce7bf380), public-evidence-snapshot+methods@linux-x64 (configuration sha256:d47d081ce5fb), public-evidence-snapshot@linux-x64 (configuration sha256:2451ce7bf380), regression-corpus@linux-x64 (configuration sha256:2451ce7bf380) · engine 0.1.0-alpha.5 · recorded 2026-10-05 · retained record, no longer listed by the run registry. It stays labelled with that run identity and is never combined with another profile or another run.

Open the qualification page for this pointer

OpenRedaction credential profile (33 types): not measured in an official run (local exploratory diagnostics only: see ADR)

The credential profile is the comparison profile chosen in docs/decisions/2026-10-06-choose-the-openredaction-credential-bearing-profile-as-the-comparison-scanner.md. It is optional in the official run class because no pinned engine configuration measures it yet: making it required would refuse every official view until the owner approves the one profile-only run. Its own history starts with that run; nothing of the default's is reused for it.

No earlier measurement of it is recorded. Nothing is shown in its place.

Official measurement: pending: requires owner approval (one profile-only run; see the decision).

Open the qualification page for this pointer

Every population and its qualification

Research record

From credential-evidence snapshot-2026.10.06.4 · records at 77ce761 · schema 1.8.0. It describes the research on the format, not what any scanner or the product does, and not a support status.

Review stateDraft, not reviewed
Format revision1 · current
ResearchResearched
Researched2026-09-23

2 events in the review history: 1 observed, 1 reviewed. Latest: observed on 2026-09-23 by automation, project maintainer. Project-maintained review is not independent validation. The family record at this release.

Format

Provider format research from credential-evidence snapshot-2026.10.06.4 · records at 77ce761 · schema 1.8.0.

What it looks like

Descriptive pattern: ^glsa_[A-Za-z0-9]{32}_[0-9A-Fa-f]{8}$

Parts are shown as recorded. Evidence classes belong to the facts below; no class is assigned to a part.

Format facts

Provider documented · provider-source · current · observed 2026-09-23
glsa service-account token prefix: Grafana states that service account tokens carry a glsa prefix; the delimiter, segment lengths, alphabet and checksum placement remain tool-corroborated
- grafana.com/blog/new-in-grafana-9-1-service-accounts-are-now-ga/provider-documentation · last read 2026-09-23 · latest outcome read · supports Grafana states that service account tokens carry a glsa prefix; the delimiter, segment lengths, alphabet and checksum placement remain tool-corroborated
Tool corroborated · tool-corroboration · current · observed 2026-09-23
Pinned scanner rules are consistent with the contract grammar (2 artifacts: gitleaks 8.30.1; trufflehog 3.97.4).
- gitleaks/gitleaks @ v8.30.1: config/gitleaks.tomlscanner-rule-source · last read 2026-10-04 · latest outcome read · supports gitleaks 8.30.1: gitleaks.toml
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/grafanaserviceaccount/grafanaserviceaccount.goscanner-rule-source · last read 2026-09-23 · latest outcome read · supports trufflehog 3.97.4: grafanaserviceaccount/grafanaserviceaccount
Provider documented · dossier-research · current · observed 2026-09-23
Legacy dossier research (verdict ready, tier T1) cited 2 sources; the dossier does not attribute sources to individual properties.
- redact-secret/redact-secret @ 8b6a5fde52ecb4dfce13f09c7a947062d21483c7: docs/audits/evidence/642/README.mdproject-research-note · last read 2026-09-23 · latest outcome read · supports Final research evidence recorded by the legacy dossier
- grafana.com/blog/new-in-grafana-9-1-service-accounts-are-now-ga/provider-documentation · last read 2026-09-23 · latest outcome read · supports Cited by the legacy dossier research for this family

Open questions

No open question is recorded for this revision.

Benchmark dossier notes

From the provider dossier, as written. The evidence level above says how well the format is backed; a fact the dossier does not record is not shown.

Shape: literal glsa_, 32 alphanumeric characters, a second _, then an 8-character hexadecimal checksum, 46 characters in all.
Basis: T1 for the prefix and the existence of a checksum: Grafana's 9.1 service-accounts announcement says tokens can be identified by a "glsa" prefix and that a checksum was added. It gives no length. The two _ separators, the 32/8 split and the checksum alphabet come from gitleaks 8.30.1, with trufflehog's Grafana detector agreeing on the glsa_ shape.
Contract in core: detector-families.md.

In this benchmark

Fixture rows on the current run. Counts are for redact-secret in published · redact-secret 0.1.0-beta.14 mode.

Fixtures: 36
Left readable: 0
Redacted too much: 0
False alarms: 0

36 fixtures: 17 expect a redaction, 19 must stay quiet. See every row

redact-secret fixture counts by evidence level
Evidence level	Fixtures	Left readable	Too much	False alarms
T1Provider-documented	17	0	0	0
T2Tool-corroborated	15	0	0	0
T3Project policy	4	0	0	0

Every scanner on the same fixtures

In run order. Counts are what each scanner recorded on this family's fixtures, whichever rules it has; a scanner with no rule for the family has nothing to report on it.

Counts per scanner on this family's fixtures
Scanner	Fixtures	Left readable	Too much
flare-redactRuntime library · 1.6.1 · Published npm package · secrets-only (pii, generic_assignment disabled) · JavaScript engineNo rule maps to it	36	15	1
gitleaksRepository scanner · 8.30.1 · Directory scan · default rules1 rule targets it	36	0	0
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped	36	0	0
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabled1 rule targets it	36	17	0

Benchmark dossier questions

Things the sources do not settle. They are listed so nobody reads them as settled.

Open caveat: Provider text gives only the glsa prefix and that a checksum exists; separators, segment widths and the checksum alphabet are tool-corroborated (T2).

Looks like it, but isn't

Values the dossier records as resembling this credential without being one.

Collisions: the legacy API key is a base64-encoded JSON object and is a different credential.

Scanner rules for this family

Mapped by hand (reviewed 2026-09-30) from each scanner's pinned rule file, never from what a scanner found on the fixtures.

Peer scanner rules that target this family
Scanner	Rule	What the rule matches
gitleaks · rules 8.30.1	`grafana-service-account-token`	glsa_ + 32 characters + _ + 8 hex
trufflehog · rules 3.97.4	`grafanaserviceaccount`	glsa_ + 41 characters

No rule maps to this family in flare-redact, openredaction.

Find

Evidence level

Scanners

36 of 36 rows

Fixtures in this family

36 rows, redact-secret's outcome on each. Rows that need a look come first (0), then the rest in corpus order. Choose "Every scanner" to see each scanner's outcome for the same rows.

Fixtures in Service account token
Fixture	Kind and evidence	redact-secret
`grafana-service-account-token-bom`grafana · multibyte-text-offsets	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-checksum-segment-bare`grafana · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-checksum-segment-quoted`grafana · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-checksum-segment-unicode-crlf`grafana · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-compose-renderer-env`grafana · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-env-service-account-token`grafana · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-github-actions-dashboards`grafana · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-http-api-bearer`grafana · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-json`grafana · structured-text-value	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-markdown`grafana · markdown-and-comment-value	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-no-final-newline`grafana · value-at-input-edges	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-python`grafana · source-code-string-literal	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-python-requests-client`grafana · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-single-quotes`grafana · quoted-value-extent	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-terraform-provider`grafana · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-toml`grafana · structured-text-value	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-yaml`grafana · structured-text-value	Must redactT1 · Provider-documented	Redacted
`grafana-service-account-token-audit-token-hash-encoded-value`grafana · benign-encoded-value	Must not flagT2 · Tool-corroborated	Quiet
`grafana-service-account-token-bom-twin`grafana · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`grafana-service-account-token-checksum-segment-bare-twin`grafana · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`grafana-service-account-token-checksum-segment-quoted-twin`grafana · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`grafana-service-account-token-checksum-segment-unicode-crlf-twin`grafana · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`grafana-service-account-token-json-twin`grafana · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`grafana-service-account-token-label-prose`grafana · benign-lookalike	Must not flagT3 · Project policy	Quiet
`grafana-service-account-token-markdown-twin`grafana · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`grafana-service-account-token-mask`grafana · benign-lookalike	Must not flagT3 · Project policy	Quiet
`grafana-service-account-token-missing-separator`grafana · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`grafana-service-account-token-no-final-newline-twin`grafana · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`grafana-service-account-token-python-twin`grafana · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`grafana-service-account-token-reference`grafana · benign-lookalike	Must not flagT3 · Project policy	Quiet
`grafana-service-account-token-rotation-note-prose`grafana · prose-mention	Must not flagT3 · Project policy	Quiet
`grafana-service-account-token-service-account-listing-public-id`grafana · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`grafana-service-account-token-short-checksum`grafana · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`grafana-service-account-token-single-quotes-twin`grafana · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`grafana-service-account-token-toml-twin`grafana · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`grafana-service-account-token-yaml-twin`grafana · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet

Sources

Researched 2026-09-23.

Documentation and code

grafana.com/blog/new-in-grafana-9-1-service-accounts-are-now-ga/

Research log

redact-secret/redact-secret#305Research issue
redact-secret/redact-secret#642Research issue
Final evidence, pinned to a commit/redact-secret/redact-secret/blob/8b6a5fde52ecb4dfce13f09c7a947062d21483c7/docs/audits/evidence/642/README.md

Other Grafana families

Cloud access policy token