What is the best way to audit who has viewed a record in a table?

[miriamberge]

We want to track (on a fairly large table) who has viewed the details of a record.  Essentially this would be an audit for sensitive data stored in the system.  We would not want to restrict the user's access to the table but we would want to be able to provide details if someone came to us and asked who looked at the record.  Ideas? 

[sachin_namjoshi]

I implemented ETL solution with seamless data pump ability to resolve performance issues on huge tables like sys_audit.

With this ETL solution, we can do scheduled export targeted audit records to remote database instance and then users can report on DB instance instead of reporting on service now instance.

This takes load of all huge queries off from service now instance.

OR

There was another solution implemented to integrate business analytics application with service now to pull data from few of these kind of tables with optimized queries using REST APIs on scheduled basis so that users can report on DB instance of business analytics application and NOT on service now instance to save performance.

Regards,

Sachin

[miriamberge]

Thanks everyone for your responses - my main concerns are that I don't want to cause any performance issues and I would prefer not to create a custom table due to the new licensing model.  You've all given me some things to think about and I appreciate the time people took to offer suggestions...  I'll have to give this more thought... thank you!

[SanjivMeher]

Is the custom table licensing model still there? I thought Bill McDermott said, customer wont be charged for custom tables anymore.

[Julian Lemcke]

Yes it is and it depends on the Product. In HRSD for example it is heavily limited to like 5 or 15 tables (don't have the exact amount in mind).