AGLEA Blog

There are many companies that provide SAP consulting. Each of these, in most cases, also provides support in the SAP security area.

This is absolutely normal. But what is the degree of expertise on these issues?

How much does slavishly following company procedures lead to problems?

Are there any solutions? But what are the impacts in security management? Can we be affected by digital stupidity?

How many times have we heard in the company when creating a new user, "give me a colleague as a reference," that is, in the process of defining a new user, we reason more by copy than by corporate trade.

But is this approach correct? Or does it present some possible problems?

Profiling also exists and can be implemented in the SAP HANA database.

But not all roads lead to the same result. Some choices may not be ideal in the long run and in the management of authorizations in SAP HANA. What is important to know when defining SAP HANA roles?

This is not always done as this database is mainly used when using SAP applications. Such as S/4HANA.

Topics like Least Privileged Access, True Compliance and Accountability are commonplace when it comes to SAP Security.

However, an additional layer of protection, that of biometrics, can be added to the existing set of standard security tools provided by SAP.

Do you use a password to login to SAP systems?

Which are the most obvious cases which you should pay attention to?

SOAR is the acronym for Security Orchestration, Automation, and Response.

Why is it important to know what it is and how is it used? The definition of a SOAR SAP Security system is strategic.

Have you ever heard of this kind of organization?

What is it? How does it work? How is SAP Security managed in this kind of organizations?

What is it? How should you structure it in our opinion?

How should you prepare to activate and evaluate it?

SAP provides pre-defined roles instead of having to create them from scratch.

Is it worth using them or not? Why are they often, or almost always, not used?