Security in the SAP System EnvironmentPosted: November 5, 2012
During a course called ADM960 at SAP, we covered numerous topics which included the fundamental concepts of authentication, encryption and network infrastructure, configuration of single sign-on, certificates-based authentication, system auditing in AS ABAP, AS Java, etc. Despite the fact that I haven’t had previous hands-on knowledge on SAP technologies and administration, I found the overall concepts pretty simple. My experience in security-related issues helped me out. All the exercises aided me in raising my awareness about security topics in SAP NetWeaver Application Server 7.00. I learned some basic transactions for password and roles auditing. I also found the configuration of SAProuter and trusted relationship to be somewhat interesting.
There are several things to remember:
- Pay attention to SAP standard users like “SAP*”. Remember that the configuration may differ depending on the system you’re using: ABAP or Java. This standard user always uses “pass” as the password. You have to clone that account and block the original one (remove all authorizations).
- Monitor services which you are actually using (including system services) and block all others.
- You can use the “se95” transaction to monitor changes.
- Use the “RSECNOTE” tool to check for critical security updates.
- For ABAP system monitoring use transaction “sm19” for audit configuration and “sm20” for log monitoring. For Java go to: SAP Netweaver Administration – System Management- Monitoring – Logs and Traces
- Use the “suim” transaction for users monitoring: authorizations, roles and account change control.
- Use the “rz20” transaction to access Alert monitor.
The “sa38” transaction is used to run reports.
For more information please refer to the original SAP Security Guidance
Image courtesy of jscreationzs / FreeDigitalPhotos.net