System Operation & Availability
Preparation of full access to SAP systems and solutions in case of disasters (High Availability/Disaster Recovery)
This access method depends solely on the rights assigned to the user. System users: Users of this user group are comparable to SAP*. They act as administrator in the system. Therefore, they should be deactivated / set to inactive as soon as possible, as soon as the system operation is ensured. You should still be aware of the SAP ERP environment to address this security risk. In a HANA system, there are privileges instead of permissions. The difference is first of all in terms of terminology. Nevertheless, the permissions are assigned differently (directly / indirectly) via the assignment of roles. These are thus accumulations of privileges. As in older SAP systems, system users must be disabled and certain roles that already exist must be restricted. Compared to an SAP ERP system, small apps are allowed instead of large applications. In this case, attention should be paid to an individual authorisation. It should be a matter of course for users to have implemented secure password rules. Settings Securing the system also means securing the underlying infrastructure. Everything from the network to the host's operating system must be secured. When looking at the system landscape, it is striking that the new technology brings many connections that need to be secured. The SAP Gateway, which is responsible for the connection between backend and frontend, is also a security risk and must be considered. All security settings of existing and future components must be validated to HANA compatibility. Secure communication of connections is obtained when you restrict access where possible. Encryption of the data of a HANA system is disabled by default. Be sure to encrypt sensitive data anyway. Especially data that is archived. If an attack is made on your system, you should be able to run forensic analysis, so you should enable the audit log. Moreover, few users should have access to it.
On the one hand, staff clerks (or other personnel officials) should be able to carry out their important work. On the other hand, the protection of personal data of one's own employees is one of the most important tasks of the authorisation system. Any mistake in this area can cause the company's data protection officers to wring their hands over their heads. For this reason, tools are currently being developed to provide security and visibility in the HR permissions area. The basic idea is a clear overview that shows which data certain users in the SAP system can access. Based on this, automatic checks can be developed, which run in the background and regularly check whether critical gaps have been created by changes to the permissions in the HR area. The use of such a tool can create more security, especially in the HR authorisation environment. In addition, the possibility of the overview function is very pleasant and relieving for all involved. Read more This blog post is intended to show what is already possible in the field of Security Automation. The topic will accompany us more and more in the SAP area in the next few years. Therefore, it is recommended to start thinking about how your company is prepared for security automation. If you are interested in setting up and preparing a company outside the security area, I can recommend the book 'Consulting Y' by Ferdinando Piumelli (Managing Director of mindsquare GmbH). In this book, Mr. Piumelli describes his observations and experiences of digital transformation as a strategy consultant for leading DAX30 companies. In doing so, he is focusing on the near future, which, in the spirit of the digital revolution, will have a major impact on the world's large companies and economy.
OS/400
SAP, as one of the world's leading software providers with over 100,000 employees, represents a central component of their system landscape for many companies. Thanks to the many different modules, such as "Finance" and "Human Capital Management", as well as the wide range of customization options, a broad field of professions and possible areas of focus has opened up here in almost 50 years.
The default permissions to open and use a launchpad are the SAP_UI2_USER_700. The role for the administration is SAP_UI2_ADMIN_700. In the administration interface, the launchpad can be customised, so this permission should only be released to a few users for administration.
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
In addition, the role assigned to the transaction is shown.
Call SPAM.