SAP Basis SAP Authorization Concept

Direkt zum Seiteninhalt
SAP Authorization Concept
SWDM Business Workflow Explorer
In earlier product generations, databases from various third-party providers were used - primarily Oracle and Microsoft SQL. However, this has changed with the introduction of the new database generation SAP HANA.

Will Blockchain's Economy and Administration Revolutionise? What is a blockchain? A blockchain is a complete and unchanging transaction history of all transactions of a decentralised community that everyone who is part of it agrees to. The word blockchain first fell in connection with Bitcoin as a decentralised network for payments in the digital currency of the same name. The blockchain describes an underlying technology in which all transactions are publicly and unchangeably recorded. This transaction history is updated periodically. Each participant in the decentralised community accepts it as a reality, stores it on their computer, and can thus ensure at any time that no one can duplicate expenditure, as this would lead to a conflict in the transaction history elsewhere. A peculiarity of blockchain technology is that it has solved the "Double Spending Problem". Double-spending means something that can be doubled, and by 2008, only one central institution was considered to be sustainable. Double Spending can best be understood using the example of an image on a mobile phone. When I upload it to Facebook, I made a copy of it and I can upload it to Instagram, for example. So I used my picture "double". This effect made it impossible to establish a trustworthy, decentralised digital currency by 2008.
Free-form recognition and document check
Basis comprises a number of middleware programs and tools from SAP. Basis is responsible for the smooth operation of the SAP Basis system and thus for R/3 and SAP ERP, for example. SAP thus provides the underlying basis (hence the name) that enables various SAP applications to be interoperable and portable across operating systems and databases.

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!

"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.

For example, an employee who has permissions in accounts payable and accounts receivable violates the SoD ("Segregation of Duties") principle and poses a potential security risk to your company.

In the case of unsuccessful tests, where subsequent or additional developments are due and the cause of the error is not directly apparent at first glance, good result documentation often pays off.
SAP Corner
Zurück zum Seiteninhalt