Google Cloud API key: format and detection

What it is

Google Cloud API keys identify a project to services such as Maps or Gemini and can be restricted by referrer or API. The Credentials pack covers them and masks them by default.

In Maskflare this is the detector gcp_api_key, labelled "GCP API key", category password or access key, in the Credentials pack.

Format

• The literal prefix AIza.
• 35 characters from letters, digits, underscore and hyphen.

How Maskflare recognises it

Prefix, exact length, entropy floor of 4.0 and a word boundary at the start.

A list of sample keys that appear in public documentation is on the allow list, so they are not masked.

Why this page shows no sample key

A realistic sample key would look like a live credential to secret scanners and to anyone skimming the page, and an obviously fake one would not pass this detector's length and entropy rules. The format above is enough to recognise the key: the prefix, the length and the character set.

Regex and validation caveats

• The pattern wants the key to be followed by a quote, a backtick, whitespace, a semicolon, an escaped newline or the end of the text. A key directly followed by a comma or a closing bracket is therefore not matched by this pattern.
• Keys that are restricted to a referrer are less risky, but the detector cannot see the restriction, so it masks all of them.
• Google service-account JSON files and OAuth client secrets are separate formats.

How to detect it in LLM traffic

Keys are embedded in front-end code, mobile app configuration and map snippets, all of which people paste into assistants when asking for help.

Maskflare reads the whole request body, including the system prompt, earlier messages and tool arguments, and replaces each match with a token such as mf_mask_d7e0 before the request goes out. Coding agents are covered through hooks that mask tool inputs and results, so a key printed by a shell command does not travel onward in the next prompt. On ChatGPT, browser protection blocks prompts that contain API keys, tokens or private keys outright.

If you build the detection yourself

1. Scan the raw text rather than parsed fields: keys sit in code, JSON strings, headers, shell output and pasted logs, often with no label at all.
2. Match the prefix and the exact length for the Google Cloud API key. Where the key has no fixed prefix, require the provider's name and an assignment next to the value instead of matching any long string.
3. Compute the Shannon entropy of the candidate and reject low values, and keep an allow list of placeholders (${KEY}, repeated characters, the alphabet run), because documentation and templates are full of them.
4. Mask the value before the text is sent anywhere. If the key was already sent, treat it as exposed and rotate it; masking later does not recall it.

How Maskflare handles it

• Protect now, Finance - Protect now, Healthcare, Developer and Monitor first: mask (a reversible token).

The available actions are mask (reversible token), redact, partial, hash, format-preserving encryption, generalize, alert and block. Masked values are kept encrypted for 30 days so that answers can be restored, then they expire; prompts and responses are not logged. The full list of detectors is in the detector reference.

Compliance profiles that include it

All 6 compliance profiles include the Credentials pack, and applying them turns this detector on: HIPAA Safe Harbor, GDPR - EU/EEA, UK GDPR, PCI DSS, US personal data and Switzerland - nDSG health data. A profile is a floor: it never turns anything off or weakens a rule that is already stricter.