Rule set sha256:8425ad0448a8

rego-gdpr32-1-002

One rule of the rule set with digest 8425ad0448a8b5d482b8dabfc7bdd33c8c32cbd5f3b9c1e36e71a8a905fbd467. An audit record that names this digest and this rule was decided by the rule as shown here. Every rule in this set.

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 with five dashes on each side, 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