High flexibility for ad hoc growth
System up-to-dateness
Practical experience at home and abroad has given us a proven view of heterogeneous system landscapes. This flows into our consulting as a further plus point and creates not only smooth functionality but also cost efficiency of your individual system landscape.
In this article on SAP Security Automation I would like to take a look at the future of automated processes in the SAP Security area. For many companies, the topic of security automation still offers a lot of potential in terms of time savings and process optimisation. Our daily work environment offers numerous tasks that could be handled excellently automatically. For this reason, in this article I present two of the possibilities that already exist in the broad area of security automation. Security Automation via SAP Security Check The first option of Security Automation, which I want to introduce here, is the automatic verification of the existing permissions. Have you ever wondered who has critical permissions in your SAP system? And have you ever tried to do this by hand? Depending on the level of expertise and experience of the privilege administrator, this is a time-consuming work. If an audit is also announced and the SAP system is to be checked for critical permissions and segregation of duties, then it is very difficult to meet all requirements and secure the eligibility landscape in this respect. For this reason, various vendors provide solutions to automate the verification of the permission system with regard to critical permissions and segregation of duties using tool support. This allows permission administrators to use their valuable time to correct the errors rather than just looking for them. For example, we use a tool that runs through the verification of over 250 rules. We then get an evaluation of which rules are violated and which points are correct. A simple example of such rules is the use of the SAP_ALL profile. Another would be to grant the jump permission in debugging (S_DEVELOP permission object with the ACTVT = 02 field). These are two relatively simple examples of Security Check tools' rulebook. In addition, queries are also made, which are located in the field of Segregation of Duties. Using this tool allowed us to move from manual validation of critical permissions to an automatic process.
Design of applications
If an error occurs, the transaction WE05 can be used to analyse it. What experience have you had with EDI? I look forward to your feedback.
If the additional memory in the Advanced Storage Area is still not sufficient for the user context, the optional second role area can be used. The size of the second roll range is determined by the difference between the parameters ztta/roll_first and ztta/roll_area. Rolling range has been eliminated in kernel release 7.4, so these parameters are obsolete from then on. Instead, the user context is now stored directly in the Advanced Memory.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
In the case of client settings, you should ensure that the production client is protected against overwriting and that changes are only approved via the transport management system (TMS) to ensure traceability.
If the critical permissions, profiles, and roles are identified, they should be adjusted according to the permission planning.