SAP Authorizations Detect critical base permissions that should not be in application roles - SAP Stuff

Direkt zum Seiteninhalt
Detect critical base permissions that should not be in application roles
Unclear objectives and lack of definition of own security standards
You can use authorization objects to restrict access to tables or their content through transactions, such as SE16 or SM30. The S_TABU_DIS authorization object allows you to grant access to tables associated with specific table permission groups. You can view, maintain, and assign table permission groups in transaction SE54 (see Tip 55, "Maintain table permission groups"). For example, if an administrator should have access to user management tables, check the permission status using the SE54 transaction. You will notice that all the user management tables are assigned to the SC table permission group.

Incorrect use of the user types and password rules can result in the shutdown of the RFC interfaces. Find out what types of users you can use and how the password rules affect these types of users. In the SAP system, you can choose between different user types when creating users. These user types control the login behaviour and also the impact of password rules on the user. This can lead to undesirable behaviour, especially if the parameter for the validity of the initial password is set. It is often not known that the password rules also apply to users of the communication type. Communication users usually use an initial password because a dialogue is not possible and the password is not changed. If parameters for the validity of the initial password are now also introduced, these also apply to communication users. We will show you how to prevent such problems and give you an overview of the types of users and the impact of the password rules.
What to do when the auditor comes - Part 1: Processes and documentation
Look closely at the security advisory so that you can identify the affected programmes or functions and schedule appropriate application tests. Use a test implementation in the SNOTE transaction to identify additional SAP hints that are required for a security advisory and may also contain functional changes.

The possibility of assigning authorizations during the go-live can be additionally secured by using "Shortcut for SAP systems".

The website "www.sap-corner.de" offers a lot of useful information about SAP authorizations.

If a login is now made via other authentication methods (such as SSO), these are not affected by the password lock.

SAP Stuff
Zurück zum Seiteninhalt