Security policies consist of three parts; password policy, lost period settings, and session limit.
Password policy
Password policies allow you to set restrictions on how weak or strong your users' passwords should be. They'll be applied to users who are allowed to use passwords to sign in, based on their routing policy. The following parameters can be configured in a password policy:
Password complexity
- Minimum length for a password
- Mixed password: When this parameter is enabled, users will be forced to set passwords with both uppercase and lowercase alphabets.
- Minimum special characters
- Minimum numbers
Password age
- Maximum password age: After setting a new password, users will be forced to change it after the number of days specified in this parameter.
- Minimum password age: After setting a new password, users will be restricted from changing it for the number of hours or days specified in this parameter.
- Refusal of previously used passwords: When setting a password, users will be restricted from reusing their recently used passwords. This parameter defines the number of recent passwords that will be refused.
Password policies also have three presets; Strong, Good, and Fair to help you quickly define your policies if you need to.
Lock period settings
Lock period settings restrict unauthorized access to an account. By enforcing a timed lock-out when there are multiple sign-in attempts with incorrect credentials, these settings protect against potential hacking. The following parameters can be configured under lock period settings:
- Monitoring period: This is the timeframe within which the number of invalid sign-ins shouldn't exceed the maximum limit.
- Maximum invalid sign-ins: This is the number of tolerated invalid sign-ins within the monitoring period.
- Lock period: This is the amount of time users will be locked out if they exceed the acceptable maximum invalid sign-ins per monitoring period.
Session limit - concurrent sessions
Concurrent session limit defines how many places you can be signed in simultaneously. Every time you sign in from a new browser, app, or device, it will be counted as a session.
For example, a user who's concurrent session limit is 3 will be able to sign in to a browser on their laptop, a browser on their mobile phone, and one on their work PC. If they try to sign in again from a different browser or device, they will be asked to sign out of their existing sessions first.
This increases user's security by reducing the amount of places their account is left signed in and unprotected.