{"id":324,"date":"2023-07-05T22:42:01","date_gmt":"2023-07-05T19:42:01","guid":{"rendered":"https:\/\/techltx.com\/de\/?p=324"},"modified":"2023-07-09T23:35:26","modified_gmt":"2023-07-09T20:35:26","slug":"sap-security-audit-log-sm20-data-leak","status":"publish","type":"post","link":"https:\/\/techltx.com\/en\/sap\/sap-security-audit-log-sm20-data-leak\/2023\/07\/","title":{"rendered":"SAP Security Audit Log SM20 data leak detection"},"content":{"rendered":"\n
\n
\n

Dear readers,<\/p>\n

In the ever-evolving world of information technology, the need for secure and comprehensive monitoring mechanisms is increasing. Central to this are security logs that record critical system information. One such tool is the SAP Security Audit Log, an audit log specifically designed to capture security-relevant system information in SAP AS ABAP systems. It documents events such as changes to user master records or unsuccessful login attempts, thereby providing an excellent basis for security analyses and compliance checks.<\/p>\n<\/div>\n\n\n\n

\n
\"SAP<\/a><\/figure>\n<\/div>\n<\/div>\n\n\n

The SAP Security Audit Log, accessible through transaction SM20, allows auditors to gain detailed insights into operations within the AS ABAP system. Once this log is activated, a record of specifically defined activities is created. The types of information that can be logged include successful and unsuccessful dialog and RFC login attempts, RFC calls to function modules, changes to user master records, successful and unsuccessful transaction starts, and changes to the audit configuration. SM20 aids in security monitoring and can be used to detect potential security breaches that might indicate a data leak. However, it is important to emphasize that SM20 is not a specific tool for detecting data leaks, like SAP ETD (Enterprise Threat Detection), for example.<\/p>\n

Here’s an overview:<\/p>\n