redact-secret · Report

Cloud API secret (unprefixed, pre-2025-07-30)

Unprefixed 64-byte base64-body API secret, recognized only beside a same-line confluent keyword.

Confluent Cloud
Detectors: confluent-cloud-api-secret-legacy
Run 2026-10-07
Mode published · redact-secret 0.1.0-beta.14

Dossier verdictReady
Dossier evidence levelT2 · Tool-corroborated
Dossier researched2026-09-24

redact-secret#309 (product PR #667). Scored as policy (no value grammar), like twilio:auth-token.

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-24

3 events in the review history: 2 observed, 1 reviewed. Latest: observed on 2026-09-24 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

Shape not recorded.

Format facts

Tool corroborated · tool-corroboration · current · observed 2026-09-17
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/confluent/confluent.goscanner-rule-source · last read 2026-09-23 · latest outcome read · supports trufflehog 3.97.4: confluent/confluent
Tool corroborated · field-context-gate · current · observed 2026-09-17
context gate: no value grammar of its own: scored as policy, only beside a same-line confluent keyword
- gitleaks/gitleaks @ v8.30.1: config/gitleaks.tomlscanner-rule-source · last read 2026-10-04 · latest outcome read · supports context gate: no value grammar of its own: scored as policy, only beside a same-line confluent keyword
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/confluent/confluent.goscanner-rule-source · last read 2026-09-23 · latest outcome read · supports context gate: no value grammar of its own: scored as policy, only beside a same-line confluent keyword
Provider documented · field-prefix · current · observed 2026-09-24
prefix: secrets created before 2025-07-30 "may not include cflt"; the release notes say "do not have" and "on or after" — the cut-over wording differs across three provider pages
- docs.confluent.io/cloud/current/security/authenticate/workload-identities/service-accounts/api-keys/overview.htmlprovider-documentation · last read 2026-09-24 · latest outcome read · supports prefix: secrets created before 2025-07-30 "may not include cflt"; the release notes say "do not have" and "on or after" — the cut-over wording differs across three provider pages
- docs.confluent.io/cloud/current/release-notes/index.htmlprovider-documentation · last read 2026-09-24 · latest outcome read · supports prefix: secrets created before 2025-07-30 "may not include cflt"; the release notes say "do not have" and "on or after" — the cut-over wording differs across three provider pages
Provider documented · field-length · current · observed 2026-09-24
length: 64 characters in every CLI-table placeholder, the Flink JSON example and the provider's Terraform test data; one provider Basic-auth example shows 60 (The 60/64 ambiguity is preserved: positives use 64, and no fixture asserts silence on a 60-character value. The pre-existing 63-character length twin rests on both pinned tools' exact 64-character rules.)
- docs.confluent.io/cloud/current/connectors/connect-api-section.htmlprovider-documentation · last read 2026-09-24 · latest outcome read · supports 60-character example
- docs.confluent.io/cloud/current/flink/operate-and-deploy/generate-api-key-for-flink.htmlprovider-documentation · last read 2026-09-24 · latest outcome read · supports length: 64 characters in every CLI-table placeholder, the Flink JSON example and the provider's Terraform test data; one provider Basic-auth example shows 60
- github.com/redact-secret/redact-secret-benchmarks/issues/233provider-documentation · last read 2026-09-24 · latest outcome read · supports length: 64 characters in every CLI-table placeholder, the Flink JSON example and the provider's Terraform test data; one provider Basic-auth example shows 60
Provider documented · field-alphabet · current · observed 2026-09-24
alphabet: A-Z a-z 0-9 + / with no = padding in any example
- github.com/redact-secret/redact-secret-benchmarks/issues/233provider-documentation · last read 2026-09-24 · latest outcome read · supports alphabet: A-Z a-z 0-9 + / with no = padding in any example
Unresolved · field-current-issuance-reproducibility · current · observed 2026-09-24
current-issuance reproducibility: a new key is always the cflt generation, so no new legacy secret can be issued; only an existing pre-cut-over key could corroborate
- github.com/redact-secret/redact-secret-benchmarks/issues/233provider-documentation · last read 2026-09-24 · latest outcome read · supports current-issuance reproducibility: a new key is always the cflt generation, so no new legacy secret can be issued; only an existing pre-cut-over key could corroborate
Unresolved · dossier-research · current · observed 2026-09-24
Legacy dossier research (verdict ready, tier T2) cited 3 sources; the dossier does not attribute sources to individual properties.
- docs.confluent.io/cloud/current/security/authenticate/workload-identities/service-accounts/api-keys/overview.htmlprovider-documentation · last read 2026-09-24 · latest outcome read · supports Cited by the legacy dossier research for this family
- docs.confluent.io/cloud/current/security/authenticate/identity-faq.htmlprovider-documentation · last read 2026-09-24 · latest outcome read · supports Cited by the legacy dossier research for this family
- docs.confluent.io/cloud/current/release-notes/index.htmlprovider-documentation · last read 2026-09-24 · latest outcome read · supports Cited by the legacy dossier research for this family
Unresolved · taxonomy-sources · current · observed 2026-09-24
The legacy taxonomy lists 1 source for this family. The taxonomy records no date; the dossier researchedAt is used as the observed-at date.
- docs.confluent.io/cloud/current/security/authenticate/workload-identities/service-accounts/api-keys/overview.htmlprovider-documentation · last read 2026-09-24 · latest outcome read · supports Listed as a source for this family in the legacy taxonomy

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: an unprefixed 64-character run over A-Z a-z 0-9 + /. No checksum is documented. Confluent's CLI-table examples, Flink example and Terraform provider test data show 64; one Connect API Basic-auth example shows 60 (probably a hand-edited placeholder).
Basis: T2. Provider examples and provider test fixtures corroborate length and alphabet; gitleaks ([a-z0-9]{64}, (?i), no + or /) and trufflehog ([a-zA-Z0-9+/]{64}, key and secret pair required) supply the rule shape and the keyword gate. Kingfisher imports the gitleaks lineage and is not independent.
Issuance: not possible; new secrets are prefixed. Cannot be re-observed.
Contract in core: detector-families.md (keyword-gated legacy shape, confidence-gated).

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: 60
Left readable: 0
Redacted too much: 0
False alarms: 0

60 fixtures: 41 must stay quiet, 19 record project policy. See every row

redact-secret fixture counts by evidence level
Evidence level	Fixtures	Left readable	Too much	False alarms
T2Tool-corroborated	18	0	0	0
T3Project policy	42	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	False alarms
flare-redactRuntime library · 1.6.1 · Published npm package · secrets-only (pii, generic_assignment disabled) · JavaScript engineNo rule maps to it	60	18	1	0
gitleaksRepository scanner · 8.30.1 · Directory scan · default rules1 rule targets it	60	11	0	2
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped	60	0	0	0
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabled1 rule targets it	60	19	0	0

Benchmark dossier questions

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

Open caveat: Provider states no length or alphabet for the unprefixed form; 64 comes from doc examples, provider test data and two scanner rules, one doc example shows 60. No legacy secret can be newly issued.

Looks like it, but isn't

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

Collisions: any 64-character base64-alphabet run, including a 64-hex digest, so the value is only claimed beside a confluent keyword. A prefixed secret also satisfies this shape. Percent-encoding of + and / inside URL userinfo breaks the run.

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	`confluent-secret-key`	confluent keyword + 64 alphanumerics
trufflehog · rules 3.97.4	`confluent`	confluent keyword + 64 characters

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

Find

Evidence level

Scanners

60 of 60 rows

Fixtures in this family

60 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 Cloud API secret (unprefixed, pre-2025-07-30)
Fixture	Kind and evidence	redact-secret
`confluent-cloud-api-secret-legacy-actions-env`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-api-key-id-public-id`confluent · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`confluent-cloud-api-secret-legacy-api-key-store`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-client-config-create`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-client-log`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-compose-jaas`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-connect-worker-config`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-env`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-export`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-global-key-id-public-id`confluent · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`confluent-cloud-api-secret-legacy-iam-curl`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-java-client-properties`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-js-constant`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-k8s-secret`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-keyword-context-bare`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-keyword-context-quoted`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-keyword-context-unicode-crlf`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-librdkafka-dict`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-schema-registry-url`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-schema-registry-user-info`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-tfvars`confluent · documented-format-literal	Project policyT3 · Project policy	Redacted
`confluent-cloud-api-secret-legacy-actions-context-twin`confluent · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`confluent-cloud-api-secret-legacy-actions-secret-reference`confluent · templated-reference	Must not flagT3 · Project policy	Quiet
`confluent-cloud-api-secret-legacy-angle-secret-placeholder`confluent · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`confluent-cloud-api-secret-legacy-api-key-list-public-id`confluent · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`confluent-cloud-api-secret-legacy-api-key-store-context-twin`confluent · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`confluent-cloud-api-secret-legacy-bootstrap-host-public-id`confluent · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`confluent-cloud-api-secret-legacy-cflt-asset-url-near-miss`confluent · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet
`confluent-cloud-api-secret-legacy-config-provider-reference`confluent · templated-reference	Must not flagT3 · Project policy	Quiet
`confluent-cloud-api-secret-legacy-config-provider-reference-templated-reference`confluent · templated-reference	Must not flagT3 · Project policy	Quiet
`confluent-cloud-api-secret-legacy-current-generation-tfvars-twin`confluent · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`confluent-cloud-api-secret-legacy-current-generation-twin`confluent · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`confluent-cloud-api-secret-legacy-env-context-twin`confluent · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`confluent-cloud-api-secret-legacy-export-context-twin`confluent · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`confluent-cloud-api-secret-legacy-iam-curl-context-twin`confluent · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`confluent-cloud-api-secret-legacy-image-digest-encoded-value`confluent · benign-encoded-value	Must not flagT2 · Tool-corroborated	Quiet
`confluent-cloud-api-secret-legacy-jaas-template-placeholder`confluent · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`confluent-cloud-api-secret-legacy-js-constant-context-twin`confluent · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`confluent-cloud-api-secret-legacy-k8s-secret-context-twin`confluent · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`confluent-cloud-api-secret-legacy-key-id-twice-near-miss`confluent · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet
`confluent-cloud-api-secret-legacy-keyword-context-bare-twin`confluent · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`confluent-cloud-api-secret-legacy-keyword-context-quoted-twin`confluent · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`confluent-cloud-api-secret-legacy-keyword-context-unicode-crlf-twin`confluent · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`confluent-cloud-api-secret-legacy-label-prose`confluent · benign-lookalike	Must not flagT3 · Project policy	Quiet
`confluent-cloud-api-secret-legacy-length-63-twin`confluent · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`confluent-cloud-api-secret-legacy-librdkafka-dict-context-twin`confluent · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`confluent-cloud-api-secret-legacy-mask`confluent · benign-lookalike	Must not flagT3 · Project policy	Quiet
`confluent-cloud-api-secret-legacy-masked-table-placeholder`confluent · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`confluent-cloud-api-secret-legacy-missing-keyword`confluent · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`confluent-cloud-api-secret-legacy-one-time-note-prose`confluent · prose-mention	Must not flagT3 · Project policy	Quiet

Sources

Researched 2026-09-24.

Documentation and code

docs.confluent.io/cloud/current/security/authenticate/workload-identities/service-accounts/api-keys/overview.html
docs.confluent.io/cloud/current/release-notes/index.html
docs.confluent.io/cloud/current/security/authenticate/identity-faq.html

Research log

redact-secret/redact-secret-benchmarks#233Research issue

Other Confluent Cloud families

Cloud API secret (cflt-prefixed)