Decommissioning/uninstallation of SAP systems and their databases
Differentiation from SAP ABAP
This is where all the system's data resides. These are composed of the actual database and the DBMS, the "database management system". In earlier versions, the database here came from different manufacturers. For example, Microsoft SQL or Oracle. Since SAP HANA, a lot has changed for IT in this data layer. This is because the database comes from SAP itself and is automatically monitored by the system. There is more to this database layer than just the working data. Important elements such as the configuration tables and system data for control and application content are also stored here. This is the repository data used by applications.
New risks in SAP HANA: In addition to the known risks, there are also new risks from the use of SAP HANA. A very good example are frequently used web applications that represent something new in the SAP area. In contrast to an SAP ERP system, HANA systems consist mainly of web applications, which were considered optional in the previous versions. These web applications can be found by various search engines on the Internet. This also applies to SAP Portal or Netweaver. There are URL schemes that help locate the system. This also applies to other SAP systems that use Web applications. This makes the new technology vulnerable to typical web attacks. SQL Injection, ABAP Code Injection, or XSS are all included. All risks known for a normal SAP system also apply to a SAP-HANA system. The data is stored unencrypted in RAM. Only then does the system gain this speed advantage. This results in risks such as a read-out by memory scraping malware. These pick up data in memory. Encryption costs performance, so it is not used by default. Especially during a migration HANA runs in a parallel system, therefore at least one new system comes to your landscape. Also note: HANA has its own tools and settings that need to be known and configured. The bottom line is that the system simply needs more attention when operating. Many settings often result in more errors. Three - points - HANA Security Plan 1) Roles and permissions In a previous SAP system, roles and permissions are certainly one of the main pillars of a secure system. Roles and permissions work differently in a HANA system. There are two types of users: 1) Default (limited): With this type of user, there are different access methods to the database. For example, the JDBC or HTTP technologies are used to give two examples.
SAP HANA Cloud Platform (SAP HCP)
The SAP Basis team takes care of the entire administration of an SAP system. As a company, you have to decide whether you want to leave the support of your system within your company or place the "Basis" in the hands of an SAP expert.
As a hint: The menu tab "Jump" allows you to set all namespaces or software components simultaneously to "modifiable" or "non-modifiable". However, before you can rearrange the namespace and software components, you must also adjust the global setting accordingly. With Save or CTRL+S you can now save your new settings and you have already set the system modifiability.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
In order to cope with the digital transformation in general, but also to cope with the changing demands on the SAP basis and its scope of responsibility, it is necessary to revise existing roles and define and establish new roles.
Some useful tips about SAP basis can be found on www.sap-corner.de.
Using this tool allowed us to move from manual validation of critical permissions to an automatic process.