Advanced User Identification and Access Control For the Enterprise Market Utilizing Common Login Methods

The Autoload Password Manager With Policy Master Configuration Utility

Policy Master v2.2.0

The World’s First Password and Login Management System

Mand Ylion

I

Mandylion

researche» labs

www.mandylionlabs.com

Getting To Know The Autoload Platform

Features and Benefits

Tokens, Cradles & Configuration Software Cautionary Notes on Password Usage Using the Autoload Token

Initial Setup

System Requirements

Loading Policy Master Utility Software

Installing Configuration Cradles

Initializing Tokens

Control & Distribution of Configuration Software

The Policy Master Software Working with Templates EZ-Autoload Utility for End Users

Setting User Information Naming Templates Entering Individual or Class of User Information

Setting Enterprise Defaults & Locks Alarms and Lockout Policy Default Password Generation

Creating Login Records Identifying the System

Defining Password Policy

Defining Initial Settings

Downloading to the Autoload Token Downloading as an Administrator Downloading as an End User

Advanced Applications Associating Tokens with Templates Group Passwords

EZ-Autoload Utility for End Users

Token Behavior Matrix FAQ’s General Information & Technical Data

Warranty Information

11

13

13

14

17

19

23

24

34

35

Index

Passwords are the most common form of personal identification in use today. They have become an important part of the routine in our daily lives. We have come to accept this annoying and imperfect little form of identification. We intuitively assume passwords provide us with adequate security. The

experts know differently. Hackers just snicker.

Getting to Know the Autoload Platform

The Autoload Platform is the next generation of Mandylion’s password management token technology. The Platform consists of Autoload Tokens, Policy Master Configuration Cradles and

the Policy Master Configuration Software Suite.

The Token has been designed” from the ground up for the way we access and use password controlled applications. It does away with the inherent weaknesses associated with passwords; the reliance on the individual to create, remember and

regularly change them.

Truly an enterprise management tool, the autoload version allows organizations to configure and control the token on behalf of the organization’s users. The organization can set and control the enterprise logins and yet still allow the user to maintain their own personal logins on the token. Mixing official and personal logins provides a benefit to the organization; It promotes a culture of

security over password use.

* Designed in conformity with U.S. Military, National Institute of Standards and Technology and National Security Agency standards for the secure creation, management and use of passwords. All units comply with DoD information security guidelines D8500.1 and D8500.2; US Army Regulation 251A; FIPS Pub. Nos. 112,190 and 196 and NIST Special Publication 800-63 titled Electronic Authentication Guideline. (9/04); NSA and Committee on National Security Systems (CNSSS) National Security Telecommunications and Information Security Systems Policy No. 11 (NSTISSP #11).

Features & Benefits

Securely Stores up to 50 passwords. Along with account numbers and website / application names.

Generates Strong Passwords. Patent pending kinetic circuitry actually senses your use of the unit. This aids the unit’s processor in the generation of strong passwords which thwart all known password cracking techniques including dictionary and brute force approaches. Passwords can be any length up to 14 characters or namespaces.

Preconfigurable. Can be configured by the organization on behalf of the user. Handles incremental updates as well as group passwords. The enterprise can control what the user can modify on the token.

Its Automatic. Prompts you to change your passwords at preset intervals, then can automatically create a new one for you.

Tamper Resistant. Only the authorized user it 1s assigned to can turn it on. Circuitry is designed to thwart electronic bypass. Unit has user selectable lockout settings including a self destruct function.

No Software needed. Nothing to Install. Simple read out can be instantly used with any Web site or system.

Carefree Operation. Uses standard batteries. Batteries last about a year with daily use. All passwords and settings are stored in permanent and protected memory which is unaffected by battery life or loss of power.

Configuration Utility and Cradle. The autoload version of the token can be configured either manually on the token itself or via the Policy Master Configuration Utility and downloaded to the token.

Operation is Simple and Intuitive. You can use it to add convenience while improving your security anywhere you use passwords, PINs or pass codes.

Getting to Know the Autoload Platform

(continued)

Ease of Use

To use the token with your logins, you simply follow three easy steps:

e Access the password input area or screen of the Web site or system you wish to gain access to.

e Activate your token and display the stored password or memory aid to arrive at the password that you created for that site.

e Enter the password in the input area of the Web site or system as you normally would ..and you are in!

Using the token instantly provides you with a quantum leap in security protection.

" For an even greater defense-in-depth security over your passwords, use the device as a memory aid to recall your actual passwords. A simple offset technique can apply something only you uniquely know to the characters displayed, to arrive at the actual password. Under this method, the passwords are never stored within the token. The device functions as a memory aid to arrive at the correct password. See FAQ’s for detail on the technique.

Cautionary Notes on Password Usage.

According to the annual FBI “TOP 20 LIST”, humanly generated, easily crackable passwords are the greatest vulnerability associated with today’s password usage.

In environments where users are either uncomfortable or further, prohibited from writing down or electronically storing their passcodes, the token may be used as a memory aid for the management and recall of strong passwords.

To use the token in this mode, the principle of offsets is used. Rather than the token displaying and storing the actual password for a Login Record, a simple offset technique can apply something only you uniquely know to the characters displayed, to arrive at the actual password. This way the password is never stored. If the token contents were somehow revealed, they would still be unusable.

The lockout features and tampered alarms of the token, although strong, are merely deterrents to wrongful access and compromise of the device. They are part of the device's "defense in depth" strategy. When combined with the other features, controls and recommended use and possession of the device, they create a formidable barrier to wrongful access of the device.

It is always theoretically possible to defeat a singular security control, such as lockout, given enough time and persistence. Accordingly, relying on a single security feature in isolation of these other controls is not recommended. In high risk environments, Mandylion strongly recommends that users keep their tokens in their possession, remain vigilant as to possible signs of tampering and utilize the token as a memory aide (see FAQ’s)

' SANS “TOP 20 LIST”, The Twenty Most Critical Internet Security Vulnerabilities at http://files.sans.org/top20.pdf

Getting to Know the Autoload Platform

(continued)

Two Ways to Enter Login Record Data

On the Token Directly. Utilizing only the token’s keypad, a user can enter or generate either automatic or custom configured passwords as well as enter identifying names and account numbers to complete their Login Record.

Download via Computer. Utilizing the Policy Master Configuration Utility, login records as well as enterprise controls over the token’s use can be easily entered onto a single or multiple tokens.

About the Display...

The Display has Three Information Areas

Main Display Area

WEREott ST

Password

Name ; Account; or Password Icons light to indicate the current display in Main Display Area

Mode/ Indicator Lamps: Edit Mode; Option Mode & Low Battery Indicator

6 Using the Autoload Token

Presented below is a simple overview of the Autoload token. For full details on the use and manual configuration of the token, please see the separate manual titled the Autoload User Guide.

...and the Manual User Interface

Only 5 Keys Control the Entire Unit:

Four Directional Arrows surrounding a center Enter/Select Key.

Scrolls up through menu selections or through character sets during data input

Up Arrow Key (@)Enter/Select(Center) Key

Confirms menu selection /entry input

(<q) Left Arrow Exits any function or scrolls cursor left

Right Arrow ( p) Scrolls cursor Right

Down Arrow (V) Scrolls down through menu selections or through character sets during data input

Note: The above symbols are used throughout this guide to represent the keys. The VA symbol indicates pressing the up and down arrow keys simultaneously. (Only used to switch between View, Edit and Options Modes.)

System Requirements:

To install and operate the Mandylion Policy Master Utility Software for the Autoload token, the system must meet the following requirements:

e Win7, VISTA, Windows XP, 2000, NT, 98, 95 Operating System;

e Wintel Pentium hardware platform;

e 10 MB available hard disk space;

e VGA monitor with 1024x 768 minimum

resolution;

e CD-ROM drive;

e Mouse;

e USB port;

e Mandylion Policy Master Token Cradle; and

e Mandylion Autoload Token.

7 Initial Setup

Loading Policy Master Utility Software Suite

Policy Master Utility Software is a self configuring application consisting of following files on the Disk:

Mandylion

researche» labs

Run Setup.exe before plugging in cradle

Policy Master Configuration Utility Application (Setup.exe) v2.1.0 Policy Master Configuration Utility Manual v2.1.0

Quickstart Guide v2.1.0 Drivers - umpf3410.151 & umpf3410.i51

Policy Master Installation CD:

Contains:

° Policy Master Application (Setup.exe)

° Policy Master Configuration Utility Manual ° Token Manual

° Token Quickstart Guide

Installing the Policy Master Program

Double click on the Setup.exe icon and follow the

instruction steps. (important: run setup.exe before plugging in cradle)

A welcome message will appear:

compete En story secomenencted that pou eet al Windows pogani tokre rere Pro Seto Popas

Oh Coel o at Seto ad clove aw woga you have amg Cii Next te contre eth the Setup pogan

WARNING Tihe pogam i protected by copgngt? haw and Flee aad Bere)

Ord wel be Peccecided to he mamare totter’ positie Lees a

e Click “Next”

Choose Destination Location (default is program files):

Setup wall metal M arveon Reteach Late Poty Meila m the tolloweng folder

To ratal rio a Gtererd kida chch liome, ard :aieci wota lase

You Can hae not to ental Marcion Reseach Labi Pokey Marier by chchung Cancel to mat Setup

e Click “Next”

Choose Program Grp (default is Policy Master):

e Click “Next”

8

Installing the Policy Master Program (con’t)

The start installation message will appear:

You ae new teady o metal Mardhor Pereach Labe Pobcy

Prec: the Miet Sutter to begin the inetallaton or the Ñ aci Detour bo eerie Pe retalston riarann

e Click “Next”

A Progress Bar will indicate installation progress:

C Ea CA Foley MestenLock oi SEEGER RRRSESRRRREREE

Aa f tes Tma PRieesareng © rarata: Ù seconds

When installation is complete:

Marcher Riereach Labe Pokey Master hat been succet ihuly re aded

Presi Pe Fred buon 00 ea Pre metabatery

e Click “Finish”

The Policy Master Setup.exe creates the following files and folders and deposits them into a newly created directory C:\ Program Files\ Policy Master.

Note: If you are upgrading from a previous version of Policy Master (which is required for the desktop personal cradle) your “accounts” folder and its contents will remain but all other files will be replaced.

To completely deinstall the Policy Master application and remove it from your computer, click the “UNWISE” application in the Policy Master Folder. This deinstall process will preserve any accounts that had been set up in the accounts folder but remove all other files.

Questions or help with the installation process can be obtained via the mandylionlabs.com web site or by calling Mandylion directly from the contact numbers on the web site.

9 Installing the Configuration Cradle

Once the Policy Master Program has been installed, the desktop personal cradle can be plugged into any available USB port to commence its installation.

The cradle is a serial device that communicates through the USB port. It requires two drivers to be installed via the Windows Operating System “Hardware Wizard”.

Plug the cradle into any available USB port and the following hardware windows will appear in sequence:

The Windows New Hardware Wizard will then automatically install the necessary drivers.

When complete, the New Hardware Wizard will provide a notice that the device is ready for use.

The Installation of the Configuration Cradle is now Complete.

Initializing Tokens

Tokens are licensed for use in conjunction with the Policy Master Software license. Each token must be initialized by the Policy Master software prior to its first use.

Initialization is a one time, one step process. It is performed by placing a new token in the configuration cradle and running the initialization utility which comes with the Policy Master configuration software.

Mandylion Token Initializer |7

This utility invokes the DESTROY command and completely resets the token to its default state.

NOTE: All data that may have been contained in the token is irretrievably erased and destroyed with

this initialization process. Additionally, this process embeds the serial number of the Policy.

Mandylion Token Initializer

Initializing Token...

Mandylion Token Initializer [X]

l ) The token should now be initialized

10 Initial Setup

(continued)

Control and Distribution of Configuration Software

The Policy Master Software license allows the token to be configured by that software.

NOTE IF YOU ARE UPGRADING FROM A PREVIOUSLY INSTALLED VERSION OF POLICY MASTER USE YOUR OLD LICENSE NUMBER OR THE SOFTWARE WILL NOT RECOGNIZE YOUR TOKENS.

NOTE FOR ENTERPRISE USERS

The Policy Master Configuration software suite provides the enterprise with a great degree of control and authority over each token that is licensed to it. Except for the Policy Master Public Utility which can be freely distributed due to its limited configuration capabilities, the entire Policy Master Configuration software suite should be controlled by the enterprise and only provided to enterprise personnel assigned to the configuration and support of end users.

If control among token administrators is sought by the enterprise, the Policy Master software has a unique ability to associate and control specific tokens by administrator or group administrators. See the Advanced Applications section of the manual on association and group association of tokens.

11

The Policy Master Configuration Software Working with Templates

The Policy Master Configuration Software is a template based application. It provides a great deal of “cut and paste” flexibility in creating login records for a single token or multiple tokens for whole classes of users. (See Advanced Applications) The basic Policy Master Template screen is shown below. This is the default file which appears on the screen when the application is launched. The template is divided into three logical areas; user information input area; selection of default parameters to the device including locks, alarms and default password generation; Login Record Area .

User Information Input Default Parameters

Individual Login Record

n Policy Mesto

otud V ecowod Lew stor

$$$ —___—__—_

Sverre hooo

ndylion earekberiatbs

Default

Hrews [se Daye

Olea

Alpa Change on | ober

Inthal Settings Support

Account $. User ID Duplay and

o Soren Nowe Scheme r P Sve pirt

- a [pi @ | poa giens) |f na a [ras se a] | a < = u | poco - Cc te ej = Token - Vis 8 - | =| ~ a a | pooooox - [s 7 lore Teken fi agp- -l | =] si . 8 | þoooooo zj [x0 Des}! | fon Teren =} [vse Betsey =) | x ° à a |a a o) |era a) fran saar =] [= P s @ | a e a [nna r d [oe a â | conc ej [30 Des}! | Jom Toren =) [via 3 -j | zj ~ E ~ f KAIKA - [3 Ds - lon Token - a Bolicy - | =| 2 - à |p a foc tes}! | fon teens] [rua serer a) [a] - =) ke) | Se a

= | - ‘Sewer > lon Token -j [via Policy - | J

" <j e | Ge Taken <) [Wie Bentey ~) | zj

" D e e a e a ~) a E)

a D e) e) | teen) r ~) (|

ü | =) [ewes ~) Toren >) s ~) | z]

a DO ) e | teen) a ~) N E)

- M Se} |) a [SN

a =) E U e a -) (_-)

- M ANO | xe) a

. =) | a) Scam) Game =)

Policy Descriptions for Login

Initial Settings For Login

Systems Definition for Login

Record Selector for Download

The Login Record Area scrolls to display entry for all 50 login records. Each Login record 1s divided into three sections; System Definitions; Policy Description; Initial Settings. Lock icons allow the administrator to enable/disable the ability of the user to change a particular field on the token. Record Selector indicates which records are to be updated/downloaded to token on an incremental or full update/download.

EZ-AutoLoad Utility for End Users

12

The Mandylion autoload token contains capacity for up to 50 simultaneous login records. In most instances, this capacity is more than adequate to accommodate all of the average user’s corporate logins as well as the user’s personal logins. To promote a culture of security within their organization as well as reinforce familiarity with the operational use of the token, the enterprise and corporate administrators should encourage their users to use this excess capacity for their personal logins.

+. Mandylion Policy Masir

Mandylion

'r¢~s.@2€8re¢s ©* ia 8-5

Public

Syulmen Policy

Logn Neoord Hres

Paazmard Scheme

lenk J0

Bank 33 Penk 40 kent 43 Penk 62 [Blank LE Iblant 44 Bleni 46 [blana 44 Blana 47 Ilana st Bleni 49

Blana $0

4 4 t

$ i $ 4 1 4 $ 4 4 4

i Ed

To that end, the Policy Master Configuration Software includes a utility which can be provided to token users for the configuration of their own personal password records. This utility is known as Policy Master Public. It is a small executable which contains only a subset of the features and configuration capabilities of the main Policy Master template. This utility is designed to be loaded either on an end user computer, or alternatively, in a kiosk type environment.

Please Note: Enabling user access to configure or change login records is strictly an enterprise policy decision. As discussed in the previous section, if an organization does not wish their users to utilize the token except for the enterprise’s login records, the token can be set administratively to lock off the user from any “on token” or “on cradle” configuration privileges.

For details on the features and use of the Policy Master Public utility, see section “Advanced Applications.”

Setting User Information Naming Templates

The Policy Master Configuration template can be saved for an individual user or generated and saved for a group of users which share similar access privileges. To name a template and save it in the “accounts folder”, select from the Account Menu “save” or “save as”. Flexibility is provided for administrators to be able to create and save templates in accordance with their organizations needs. All Policy Master Configuration templates carry an “ebp” windows file extension.

Entering Individual or Class of User Information

The User Information Input area contains 6 fields of static information which helps identify a particular template and associate it with a particular individual or group of individuals. Entry of data into these fields is strictly optional on the part of the administrator. No user data contained in this area is downloaded to the token.

The form allows the administrator to enter Roles, the users name and Title, supervisor information as well as security officer points of contact, if any, assigned to that individual or group of individuals. An overrideable system field records and keeps the initial creation date of the form.

13 Setting Enterprise Defaults and

Locks Alarms and Lockout Policy

The autoload token possesses several tamper alarms, lockouts and limits on failed login attempts. These alarms and lockout policy can be set and controlled by the administrator and/or the user. The logical and physical controls over access to the token form a defense in depth approach to controlling the authorized use of the token.

Lock Outs

Attempts

3 tries Y se a

Shutout ' Sleep

Allow Change on Token: P

Locks can be set for the number of failed attempts to gain access (1, 3 5 or 10 tries) as well as the sanction if those limits are exceeded (various time lockouts through complete overwrite, destruction of entered data and lock of the token). Administrators can enable/disable the ability of the user to change the lockout parameters on the token.

Default Password Generation

For convenience, each autoload token has a default password schema and renewal parameters which is utilized when a specific password policy is not defined for a particular login record. Administrators set the default password generation parameters on the template and can enable/disable the ability of the user to change these parameters on the token.

Default Password Generation

Schema: [XXXXXXXX

Renewal | Never v |

Allow Change on Token: W

system

Policy

Creating Login Records

Initial Settings Support

Record Login Record Account #, User ID Initial Initial Display and Tech Support Number | Name or Screen Name Schema Renewal Password Renewal Save Options | Telephone # 1: Iv [Blank 1 a [Empty a | -| [Nevez -| a [on Token -| [one Time -| | [Na =

Identifying the System

To identify a particular login record, the template provides three downloadable input fields. Each is 14 characters in length. The first field describes the Login Record’s name (i.e. email, or VPN etc); the second field is available to enter an account number, screen name or user ID associated with the login record and finally, there is a field to enter technical or help desk telephone numbers associated with the login.

Administrators set the system definitions for each login record and can enable/disable the ability of the user to change these identifiers on the token.

Defining Password Policy

For purposes of the template, password policy is defined as the schema or composition of the password required by the login and its renewal.

User passwords can be specified by length, composition and renewal interval. Composition or schema of each password can be specified down to the keyspace (position) within the passcode to be generated. Composition can be randomly drawn from the entire printable ASCII character set (base 94) or throttled to any or a combination of the following subsets of the printable ASCII character Set:

e Upper Case Letters (base 26)

e Lower Case Letters (base 26)

e Upper and Lower Case Letters (base52)

e Numbers (base 10)

e Special Characters (base 31)

e Any but Special Characters (base 63)

e National Character Set (#;$,@)

e Upper Case Alpha and Numbers (base 36)

The following options can be enabled or disabled by the Administrator in the creation of a password’s composition, by login record:

e Minimum length; Maximum length;

e Password to be totally random; i.e. cannot contain the username or word;

e Can specify minimum representation of each ASCII character set;

e Password must contain a configurable number of numeric characters;

e Password must contain a special character (from a customizable list);

e Password must contain at least one lowercase character;

e Password must contain at least one uppercase character;

e Password cannot be set to a previously used password ;

e Password cannot contain any variation of the users name;

e Password cannot can not be a dictionary word.

Password schema is created by making a selection from the pull down menu in the “Schema” column of the Policy section. Selections are Default, Structured, Randomized and Manual.

Schema Renewal

| ~] [Nevez v|

EES Zt

Selecting the Structured Option in the pull down menu displays a preference box which allows the administrator to set the token to generate a purely random password of a specific length for that specific login record.

tnter 4) a

Piopio enisi à how scheme

LI - Uppe Laie Ga | o [ae Cpe A -Lipa of Lowest Leese Abie N - Hura: , -Spec Lipis D. Nora Oaai Set Ary Dus peaosi Livre Ary Vrrtabbe lew acter ~~ Upper Las Abhag Met

chena |

_ œ% | _ Cmo |

With this option, the device’s random number generator can be further throttled to only generate specific subsets of the ASCII character set in each position within a particular password. This feature allows for the creation of passwords that fit the schema requirements of applications/hosts which might require, for instance, only an alphanumeric in the first position of the password.

15 Creating Login Records

(continued)

Selecting the Randomize Option in the pull down menu displays a Preference Box that sets the token to generate a purely random password of a random length within a specified minimum and maximum length range for the login record selected. This option also allows the administrator to set the minimum and maximum count of characters within the password from specific subsets of the ASCII character set.

Laer ate Mew Shema

Nondomred Mast Mreterenoes

U -Lpp Lanm Abe

L- Lower Caos Aipha Unoer o Lower (ane Aipha Murba

5: Speca Cheeco N otorva Cha acter Set

. Ary Bu Spena Chasde

\ Ary Pridi Osca Uppe Lave åta o Number

Mack Urean | cones

10} 0

Mrena Schemes Langh

Mamam Sewa Lerga

Unlike the Structured Option, this option calls on the powerful random number generators to select the position within the password of where these specific character sets will fall.

Selecting Manual in the pull down menu displays a Preference Box which allows for entry of a manual or previously generated password. A manual password may also be entered into any record as its password of record or as an initial bootstrap, one time password.

tnter Password

This latter feature allows for the input of host generated passwords or group passwords and their coordination among users.

Expiration/Renewal Periods

Password expiration intervals can be set and controlled by login record via the pull down menu in the “Renewal” column of the Policy section:

Policy

Schema Renewal

16 Creating Login Records (continued)

Intervals included in the standard configuration are:

e Upon First Use

e 30 Days e 45 Days e 60 Days e 90 Days e 180 Days

e One Year e Two Years e Never

Mandylion autoload token allows for a “grace period” for password change to accommodate synchronization with other logins and applications as well as to temporarily delay password updates to a more convenient time to the user.

Defining Initial Settings

The Policy Master Configuration software has the ability to not only set the parameters for the ongoing password for each login record but can also control and accommodate the definition of the “bootstrap” or “Expire on First Login” policy for that record.

The administrator has the option of setting the Expire On First Login password to expire upon first use and automatically generate a new password for the user that complies with ongoing policy. Alternatively, the Expire On First Login password can be delayed to first policy change date or held static, as in the case of group or manual password login records.

Individual passwords can be set to be generated by the device or securely loaded via the cradle from the individual template by login record. This latter feature allows for the input of host generated passwords or group passwords and their coordination among users.

Once a template has been defined for a particular user or class of users, it can be downloaded to an Autoload token. Downloading is accomplished via a Policy Master Configuration Cradle.

To download to a token, select from the Account Menu either “Save and Download to Token” or “Download to Token Only” (not an available option with group or associated templates See Advanced Applications).

= Mandylion Policy Master Weera Options Assodate

Open... Save

Save As...

Save And Download To Token Download To Token Only Clear

Exit

17 Downloading to the Token

The download process is quick and the average token can be configured in less than 10 seconds.

PolicyMaster

Downloading to Token...

| Record{02}: System Name

Cancel

Flexibility is provided for administrators to be able to create and save templates in accordance with their organizations needs and download to the tokens as needed.

Tokens can be configured by administrators prior to their initialization by the end user.

When provisioned with a token, all the user has to do is create their own fingerpattern for access and they are done! This constitutes the initialization process by the user.

Unused login records can be set by the administrator to allow for the user’s personal use. Alternatively, a user can configure their own token from their own PC or a shared “kiosk” type station without the assistance of an administrator. (See EZ-AutoLoad Utility for End Users See Advanced Applications)

Due to a unique lockout control, Login records set by the enterprise cannot be reconfigured or erased by the user. Login records set by the user can be overwritten by the enterprise, however, they cannot accessed by the enterprise.

On the back of the autoload token there are 4 ports which connect the token with the “pogo pins” on the face of the Policy Master Configuration Cradle.

From a security design perspective, no bilateral communication occurs between the token, the Policy Master cradle and the Policy Master Software in the download process.

All downloads constitute “unidirectional writes” of data streams which are either accepted or rejected by the token based upon the criteria established in the token. As a safeguard, the Policy Master configuration software and templates cannot interrogate a token for its contents or state. If an administrator is unsure as to a token’s origin, the administrator’s only option is to DESTROY, reset and reinitialize the token. (See Initializing Tokens)

Proper Placement of Token on Cradle

The token should just “snap” into the cradle and make direct contact with the “pogo pins” on the cradle. A specially designed channel at the bottom of the cradle allows the token to be placed on the cradle while on a keyring.

18 Downloading to the Token

(continued)

If properly positioned on a plugged in cradle, the token LCD will remain blank or display what the token normally displays off the cradle ( “Enter Code” or New Code or View, etc.) Only when downloading will the token read “Ready” indicating that the token has been properly mounted and is ready for downloading and is receiving a download.

If you do not see “Ready” on the token’s LCD while in the actual act of downloading to the token, attempt the mounting process again to ensure the ports on the token are aligned over the “pogo pins” on the cradle.

If the token is still not in “Ready” mode, make sure that the cradle is plugged into the USB port of your computer and that the token is operative. Taken off the cradle, a properly operating token will read either “New Code?” or “Enter Code” on the LCD when the enter (center) button is depressed.

The Policy Master Configuration software suite provides the enterprise with a great degree of control and authority over each token that is licensed to it. Except for the Policy Master Public Utility which can be freely distributed due to its limited configuration capabilities, the entire Policy Master Configuration software suite should be controlled by the enterprise and only provided to enterprise personnel assigned to the configuration and support of end users.

In certain environments, token administrators may wish to associate a specific Policy Master template that they have created with a particular token or class of tokens.

This association is a “hard” physical association. It binds the Policy Master Template created with the token(s) it has been downloaded to. It differs from naming and saving a “default” Policy Master Template file in the name of an individual, class of user, etc. (See Policy Master Configuration Software Working with Templates) in that once a token and particular template have been associated, only that unique template file will be able make changes and add login records to the associated token(s).

A token can be associated with only one Policy Master Template at a time. Association, however, does not preclude group records from being added or changed to unassigned login records. Further, association does not preclude the end user from adding and changing their own personal logins to previously unassigned records, 1f that permission had been granted to them by the administrator.

Note: Association of tokens is an advanced application and is not recommended for routine token use.

The advantage of this association is strictly administrative in nature only. It does not necessarily enhance the security of the underlying token’s use and can actually increase the complexity of token administration. This association merely precludes an overwrite of any of the corporate logins that have

Advanced Applications

Associating Tokens with Templates

by another properly licensed Policy Master Template. A token can be associated with only one Template at a time. Once an association 1s made, it cannot be reversed. If a token’s alarms/sanctions are activated and the DESTROY function invoked, the token’s contents and settings will be erased, however, it will still remain associated with that particular template. If an association is no longer desired or needed, the only way to reset the token is to re-initialize it using the Initialize Utility. This action will not only terminate the association that had been established, it will also DESTROY the contents of the token. The token will be reset to its factory defaults.

To associate a particular Policy Master Template with a token, select from the “Associate” menu on any Policy Master Template the “Individual Form with Specific Token” option. This association can be initiated at any time in the creation of the Template.

ie ror vn pec To Mawuyrrvn

Peg r pe Bb ] ad's

Token Association Pending

Once an association is made, the status in the header area will change to Associated (pending) and the header information of the Template will change color indicating that you are now working with an associated form. Further, the Associate menu will no longer be operative and indicate, via a check mark, that the Template association has been selected. As a safeguard to keep the associated form in sync with the corresponding token, the “download only” menu choice is disabled from the Account pull down menu and download and save is now the only download option.

Inputting login record parameters into an associated template is identical to the default Policy Master Template. (See Policy Master Configuration Software-Working with Templates).

Once an associated Template has been downloaded and bound to a token, its status in the header area will

change from “Associated Pending” to “Associated”. The act of just creating and saving an associated Template without performing a download does not bind the Template with a token. According, the final status indication of “Associated” only appears upon a download to a token.

= Mandylion Policy Master - C:\Program Files\Poli Account Options Assocate

Mandylion

labs

researche»

Associated

Group Passwords

The Policy Master Configuration software suite provides for the efficient and secure administration of group passwords. Group passwords typically occur in multi-server 24/7 uptime environments where a trusted core of administrators are required share root login access. Physical Cipher locks to doors and safe combinations are also considered group passwords. In addition to the access code itself, group passwords may or may not share identical user ID/screen names.

The Policy Master Configuration software suite manages all variations of group passwords and offers a secure method to create disseminate and renew group passwords.

Similar to associating a token with a Template, assigning a