Audit on Tables/fields

[MThomas1]

Hello,

we are requesting guidance on Auditing ON for tables.

1. what is the best practice for Audit enabling?
2. which tables are recommended for Audit ON/NOT ON ?
3. Any tables not recommended for Audit ON?
4. Any disadvantages with auditing ON? system performance impact? Any processing delay expected?
5. is it safe to ON auditing for user/group tables?
6.how to read/report on audit tables?

Thank you an appreciate your guidance on the request.

[GlideFather]

Hi @MThomas1,

just a pedantic remark, the Audit value is not on/off but true/false 😛 regarding your questions, I don't think there is any universal answer, historic values in some fields are not allowed to be audited due to specific purposes (DORA, GDPR, ISOs...). 

Regarding the performance, I guess that would be valid consideration if you would audit all the fields from all the tables, but it will be difference between audits on a custom table with 10K records and auditing CMDB with millions of records..

Rather it shall be done smart and to meet business needs of your organisation.

I found only this presentation: Audit Management - Process Workshop Presentation, perhaps you can review the Best Practice Library (ex Now Create) in more details