DIGIPASS Authentication for Juniper ScreenOS

Disclaimer Disclaimer of Warranties and Limitations of Liabilities This Report is provided on an 'as is' basis, without any other warranties, or conditions. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of VASCO Data Security. Trademarks DIGIPASS & VACMAN are registered trademarks of VASCO Data Security. All trademarks or trade names are the property of their respective owners. VASCO reserves the right to make changes to specifications at any time and without notice. The information furnished by VASCO in this document is believed to be accurate and reliable. However, VASCO may not be held liable for its use, nor for infringement of patents or other rights of third parties resulting from its use. Copyright 2007 VASCO Data Security. All rights reserved. 2007 VASCO Data Security. All rights reserved. Page 2 of 53

Table of Contents DIGIPASS Authentication for Juniper ScreenOS... 1 Disclaimer... 2 Table of Contents... 3 1 Overview... 6 2 Problem Description... 6 3 Solution... 6 4 Technical Concept... 7 4.1 General overview... 7 4.2 Juniper ScreenOS prerequisites... 7 4.3 VACMAN Middleware Prerequisites... 7 5 Juniper ScreenOS... 8 5.1 Authentication server... 8 5.2 IP Pool...11 5.3 Local user...13 5.4 Local Group...15 5.5 XAuth Settings...16 5.6 VPN Gateway...17 5.7 VPN AutoKey IKE...21 5.8 Policy configuration...23 6 Juniper-Remote... 27 6.1 New connection...27 6.2 My Identity...29 6.3 Security Policy...31 7 VACMAN Middleware... 33 7.1 Policy configuration...33 7.2 Component configuration...35 2007 VASCO Data Security. All rights reserved. Page 3 of 53

8 User configuration... 36 8.1 ODBC installation...36 8.1.1 User creation...36 8.1.2 Import DIGIPASS...38 8.1.3 DIGIPASS Assignment...40 8.2 Active Directory installation...42 8.2.1 User creation...42 8.2.2 Import DIGIPASS...44 8.2.3 DIGIPASS assignment...46 9 Juniper-Remote test... 48 10 VACMAN Middleware features... 49 10.1 Installation...49 10.1.1 Support for Windows 2000, 2003, IIS5 and IIS6...49 10.1.2 Support for ODBC databases and Active Directory...49 10.2 Deployment...49 10.2.1 Dynamic User Registration (DUR)...49 10.2.2 Autolearn Passwords...49 10.2.3 Stored Password Proxy...49 10.2.4 Authentication Methods...49 10.2.5 Policies...50 10.2.6 DIGIPASS Self Assign...50 10.2.7 DIGIPASS Auto Assign...50 10.2.8 Grace Period...50 10.2.9 Virtual DIGIPASS...50 10.3 Administration...51 10.3.1 Active Directory Users and Computers Extensions...51 10.3.2 Administration MMC Interface...51 10.3.3 User Self Management Web Site...52 10.3.4 Delegated administration...52 2007 VASCO Data Security. All rights reserved. Page 4 of 53

POWER STATUS ALARM HA POWER RESET CONFIG TX/RX 0/0 LINK TX/RX 0/1 LINK TX/RX 0/2 LINK TX/RX 0/3 LINK 10/100/1000 CONSOLE AUX USB 0 1 SLOT NUMBER 1 2 3 4 5 6 SSG 520 1 Overview The purpose of this document is to demonstrate how to configure VACMAN Middleware 3.0 (VM3.0) to work with Juniper ScreenOS (ScreenOS) based devices. ScreenOS is an operating system created by Juniper that operates on most of their firewall and IPSec/VPN devices. 2 Problem Description The basic working of ScreenOS is based on authentication to an existing media (LDAP, Radius, local authentication ). To use the VACMAN Middleware with ScreenOS, the XAuth settings need to be changed or added manually. 3 Solution After configuring VACMAN Middleware and ScreenOS in the right way, you eliminate the weakest link in any security infrastructure the use of static passwords that are easily stolen guessed, reused or shared. In this integration guide we will make use of a Juniper SSG-520. This device combines a firewall, an IPSec/VPN and a UTM device in one. For authentication, we focused on the IPSec/VPN part. The same authentication methods can be used in other modules of the Juniper ScreenOS, such as firewall authentication to secure parts of the network. VACMAN Middleware IP:10.0.2.10 Port: 1812 Shared Secret: vasco Juniper SSG-520 Untrusted IP: 10.0.1.1 Trusted IP: 10.0.2.151 10.0.1.0/24 10.0.2.0/24 (Both run on the same server) Domain Controller DNS server Active Directory Domain: labs.vasco.com IP: 10.0.2.10 Figure 1: Solution The network schema you see above does not represent a real-life situation. We only display a lab environment. The untrusted IP range (10.0.1.0/24) represents an external network. 2007 VASCO Data Security. All rights reserved. Page 6 of 53

4 Technical Concept 4.1 General overview The main goal of the ScreenOS is to perform authentication to secure all kind of VPN and firewall connections. As the ScreenOS can perform authentication to an external service using the RADIUS protocol, we will place the VACMAN Middleware as back-end service, to secure the authentication with our proven VACMAN Middleware software. 4.2 Juniper ScreenOS prerequisites Please make sure you have a working setup of a device running ScreenOS. It is very important this is working correctly before you start implementing the authentication to the VM3.0. At this time this is a list of devices that run Juniper ScreenOS: NetScreen - Hardware Security Client NetScreen - 5GT NetScreen - 5GT ADSL NetScreen - 5GT Wireless SSG 5 SSG 5 Wireless SSG 20 SSG 20 Wireless SSG 140 SSG 320M SSG 350M SSG 520M SSG 550M ISG 1000 ISG 2000 NetScreen - 5200 NetScreen - 5400 The screenshots used in the rest of this document, are taken from ScreenOS version 5.4.0. Other ScreenOS versions or different devices could give you a little different screen layout or naming of objects, but the general idea behind it is always the same. 4.3 VACMAN Middleware Prerequisites In this guide we assume you already have VACMAN Middleware 3.0 (VM3.0) installed and working. If this is not the case, make sure you get VM working before installing any other features. 2007 VASCO Data Security. All rights reserved. Page 7 of 53

5 Juniper ScreenOS For the ScreenOS setup we suppose the device has been already setup. The steps below help you to make the necessary changes to make use of VACMAN Middleware to perform your authentication with a DIGIPASS. On the other hand, these steps can also be used to setup the device from scratch, only the basic setup of the device has not been taken into account in this manual. 5.1 Authentication server First thing to do is to add the authentication server that points to the VM3.0. Select Configuration Auth Servers from the menu and click the New button in the upper right corner of this window. 2007 VASCO Data Security. All rights reserved. Page 8 of 53

Fill in/set the following fields: (according to your setup) Name: VACMAN Middleware IP/Domain Name: 10.0.2.10 Backup 1: fill in if applicable Backup 2: fill in if applicable Account type: XAuth Source Interface: ethernet0/2 (must be your trusted interface) Select the RADIUS option o RADIUS Port: 1812 (default in VM3.0) o Shared Secret: vasco (set in VM3.0) Scroll down the page and select OK. The Account type can be more than XAuth alone. We only need XAuth for the IPSec VPN connection. This is a list of possibilities: Auth firewall authentication L2TP L2TP VPN authentication Admin authentication for the administrative logon (can t be combined) XAuth IPSec VPN authentication 802.1X wireless authentication 2007 VASCO Data Security. All rights reserved. Page 9 of 53

5.2 IP Pool Next we need to configure an IP Pool that will assign a range of IP addresses to the VPN clients. Select Objects IP Pools, and click the New button in the upper right corner of the screen. Give the IP Pool a meaningful name and enter the start and end IP. Click OK to save the IP Pool. 2007 VASCO Data Security. All rights reserved. Page 11 of 53

5.3 Local user The next step is to create a local user. This local user will allow us to setup an encrypted tunnel from the client to the server over which the username and OTP will be sent to the VM3.0. Select Objects Users Local and click the New button in the upper right corner. 2007 VASCO Data Security. All rights reserved. Page 13 of 53

Fill in/set the following fields: (according to your setup) User Name VascoXAuth Status: Enable Select IKE User Number of multiple logons : 99 Select Simple Identity o IKE Type: AUTO o IKE Identity: xauth@labs.vasco.com Select XAuth User User Password vascopass Confirm Password vascopass 2007 VASCO Data Security. All rights reserved. Page 14 of 53

5.4 Local Group To let everybody use this user to set up an encrypted tunnel, it is necessary to add this user to a group. Select Object Users Local Groups and click the New button in the upper right corner. Give a meaningful Group Name and select the user you just created before and click the << button to add the user to the group. Click OK to save your changes. 2007 VASCO Data Security. All rights reserved. Page 15 of 53

5.5 XAuth Settings The following things we need to configure are the default XAuth settings for the VPN settings. Select VPNs AutoKey Advanced XAuth Settings. Select the authentication server we created before as well as the IP Pool. You will have the ability to configure the DNS and WINS server IPs for the client connections. Click Apply when finished. 2007 VASCO Data Security. All rights reserved. Page 16 of 53

5.6 VPN Gateway We will now configure the VPN gateway, this gateway will be responsible to create the encrypted tunnel over which we will send our credentials to VM3.0. Select VPNs AutoKey Advanced Gateway and click the New button in the upper right corner. 2007 VASCO Data Security. All rights reserved. Page 17 of 53

Fill in/set the following fields: (according to your setup) Gateway Name: VascoGateway Security Level: Custom Remote Gateway Type o Dialup User Group: VascoGroup Preshared Key: vasco123 Outgoing Interface: ethernet0/0 (must be your untrusted interface) When this is done, click the Advanced button. 2007 VASCO Data Security. All rights reserved. Page 18 of 53

Set the fields like this: (according to your setup) Security Level o User Defined: Custom Phase 1 Proposal o pre-g2-des-md5 o pre-g2-des-sha o pre-g2-3des-md5 o pre-g2-3des-sha Enable NAT-Traversal checked At the bottom of this page click the Return button and in the Gateway screen, click the OK button. You will then receive a warning message stating that your dial-up group is now configured, but you will need to enable XAUTH as well. Click OK. 2007 VASCO Data Security. All rights reserved. Page 19 of 53

In the gateway list, click the Xauth link behind the gateway you just created. Select XAuth Server and select the Use Default Xauth Settings option. The Allowed Authentication Type is Generic. Click OK to save your changes and go back to the gateway list. 2007 VASCO Data Security. All rights reserved. Page 20 of 53

5.7 VPN AutoKey IKE Now our gateway is setup we still need to create a VPN tunnel that points to our gateway. Select VPNs AutoKey IKE and click the New button in the upper right corner. Fill in/set the following fields: (according to your setup) VPN Name: VascoVPN Security Level: Custom Remote Gateway: Predefined VascoGateway When this is done, click the Advanced button in the bottom of the page. 2007 VASCO Data Security. All rights reserved. Page 21 of 53

Fill in/set the fields like this: (according to your setup) Security Level o User Defined: Custom Phase 2 Proposal o nopfs-esp-des-md5 o nopfs-esp-des-sha o nopfs-esp-3des-md5 o nopfs-esp-3des-sha At the bottom of the page click Return and in the VPN page click OK to save your settings and go back to the list page. 2007 VASCO Data Security. All rights reserved. Page 22 of 53

5.8 Policy configuration Our VPN is now setup, but we will have to make a firewall policy that allows the incoming VPN connection and to bind this VPN connection to a VPN tunnel. Select Policies from the menu. Select From: Untrust - To: Trust and click New. 2007 VASCO Data Security. All rights reserved. Page 23 of 53

Fill in/set the fields like this: (according to your setup) Name: VascoPolicy Source Address o Address Book Entry: Dial-Up VPN Destination Address o New Address: 10.0.2.0 / 24 Action Tunnel Tunnel VPNs VascoVPN Select Position at Top When you already had a VPN policy before, you will receive a notification message stating there is a Duplicate Address entry. Click OK. 2007 VASCO Data Security. All rights reserved. Page 24 of 53

If you received the notification message of the duplicate address, it may be advised to uncheck the enable checkbox of the old policy. This finishes our ScreenOS settings. 2007 VASCO Data Security. All rights reserved. Page 25 of 53

5.9 Summary As a little recapitulation of what we did, this little scheme represents how everything is connected: Firewall Policy VascoPolicy VPN Tunnel VascoVPN VPN Gateway VascoGateway Local Group VascoGroup Local User VascoXAuth XAuth Settings XAuth Server VACMAN Middleware IP Pool VascoPool 2007 VASCO Data Security. All rights reserved. Page 26 of 53

6 NetScreen-Remote We will now setup the client side to make a VPN connection to the Juniper SSG-520 with the settings we changed in the previous chapter. To make the actual connection we have to specify a username and password that will be verified on the VM3.0. 6.1 New connection To create a new connection on the Juniper-Remote client, select Edit Add Connection. 2007 VASCO Data Security. All rights reserved. Page 27 of 53

Give the connection a meaningful name, select it and change the following settings according to your setup. Connection Security: Secure Select Only Connect Manually ID Type: IP Subnet Subnet: 10.0.2.0 Mask: 255.255.255.0 Protocol: All Select Use Secure Gateway Tunnel ID Type: IP Address 10.0.1.1 2007 VASCO Data Security. All rights reserved. Page 28 of 53

6.2 My Identity Go to My Identity and change the Select Certificate to None. By doing this the Pre- Shared Key button will become available. Click this button. Click the Enter Key button and fill in the Pre-Shared Key you set up in the ScreenOS in the previous chapter under the Gateway settings. In our case this was vasco123. Click OK when finished. 2007 VASCO Data Security. All rights reserved. Page 29 of 53

Fill in the rest of the fields like this or according to your setup: ID Type: E-mail Address xauth@labs.vasco.com Virtual Adapter: Disabled Internet Interface: Any 2007 VASCO Data Security. All rights reserved. Page 30 of 53

6.3 Security Policy Select the Security Policy and select Aggressive Mode in the list. Go to Phase 1 Proposal and select Pre-Shared Key; Extended Authentication as authentication method. Make sure the encryption and hash algorithm are in the list you selected in the Advanced Gateway settings in the previous chapter. Possible combinations: des-md5, des-sha1, 3des-md5 and 3des-sha1. Also make sure the Key Group is Diffie-Hellman Group 2. 2007 VASCO Data Security. All rights reserved. Page 31 of 53

In the Phase 2 Proposal you have to select the same as above in the Encapsulation Protocol field. The Authentication Protocol should be empty. Possible combinations: des-md5, des-sha1, 3des-md5 and 3des-sha1. When all settings are done, click File Save to save this profile and be able to use it. Now our server and client are setup. We will now take a look how VM3.0 has to be configured and how a user can be added/created to test our VPN connection. 2007 VASCO Data Security. All rights reserved. Page 32 of 53

7 VACMAN Middleware 7.1 Policy configuration Setting up the VM only requires you to set up a policy to go to the right back-end and to add an extra Radius component pointing to the ISA server. To add a new policy, right-click Policies and choose New Policy. Figure 2: VM configuration (1) There are a few policies available by default. You can also create new policies to suit your needs. Those can be independent policies, inherit or copy their settings from default or other policies. Fill in a policy name and choose the option most suitable in your situation. If you want the policy to inherit setting from another policy, choose the inherit option. If you want to copy an existing policy, choose the copy option and if you want to make a new one, choose the create option. Figure 3: VM configuration (2) We chose to create a new policy and specify all details about the authentication policy. 2007 VASCO Data Security. All rights reserved. Page 33 of 53

In the policy properties configure it to use the right back-end server. This could be the local database, but also Windows (Active Directory) or another radius server (RADIUS). This could the same authentication service as you were previously using in the ISA server. Main Settings tab o Local auth.: Digipass/Password o Back-End Auth.: If Needed o Back-End Protocol: Windows User Settings tab o Dynamic User Registration: Yes o Password Autolearn: Yes o Stored Password Proxy: Yes o Windows Group Check: No Check Challenge Settings tab o 2-Step Challenge Response None o Primary Virtual DIGIPASS None After configuring this Policy, the authentication will happen, if needed (when it does not know the user locally), in the back-end to Active Directory. User credentials are passed through to the VM3.0, it will check these credentials with the AD and will answer to the ISA server with an Access-Accept or Access-Reject RADIUS message. Figure 4: VM configuration (3) Figure 5: VM configuration (4) Figure 6: VM configuration (5) 2007 VASCO Data Security. All rights reserved. Page 34 of 53

7.2 Component configuration For testing purposes you can change the existing RADIUS Client (default RADIUS client that listens for all connections) by right-clicking and choose Properties. If you already use the default RADIUS client, it would be better to create a new RADIUS component. Figure 7: VM configuration (6) In the policy field you should find your newly created policy. Fill in the shared secret you entered also in the RADIUS server properties on the ISA server. Click Create. Figure 8: VM configuration (7) All configuration is done by now. The next chapter shows you how to add a user manually. In our policy we enabled the Dynamic User Recognition (DUR). So users who get verified through the Active Directory, and are not known in the local database, are automatically added. It also shows how to assign a DIGIPASS to a user. 2007 VASCO Data Security. All rights reserved. Page 35 of 53

8 User configuration The user creation steps you will find in this chapter are optional when you didn t activate the option Dynamic User Registration (DUR) and/or Password Autolearn in your policy settings. The assignment of a DIGIPASS can happen manually as explained in the steps below. The user creation and DIGIPASS assignment steps depend on which database backend you installed VACMAN Middleware. Either you installed it with an ODBC back-end or with an Active Directory back-end. 8.1 ODBC installation 8.1.1 User creation User creation, while using an ODBC back-end, will happen in the DIGIPASS Administration MMC. Right-click the Users folder and select New User... Figure 9: ODBC User Creation (1) 2007 VASCO Data Security. All rights reserved. Page 36 of 53

Fill in the username and password fields. Optionally choose the right domain and Organizational Unit and click the Create button. Figure 10: ODBC User Creation (2) The user will now show up in the Users list of you DIGIPASS Administration MMC. At this point it will be exactly the same as when Dynamic User Recognition (DUR) was enabled. Figure 11: ODBC User Creation (3) 2007 VASCO Data Security. All rights reserved. Page 37 of 53

8.1.2 Import DIGIPASS Right-click the DIGIPASS folder and select Import DIGIPASS.... Figure 12: Import DIGIPASS (1) Browse for your *.DPX file, fill in the Transport Key and look at your available applications by pushing the Show Applications button. You can either import all applications or only the ones you selected, by the Import buttons above and below the Show Applications button. Figure 13: Import DIGIPASS (2) 2007 VASCO Data Security. All rights reserved. Page 38 of 53

8.1.3 DIGIPASS Assignment There are two possible ways to assign a DIGIPASS to a user. You can search for a DIGIPASS and assign it to a user or you can search for a user and assign it to a DIGIPASS. You can see the difference in the following two figures. Right-click a user and select Assign DIGIPASS... or... Figure 15: DIGIPASS assignment (1) you can right-click a DIGIPASS and select Assign. Figure 16: DIGIPASS assignment (2) 2007 VASCO Data Security. All rights reserved. Page 40 of 53

If you leave the User ID blank and press the Find button, you will get a list of all the available users in the same domain as the DIGIPASS. The usernames are partly searchable too. Notice: If no users show up, make sure the domains of the DIGIPASS and the user match. Figure 17: DIGIPASS assignment (3) When assigning a DIGIPASS to a user the same procedure will be applicable. You can either select the desired option to search for a DIGIPASS or search through serial number. Leaving all options blank will show all possibilities in the same domain. When the DIGIPASS gets successfully added to your user you will get a confirmation message. Figure 18: DIGIPASS assignment (4) 2007 VASCO Data Security. All rights reserved. Page 41 of 53

8.2 Active Directory installation 8.2.1 User creation User creation, while using an Active Directory back-end, will happen in the Active Directory Users and Computers MMC. Right-click a user and select Properties. This can happen automatically when the Dynamic User Registration (DUR) option in the policy settings is active. Figure 19: Active Directory User Creation (1) 2007 VASCO Data Security. All rights reserved. Page 42 of 53

In the DIGIPASS User Account tab you will see a field to manually add a password. This can also be automatically filled by enabling the Password Autolearn option in the policy settings. Figure 20: Active Directory User Creation (2) After clicking the Apply button you will see the Update History fields being filled with the current date and time. When these fields are filled it means the DIGIPASS account exists and can be used. Figure 21: Active Directory User Creation (3) 2007 VASCO Data Security. All rights reserved. Page 43 of 53

8.2.2 Import DIGIPASS To make sure you can see the DIGIPASS folders in the MMC, go to View and select the Advanced Features. This way you will see the DIGIPASS folders. Figure 22: Import DIGIPASS (1) Right-click the DIGIPASS-Pool folder and select Import DIGIPASS. Figure 23: Import DIGIPASS (1) 2007 VASCO Data Security. All rights reserved. Page 44 of 53

Browse for your *.DPX file, fill in the Transport Key and look at your available applications by pushing the Show Applications button. You can either import all applications or only the ones you selected, by the Import buttons above and below the Show Applications button. Figure 24: Import DIGIPASS (1) When the DIGIPASS is imported successfully you will receive a confirmation message. Figure 25: Import DIGIPASS (1) 2007 VASCO Data Security. All rights reserved. Page 45 of 53

8.2.3 DIGIPASS assignment There are two possible ways to assign a user to a DIGIPASS. You can search for a DIGIPASS and assign it to a user or you can search for a user and assign it to a DIGIPASS. You can see the difference in the following two figures. Right-click a User and select Assign DIGIPASS... or... Figure 26: DIGIPASS Assignment (1) right-click a DIGIPASS and select Assign DIGIPASS. Figure 27: DIGIPASS Assignment (2) 2007 VASCO Data Security. All rights reserved. Page 46 of 53

If you leave the User ID blank and press the Find button, you will get a list of all the available users in the same domain as the DIGIPASS. The usernames are partly searchable too. Figure 28: DIGIPASS Assignment (4) When assigning a DIGIPASS to a user the same procedure will be applicable. You can either select the desired option to search for a DIGIPASS or through serial number. Leaving all options blank will show you all possibilities. Remember to check the Search upwards checkbox. 2007 VASCO Data Security. All rights reserved. Page 47 of 53

9 Juniper-Remote test To test our VPN connection, right click the Juniper-Remote icon in the taskbar and select Connect My Connections\VascoVPN. This is the name you specified when you created a new connection in the Juniper-Remote client. If the tunnel is initiated correctly, you will be asked to put in a username and password. Type here the username and OTP that will be verified on VM3.0. In our case this was testuser and a Demo OTP. When everything works fine, you will be authenticated and VPN connection is started. You will now be able to reach the trusted network from your remote computer. 2007 VASCO Data Security. All rights reserved. Page 48 of 53

10 VACMAN Middleware features 10.1 Installation The VACMAN Middleware (VM) installation is very easy and straightforward. VM runs on Windows platforms, supports a variety of databases and uses an online registration. Different authentication methods allow a seamless integration into existing environments. 10.1.1 Support for Windows 2000, 2003, IIS5 and IIS6 VM can be installed on Windows 2000 and Windows 2003. Web modules exist for IIS5 and IIS 6 to protect Citrix Web Interface, Citrix Secure Gateway, Citrix Secure Access Manager (Form-based authentication), Citrix Access Gateway and Microsoft Outlook Web Access 2000 and 2003 (Basic Authentication and Form-Based Authentication). 10.1.2 Support for ODBC databases and Active Directory Any ODBC compliant database can be used instead of the default PostgreSQL database (MS SQL Server, Oracle). Since Version 2.3 of VACMAN Middleware, AD is not only intended for storage of DIGIPASS anymore, but configuration and management of your DIGIPASS infrastructure is now also full integrated into the AD management tools. This option requires an AD schema update. 10.2 Deployment Several VACMAN Middleware features exist to facilitate deployment. Combining these features provides different deployment scenarios from manual to fully automatic. 10.2.1 Dynamic User Registration (DUR) This feature allows VM to check a username and password not in the database with a back-end RADIUS server or a Windows domain controller and, if username and password are valid, to create the username in the VM database. 10.2.2 Autolearn Passwords Saves administrators time and effort by allowing them to change a user s password in one location only. If a user tries to log in with a password that does not match the password stored in the VM database, VM can verify it with the back-end RADIUS server or the Windows domain controller and, if correct, store it for future use. 10.2.3 Stored Password Proxy Allows VM to save a user s RADIUS server password or Windows domain controller password in the database (static password). User s can then log in with only username and dynamic one-time password (OTP). If this feature is disabled, users must log in with username and static password immediately followed by the OTP. 10.2.4 Authentication Methods Different authentication methods can be set on server level and on user level: local authentication (VM only), Back-End authentication (Windows or RADIUS). On top of that a combination of local and back-end can be configured. The additional parameters always, if needed and never offers you additional customization of the back-end authentication process. 2007 VASCO Data Security. All rights reserved. Page 49 of 53

The configuration of authentication methods is done within the policy (policies). 10.2.5 Policies Policies specify various settings that affect the User authentication process. Each authentication request is handled according to a Policy that is identified by the applicable Component record. Components can be radius clients, authentication servers or Citrix web interfaces. 10.2.6 DIGIPASS Self Assign Allows users to assign DIGIPASS to themselves by providing the serial number of the DIGIPASS, the static password and the OTP. 10.2.7 DIGIPASS Auto Assign Allows automatic assignment of the first available DIGIPASS to a user on user creation. 10.2.8 Grace Period Supplies a user with a certain amount of time (7 days by default) between assignment of a DIGIPASS and the user being required to log in using the OTP. The Grace Period will expire automatically on first successful use of the DIGIPASS. 10.2.9 Virtual DIGIPASS Virtual DIGIPASS uses a text message to deliver a One Time Password to a User s mobile phone. The User then logs in to the system using this One Time Password. Primary Virtual DIGIPASS A Primary Virtual DIGIPASS is handled similarly to a standard physical DIGIPASS. It is imported into the VACMAN Middleware database, assigned to a User, and treated by the VACMAN Middleware database as any other kind of DIGIPASS. Backup Virtual DIGIPASS The Backup Virtual DIGIPASS feature simply allows a User to request an OTP to be sent to their mobile phone. It is not treated as a discrete object by VACMAN Middleware, and is not assigned to Users, only enabled or disabled. It can be enabled for Users with another type of DIGIPASS already assigned, and used when the User does not have their DIGIPASS available. 2007 VASCO Data Security. All rights reserved. Page 50 of 53

10.3 Administration 10.3.1 Active Directory Users and Computers Extensions Since VACMAN Middleware version 2.3, Managing the users and DIGIPASS can be done within the Active Directory Users and Computers section. Selecting the properties of a user, offers complete User-DIGIPASS management. Figure 29: VM Features (1) 10.3.2 Administration MMC Interface A highly intuitive Microsoft Management Console (MMC) exists to administer the product. An Audit Console is available to give an instant view on all actions being performed on the VM. Both can be installed on the VM server itself or on a separate PC. Figure 30: VM Features (2) 2007 VASCO Data Security. All rights reserved. Page 51 of 53

10.3.3 User Self Management Web Site A web site running on IIS has been developed to allow users to register themselves to the VM with their username and back-end (RADIUS or Windows) password, to do a DIGIPASS self assign, to update their back-end password stored in the VM database, to do a change PIN (Go-1/Go-3 DIGIPASS), to do a DIGIPASS test. Figure 31: VM Features (3) 10.3.4 Delegated administration Administration can be delegated by appointing different administrators per organizational unit (OU). These administrators can only see the DIGIPASS and users that were added to his OU. 10.3.5 Granular access rights It is possible in VACMAN Middleware to setup different permission per user. This can be in function of a domain or an organizational unit. Administrators belonging to the Master Domain may be assigned administration privileges for all domains in the database, or just their own domain. Administrators belonging to any other Domain will have the assigned administration privileges for that Domain only. It s possible to set different operator access levels. E.g. A user can be created that only has the rights to unlock a DIGIPASS. Figure 32: VM Features (4) 2007 VASCO Data Security. All rights reserved. Page 52 of 53

11 About VASCO Data Security VASCO designs, develops, markets and supports patented Strong User Authentication products for e-business and e-commerce. VASCO s User Authentication software is carried by the end user on its DIGIPASS products which are small calculator hardware devices, or in a software format on mobile phones, other portable devices, and PC s. At the server side, VASCO s VACMAN products guarantee that only the designated DIGIPASS user gets access to the application. VASCO s target markets are the applications and their several hundred million users that utilize fixed password as security. VASCO s time-based system generates a one-time password that changes with every use, and is virtually impossible to hack or break. VASCO designs, develops, markets and supports patented user authentication products for the financial world, remote access, e-business and e-commerce. VASCO s user authentication software is delivered via its DIGIPASS hardware and software security products. With over 25 million DIGIPASS products sold and delivered, VASCO has established itself as a world-leader for strong User Authentication with over 500 international financial institutions and almost 3000 blue-chip corporations and governments located in more than 100 countries. 2007 VASCO Data Security. All rights reserved. Page 53 of 53