INVOICES AND FINANCE
WORKFLOW AND ARCHIVING
E-COMMERCE
SECURITY
ANALYTICS
MARKETING
DIGITISATION OF CONTENT
ROBOTIZATION OF PROCESSESSECPOL - How to Use it Safely
- Security
You may already know that as of SAP 7.40 SP8, you can use SAP security policies (SECPOL) to define user-specific security parameters, as opposed to system profile values.
But did you also know that as a result, you may inadvertently weaken secure values such as login restrictions and password complexity?
Our practical tip will show you how to effectively prevent such weakness.
You can set the parameters of your security rules in a different way, according to:
1. the complexity of the password
2. password change interval
3. login restrictions
You use "SECPOL" transactions to maintain security rules, and you have the ability to define as many rules as you want.
The relationship between the "security policy marker" and system profile values at a glance:
The SU01 transaction is then used to assign for users.
But be careful, because there is a big catch!
Safety rules do not replace the value of individual profiles, but they do replace the ALL values. This means that values that are not defined in the Security Policy are not set to secure values according to RZ10 parameters, but to unsecure values in the user context. In this way, secure values such as login restrictions and password complexity can be accidentally weakened.
The following example shows such behavior:
Our experience in projects has shown that many customers do not expect this behavior from the system. The general expectation is that parameters can be set against the default settings. However, this is not the case.
Our tip for you:
- Safety (SECPOL) rules should only be used if ALL values are defined in a way that is completely similar to RZ10 parameters, with only a few values being stronger or weaker.
- Remember, you adjust all the safety rules by reinforcing the relevant RZ10 system parameters.
To safeguard your SAP systems, SAST SUIT provides extensive testing in the context of security rules. SAST identifies significant configuration errors and incorrect values entered in your SAP system.
More from the category
- Security
