Static password provisioning is used for Projects. For example, the Military often needs static passwords because of immediacy issues. During certain military projects, the provisioned users don't have time to look up a password. Because Static Password Provisioning is less secure than applying the Password Randomization Policy to all users, it is important to consider the type of project that the provisioned user is working on. If the project is new, then apply static passwords often, and make sure that the provisioned user doesn't have to change the password at logon! If the project is ongoing or mature, then you don't have to reapply static passwords as often. In addition, applying a static password requires the following:
- Users cannot change the password.
Password never expires.
Password Randomization vs. Static Password Provisioning
Password randomization and static password provisioning use opposing logic when dealing with passwords. Remember that the policy that runs last, wins!