I'm new to FGA auditing and have created an FGA policy for SELECT on table T column SSN. This works well. Any user that specifically selects column T.SSN, generates a row in my audit table. (I'm using DB 11.2.0.4)

select T.SSN from T; -- generates an audit row
select * from T; -- generates and audit row

Then I have created a view V with 2 table columns. One of the table columns is T.SSN, the other is T.DOB.
So my view only has two columns, V.SSN and V.DOB

So now if I query view V:
select V.SSN from V; -- generates an audit row as expected
select * from V; -- generates an audit row as expected

now the false positive!!
select V.DOB from V; -- generates an audit row. Very Unexpected. The user actually never selected the SSN column but because the user was querying through a view which happens to contain the SSN, FGA audits the select.

Is there a way to prevent this false positive while still keeping the SSN column in the view?

Has anyone ever run into this before?


Thanks in advance for any advice you could offer.
Bob