A field-secured value copied into an unsecured column
What it is
Secured column value lands in an unsecured column.
Why it matters
A field mapping or formula copies a secured value into an unsecured column, so anyone who can read the destination reads the protected value without a grant. An active leak of data you deliberately gated.
Find it yourself
List your field-secured columns, then check two things for each: attribute mappings from that column to a child table, and any calculated or rollup column whose formula reads it. Where the destination is not itself secured, the protection is bypassed. This is the highest-value check in this family and the least likely to be done.
How to fix it
Secure the destination the same way or break the mapping, and clear values already copied.
Related controls
These mappings are indicative. Pathix detects a condition relevant to a control. It does not certify your compliance, and a finding is not an audit opinion. You stay responsible for your control environment.
Pathix checks this across every environment you scan, along with 39 other conditions. Self-hosted in your own Azure, read-only, metadata-only.