Blockchain technology
SU56 Entered authorizations in buffer
SAP HANA (SAP High-Performance Analytic Appliance) is an SAP platform based on in-memory technology. With SAP HANA, you can achieve huge performance increases over traditional databases that were previously unthinkable. This enables you to analyze and evaluate mass data almost in real time without the need for data aggregation.
In order to solve the challenges, it is necessary to develop a suitable catalogue of criteria to evaluate the feasibility or suitability of certain applications for certain service forms. The service catalogue must be structured in such a way that the criteria, which cannot be answered clearly, can be identified and subjected to continuous consideration. The catalogue of criteria cannot generally provide a 100% decision, but only a decision aid and an absolute must-criteria.
Design of applications
SAP's client concept enables a SAP system to be split into several logical sub-systems - clients. These subsystems can be used independently and in isolation as separate systems. But how should non-client transactions be treated? How can you prevent one client from accessing the other and why should you want to prevent that? In this blog post, I will answer these questions and discuss some negative examples. Why is it important to consider independent transactions separately? Imagine that every one of your employees is allowed to create or change a client in the production system, or worse, both. Creating and modifying a client in the production system is authorised and documented - you wonder what could possibly go wrong? The risk in this case is a loss of integrity of system and data, loss of confidentiality: With each new client, Superuser SAP* lives up to its comprehensive, cross-client rights and the assigned standard password.
After the addition of Java Stack (the applications developed in J2EE, BSP, JSP, etc.), the security standard for business processes was increased. Both ABAP and Java stack can be monitored from one platform. Netweaver supports standard protocols such as HTTP, SMTP, XML, SOAP, SSO, WEBDAV, WSDL, WMLSSO, SSL, X.509 and Unicode format (text processing representation).
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.
Following the recommendation of dividing the SAP basis into an application-orientated and infrastructure-related SAP basis [A4], Figure 3 shows a possible presentation form.
Manual identification of critical SAP permissions is difficult overall.