During numerous customer engagements, I learned that there is an increasing need, or even a mandate, to enable database auditing due to company policies, industry regulations, or the law. Auditing typically is enabled at both the SAP application level as well as the database level. Database-level auditing additionally captures workload and connections originating from outside the core SAP application, like direct connections to the database from a command line interface or the workload of third-party tools.
However, auditing both the SAP application and the database can lead to significant redundancy in audit data and thus can increase storage requirements.
This raises an important question: How can this redundancy be minimized or avoided, while still maintaining a secure and compliant audit trail?
During numerous customer engagements, I learned that there is an increasing need, or even a mandate, to enable database auditing due to company policies, industry regulations, or the law. Auditing typically is enabled at both the SAP application level as well as the database level. Database-level auditing additionally captures workload and connections originating from outside the core SAP application, like direct connections to the database from a command line interface or the workload of third-party tools.However, auditing both the SAP application and the database can lead to significant redundancy in audit data and thus can increase storage requirements.This raises an important question: How can this redundancy be minimized or avoided, while still maintaining a secure and compliant audit trail? Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
