Sensitive personal column exposed to report authors
"Sensitive personal column exposed to report authors" is one of the governance checks Auditabi runs on a Power BI semantic model. n visible column(s) look like personal data (birth date, national id, salary, phone, address, IBAN). It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Remove the column, hide it, or replace it by a bucket (age band, salary band) if the analysis needs the shape and not the value.
What is detected
n visible column(s) look like personal data (birth date, national id, salary, phone, address, IBAN). Anyone who can open the model can read them and build a visual on them.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Remove the column, hide it, or replace it by a bucket (age band, salary band) if the analysis needs the shape and not the value.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.