Rule set sha256:ef0271a74ba2
rego-gdpr32-1-001
One rule of the rule set with digest ef0271a74ba2f80b96890ef958bdd3699e910badcbf1e7578d9efa398d6f21d8. An audit record that names this digest and this rule was decided by the rule as shown here. Every rule in this set.
| Rule | rego-gdpr32-1-001 |
|---|---|
| Rule version | 38973ff94c53e77016eb55e2903ddbe0ea0dcd3d8a2a6c00bff7515866663b0c |
| Provision | Regulation (EU) 2016/679, Article 32(1) ELI: http://data.europa.eu/eli/reg/2016/679/art_32/par_1/oj |
| Approval | Not approved |
rules/rego/complyedge/data_protection/api_key.rego
- Citation
- Regulation (EU) 2016/679 (GDPR), Article 32(1)
- Condition
- The text carries a live credential in a vendor's published key format: AWS access key id (AKIA/ASIA + 16), GitHub token (ghp_/gho_/ghu_/ghs_/ghr_ + 36, github_pat_), OpenAI (sk- / sk-proj-), Anthropic (sk-ant-), Stripe live keys (sk_live_ / rk_live_), Slack (xoxb-/xoxp-/xoxa-/xoxr-/xoxs-), Google API key (AIza + 35), a JSON Web Token (three base64url segments starting eyJ), or an "Authorization: Bearer" header with a 20+ character token. Stripe TEST keys, AWS's documented example key (ending EXAMPLE), the key id inside a presigned S3 URL, and a JWT that is a URL query value (a magic link addressed to its recipient) do not fire.
- Condition type
- deterministic (format match plus checksum; no judgment of meaning)
- Status in the file
- review