Rule set sha256:a7e715b79299
rego-gdpr32-1-002
One rule of the rule set with digest a7e715b792994b004a7cc9714100077fad036164172ce42812ed396af0b727f5. 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-002 |
|---|---|
| Rule version | 69cdbc04b42cb8d6786628454b1473525c8436a8f24c358d2ba5f302508efa76 |
| Provision | Regulation (EU) 2016/679, Article 32(1)(b) ELI: http://data.europa.eu/eli/reg/2016/679/art_32/par_1/pnt_b/oj |
| Approval | Approved Approved by Leo Celis on 2026-10-22 (via agent review per §5.1 amendment v1.1) |
rules/rego/complyedge/data_protection/private_key.rego
- Citation
- Regulation (EU) 2016/679 (GDPR), Article 32(1)(b)
- Condition
- The text carries a PEM private key block header (five dashes, BEGIN, the key type, PRIVATE KEY, five dashes), or the RSA / EC / DSA / OPENSSH / ENCRYPTED variants, or a PGP PRIVATE KEY BLOCK. Public keys and certificates (BEGIN PUBLIC KEY, BEGIN CERTIFICATE) do not fire.
- Layer 1 detects
- the line -----BEGIN PRIVATE KEY-----, the same with RSA, EC, DSA, OPENSSH or ENCRYPTED before PRIVATE KEY, or -----BEGIN PGP PRIVATE KEY BLOCK-----, in capitals as written. It matches formats, not purpose: a credential in a format not named here is missed (a PuTTY key file, PuTTY-User-Key-File-3 with its Private-Lines), and it does not read why the value is in the text. No model reviews a hit: a match keeps the block in Layer 2 as well.
- Condition type
- deterministic (format match only, no checksum exists for this value; no judgment of meaning)
- Status in the file
- approved