SAP Basis PROJECT HISTORIES - NW Admin

Direkt zum Seiteninhalt
PROJECT HISTORIES
Analysis and elimination of technical problems in the SAP Basis environment under the platforms ORACLE and Windows
The presentation view is used to visualize the applications and data for the user. The presentation is done with the help of a graphical user interface (GUI). Furthermore, the presentation view consists of several modules, which are also summarized as SAP GUI. SAP Fiori is the presentation layer of the next generation and is therefore particularly user-friendly.

Remove weak password hashes from the system: Only updating the profile parameter does not provide you with the necessary security. There are still many weak hash values in your database that can be used to attack your system. These must be completely removed from the database. To do this, use the report CLEANUP_PASSWORD_HASH_VALUES. To do this, call the transaction SA38 and enter the name of the report in the input field. Run or F8 executes the programme and cleans your database Report CLEANUP_PASSWORD_HASH_VALUES This programme removes the outdated hash values across all clients. Have you already experienced this attack method or any other comments on this topic? Share your experiences with us in the form of a comment under this article.
Preparation of full access to SAP systems and solutions in case of disasters (High Availability/Disaster Recovery)
This makes the technical user the dialogue user and a login in the SAP system is unrestricted. So Johannes logs in with the known password of the RFC user in the production system. Thanks to very extensive permissions, it now has access to all sorts of critical tables, transactions, and programmes in production. With the identity of the RFC user Johannes starts with the technical compromise of the production system... RFC Security: All invented - or everyday threat? Whether a simple trim, altered biometric properties or an encapsulated technical user in the SAP system: the basis of the compromise is the same. A person uses a different identity to gain access and permissions to protected areas. Moreover, the evil in all three stories could have been prevented by pro-activity. When was the last time you thought about the security of your RFC interfaces? Can you say with certainty that all your technical RFC users only have the permissions they actually need? And do you know who exactly knows the passwords of these users? Can you 100% rule out that not now in this moment an SAP user with a false identity infiltrates your production systems? Change now: It's about pro activity! But before you start now and start looking for the "identity converter" (which I really do not recommend!), I suggest that you take root of evil and proactively strengthen your RFC security. So if you want to find out more, I have the following 3 tips for you: 1) Our e-book about SAP RFC interfaces 2) Clean up our free webinar about RFC interfaces 3) Blog post about our approach to optimising RFC interfaces As always, I look forward to your feedback and comments directly below these lines!

The website www.sap-corner.de offers many useful information about SAP basis.


SAP recommends a role design for Fiori permissions based on the defined catalogues and groups in the launchpad. In such a catalogue there is usually a set of apps and services which is relevant for a specific user group. If a role for one or more catalogues in the launchpad has been authorised, the corresponding catalogues and groups will be displayed in the app finder only for eligible users when the launchpad is launched. This ensures that every user only sees what they are working with. Important: These Fiori permissions are maintained on the frontend server! Maintain catalogue permissions in the PFCG To add a Fiori permission to open a catalogue for a role, reopen this role in the PFCG in Change mode and follow the next steps: 1) Select Menu tab 2) Click on the small arrow to add an item 3) Select "SAP Fiori Tile Catalogue" Then select the corresponding Catalogue ID for which the selected role should be eligible. Now the role only has to be assigned to the corresponding users in the system. Once you have completed these steps, you will have the Fiori permissions you need to view individual tile catalogues on the launchpad.

For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.

Network-based ACL The network-based ACL file contains permitted and prohibited subnets or specific clients.

So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.

Quite a lot of power! Did you also know that the SAP system provides a feature that deletes table change protocols (DBTA BLOG table) and that it is effective across all clients? If the table change logs have not been additionally archived via the BC_DBLOGS archiving object, traceability is no longer available.
NW BASIS
Zurück zum Seiteninhalt