Hewden chooses mobile phone token security


Hewden chooses mobile phone token security

Antony Savvas

Hewden, the equipment rental provider, has chosen a mobile phone security token system to protect its corporate systems when its rental team need to access applications and data remotely. 

Hewden, which has 360 service delivery centres throughout the UK, has chosen the SecurAccess system from SecurEnvoy.

SecurAccess is a two-factor authentication system that uses mobile phones as virtual tokens. It removes hardware and deployment management problems, and prevents keylogging attacks.

Hewden had originally considered the use of hardware tokens to add a second authentication factor to its remote workforce, but opted for virtual tokens as the most appropriate and effective solution.

A one-time pass code is sent to a remote worker's individual mobile phone  to allow them to use the corporate system remotely. They then simply enter their standard user name and Microsoft password, plus the pass code from their mobile phone. 

Once the pass code has been used, a new one is sent and the previous pass code is overwritten.
Using SecurAccess is said to have saved Hewden between 50% and 60% off the cost of using hardware tokens, as the user licence is cheaper.
Tom Mann, Hewden infrastructure manager, said, "Hardware tokens are expensive, not user friendly and all too easy to lose and break. Mobile phones provide a much more robust solution and are very straightforward to use.”

Related article: Entrust sells cheaper security tokens

Comment on this article: computer.weekly@rbi.co.uk


Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

COMMENTS powered by Disqus  //  Commenting policy