AGLEA Blog

For some SE16 may be an unknown acronym. For others it is the "bread and butter." It is a SAP transaction remarkably familiar to administrators. And often not only them, unfortunately.

But what is it used for? How many versions of it are there? How do you use it and what are the risks involved?

We discuss  it in this article!

There are different formative paths and trainings for the SAP Security area. Below there are the main courses in the SAP Security and Governance area provided by SAP.

During daily support users often have to request some information. By email or by corporate ticketing tool.

What system are you on? What were you doing? What transactions were you using when you received the error and so on 

To facilitate these requests, in the SAP authorizations field, we can define a short user manual to publish, for example on the company intranet. 

Have you replaced the database with SAP HANA? There are several new Security features to activate! 

Enable all features for SAP HANA Security! Follow the tips to protect data and ensure database compliance. 

What are the main questions before starting a revising project of the authorizations in SAP? 

Segregation of Duties project: how many risks need to be defined?

Security for custom code in SAP has always been underestimated in most installations

Only recently, in the last years, customers are starting to understand the true importance of code security, mostly related to ABAP language in SAP case.

The SAP ABAP developer then becomes a strategic figure in making sure that programs security (especially custom code security) is attended to and correctly managed.

How do you make sure to always be on top of the topic?

How does segregation of duties help protect your company data?

Here's why it's important to check how data is exported and by who it's spread

How do you monitor the data exported from SAP ECC?

Many users must be formally authorized in order to do that as part of their job. It’s however of great importance, especially in a GDPR framework, to monitor how and who exports data in a non-authorized way from the SAP system.

How do you do that? Let’s see some paid methods and others included in the SAP business suite

In SAP there is/was a limit on the number of profiles that can be assigned to a user. Historically this limit of 300 and then 312 has been kept to stop the assignment of too many authorizations to users.

Does this limit persist?