Classification and masking

Describe what each topic holds, who owns it and how sensitive it is, and hide personal data from everyone who browses it in KCM.

Starter and above

Topic metadata

Open a topic and its metadata tab to record:

Editing metadata needs a cluster EDITOR or ADMIN role, or a topic grant with ALTER; reading it needs VIEWER or DESCRIBE. Metadata can be locked against changes.

Classification

FieldValues
Data sensitivityPUBLIC, INTERNAL, CONFIDENTIAL, RESTRICTED
ContentsContains PII, PCI, PHI or secrets; in GDPR scope
RequirementsMasking required, encryption required
Legal basisConsent, contract, legitimate interest, legal obligation, vital interest, public task
Residency and retentionData residency constraint, retention policy, duration and justification
PII fieldsThe fields to mask, see below

Masking

Masking is on for a topic when Masking required is checked and at least one PII field is listed. Each masked value is replaced with <ANONYMIZED>, whatever its type (text, number, boolean, object or array), and the message stays valid JSON.

PII fields syntax

EntryMasks
emailEvery JSON field named exactly email, at any depth, inside arrays too (backup_email is not matched).
customer.address.streetThat path from the root of the value. Arrays on the way are traversed.
$.phones[*].numberSame as phones.number: a leading $. and [*], [] or [0] are accepted. An index masks every element.
$keyThe whole message key.

Where masking applies

Masking applies to every user, global administrators included: KCM has no permission to see masked values.

What masking does not cover

Masking protects what KCM displays. It does not change the data in Kafka. Replaying a message by its offset re-produces the original record, and ksqlDB or Flink SQL results are not masked. Restrict those features with roles on sensitive clusters.