This time I’d like to present a hot new SAP feature to you: Security Policies!
It is available starting from ERP 6.0 EHP6.
The system behavior regarding password rules and logon restrictions is controlled by profile parameters, e.g. “login/min_password_lng” for the minimum password length. These parameters are valid system-wide and could not be overridden by any means.
With the new security policies, it is now possible to define different sets of password rules, password change policies and logon restrictions and assign these policies to users.
This provides the flexibility to segregate users and assign an appropriate policy to each of those groups of users!
For instance, you can enforce strict rules on the global level (= profile parameters) and loosen them on user level via a security policy (e.g. increased validity period of unused initial password for users, who use SAP less frequently).
For users with a security policy assignment, the attributes defined therein
override replace the profile parameters – for users without a SecPol the parameters stay relevant.
The administration of security policies can be performed via the new tcode SECPOL, which is secured by two brand-new authorization objects: S_SECPOL is checked during the maintenance of the policies themselves, while S_SECPOL_A is used to define the values that may be assigned to the security policy attributes.
First of all, let’s create a new policy:
… then mark it and switch to the attribute maintenance screen by double-clicking on “Attributes”.
The following attributes are available:
|( none )
|Check the password blacklist
|Minimum number of digits
|Minimum password length
|Minimum number of letters
|Minimum number of lowercase letters
|Minimum number of special characters
|Minimum number of uppercase letters
|Minimum wait time for password change
|No. of different characters when changing
|Password change requirement for SSO logons
|Interval for regular password changes
|Password change after rule tightening
|Size of the password history
|Disable password logon
|( none )
|Disable ticket logon
|Maximum number of failed attempts
|Validity of unused initial passwords
|Validity of unused productive passwords
|Automatic expiration of password lock
The button “Effective…” shows the relation of the policy values to the default ones (=, ≠ or not set), while the “Superfluous Entries” button identifies unnecessary entries (i.e. identical to the default ones).
To assign the newly created security policy, just edit a user in SU01, switch to the “Logon Data” tab and enter the SecPol name in the “Security Policy” field:
Mass-assignments via SU10 are of course possible, too!
To be able to assign a SecPol, you’ll need the authorization object “S_SECPOL”, which behaves similar to S_USER_AGR – i.e. activity 22 (assign) and the policy’s name are checked.
If you want to select users by their security policy assignment, you can simply use the User Information System:
SUIM » User » by Logon Date and Password Change
Central user administration
The security policy ↔ user assignment is supported by the CUA and its distribution can be configured via SCUM as usual.
See you soon!