Customer 360 Enterprise Data Platform — Denodo on Azure  ·  View 37 of 39  ·  Assurance

Sensitive Data

Five classes of sensitive data, classified once and enforced everywhere above it.

Editable source SVG draw.io All views
Classify Tag Policy Enforce Prove Direct identifiers Name, tax id pii.direct Deny unless granted Full redaction Access log per query Contact data Email, phone, address pii.contact Partial by role Last four shown Mask applied count Financial Card, IBAN, balance pii.financial Deny by default Tokenised at source Never cached Behavioural Clickstream, sessions pii.behaviour Pseudonymised Hashed device id Re-identification review Derived scores Lifetime value, churn restricted.model Approved purpose only Row filter by book Purpose recorded Sensitive Data — Classified Once, Enforced Everywhere Classification is declared on the integration view, not on each business view. A new business view inherits every mask the moment it is created, which is why the layering rule is a security control. v 1.0 · owner Data & AI Global Practice · date 2026-09

Decisions

  • Classification is declared on the integration view, not on each business view. A new business view inherits every mask the moment it is created, which is what makes the layering rule on view 08 a security control.
  • Financial columns are never cached anywhere, in any form. Removing them from the cache tier removes a whole class of exposure at the cost of one federated call.
  • Behavioural data is pseudonymised at the point of landing rather than at query time, so the raw device identifier never exists in a table anyone can query.

Proof

  • Every access to a direct identifier is logged individually; masking events are counted per query so a sudden drop in masks applied is itself an alert.
  • The CI policy scan compares the published column set against the classification register on every promotion.

Risks

  • Re-identification from behavioural data joined to a small cohort. Pseudonymisation does not prevent it; the mitigation is a minimum cohort size on analytical views and a periodic re-identification review.