GBase 8a Applies Data Masking Only on Output, Not on Filters or Sorting
GBase 8a, a column-oriented analytical database, supports data masking policies that replace sensitive column values with defaults for unprivileged users. Testing reveals that masked columns still use original values internally for WHERE filtering, GROUP BY aggregation, and ORDER BY sorting, meaning query logic remains accurate even when displayed output is obscured. However, when masked column data is projected to a client or physically copied via UPDATE or INSERT SELECT, only the masked value is written or returned. This means a user can unknowingly confirm the existence of specific values through filter results, even though the actual data is never directly exposed. The behavior mirrors Oracle Data Redaction policies and has important implications for designing both secure and performant queries in GBase 8a environments.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in