Insert Queue
The basics of Basis Administration
The presentation layer is the interface to the users. Through a graphical interface, users enter data or interact with data through the applications. This presentation layer exchanges data with the application layer.
The tasks of a company's own SAP Basis department are undergoing enormous change at many companies, as SAP is also relying more and more on cloud services. Strategically, completely self-hosted SAP systems are becoming rarer and the proportion of customers using an SAP system from the cloud is increasing. The new roles of SAP Basis employees tend to be "enablers" and coordinators between the cloud provider and internal IT and the business departments. Until that time comes, companies can also rely on external service providers to offer expert know-how as well as operational support for the transition period.
Provision of the services and basics
The Technical Lead functions as the work package leader or sub-project manager within the SAP basis when the project is the focus of the SAP basis. The Technical Lead will become more important in the future as the SAP basis acts as a technology consultant and more projects and project activities are expected in the future. This role must be filled more and more often. Due to the increased demands, this role and the associated activities must be professionalised through training and further training.
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.
"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP base.
It also sets measurable targets for the next three years.
But, for the most part, the following three options have proven effective as a consensus mechanism: 1) Proof of Work 2) Proof of Stake 3) Proof of Importance The differences are presented in another blog post.