Token Policy User PIN Complexity
Originally Published: 2019-11-22
Last Modified: 2023-09-24
Article Number
000063764
Applies To
RSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.4.0
Platform: null
Platform (Other): null
O/S Version: null
Product Name: null
Product Description: null
Resolution
1) I am looking at the SecurID Token Policy for any complexity settings. Are there safeguards in place to keep a user from creating a simple pin like 11111 or 12345 ?
[SERGIO] You should create a password dictionary that contains words that cannot be used as passwords or PINs. After that, assign the password dictionary to the Token Policy. Please let me provide the steps:

1) Create a text file having all PIN Numbers that will not be accepted. For instance:

123456
654321
1111111
222222

2) Add the Password Dictionary to Authentication Manager Server.

In the Security Console, click Setup > System Settings > Under Authentication Settings, click Password Dictionary.

Note: AM Servers shows Password Dictionary but the dictionary can be applied for PIN Numbers as well.

3) Assign the Password Dictionary to the Token Policy.

Use the search fields to find the token policy that you want to edit > From the search results, click the token policy that you want to edit > From the context menu, click Edit > Under "SecurID PIN Format" select the dictionary from the Excluded Words Dictionary drop-down list.

 

Related Articles

Trending Articles

Don't see what you're looking for?