Authentication makes sure the person accessing their bank account, your network, email account, application, website shopping system etc. is who they say they are, and that they are authorised to view information, make payments etc..

Two Factor authentication adds the requirement to have the ability to generate a token, or one time password using an authorised method.

• Customer installs Deepnet Authentication "server" software.

• Customer decides which application they wish to authenticate to occur.  For example lets say Outlook Web Access 2003 (OWA).

• Following simple instructions provided customer configures OWA to require authentication.

• Customer decides which form of tokens they wish to issue - for example again lets say you wish to issue "One Time Password" tokens via SMS to their mobile phone.

• In the Deepnet Authentication "server" software, you create a user, set up their details and enter their mobile number.

• End user goes to the OWA server and tries to logon.  Customer enters their username and password, and is presented with a button to send a OTP (one time password) via SMS.

• In a few seconds an SMS is received by the end users mobile phone which they enter into the logon screen, authorised and logon to OWA proceeds as normal.

• End user leaves the company.   Deepnet administrator clicks a button which revokes the customers ability to receive OTP (this can be done automatically via AD / LDAP etc).

They are also frequently lost - adding to inconvenience (no token = no access) and expense for both the end user and the issuing company.

Already use RSA, Safeword, Vasco, Aladdin or other push-button hardware tokens? Costing you a fortune to replace, manage and deploy? See Deepnet's free hardware swapout offer.

Everything is included in one price. 

Server software, all software token types and all application methods are included - you choose how you wish to deploy / mix and match authentication to your requirements.

The customer will then create an account, and purchase credits which are debited as users receive SMS messages.

ClickaTell are highly reliable, ultra-fast and very cost-effective.  Bulk credits can be purchased and work out at around 2p per SMS.

• The Deepnet Administrator would create a user, select MobileID as the delivery method, and enter the end-users mobile number.

• An option would then be presented to deliver the MobileID application to the phone via WAP Push.

• Once received on the mobile device, you save the application.

• Then if for example you wish to log on to Outlook Web Access using MobileID, you would visit the OWA website, enter your username and password as normal.  You will also be prompted for a OTP )one time password).   You would go to "Applications" on your mobile and run the MobileID application.

• A OTP will be generated which you would enter into OWA and logon would proceed as normal.

However, Tokens / token generation is decided on by the business - and depending on which authentication method is chosen you may run some authentication client software on the PC - it may even be a "home" PC....

That's it. There are NO confusing price lists and NO hidden optional extras.

• All of the server software is included.
• You can use ANY combination of available token generation methods- MobileID, QuickID, Typesense etc. etc.  Its your choice from within the management console..
• Annual support and upgrades is included.
• There are NO COSTS FOR HARDWARE TOKENS.