3 Ways To Keep Your Sign-In Process Secure

Rhian Greener

3 minutes read time

April 03, 2019

Last month, visitor management became a hot topic as IBM posed some questions around Kiosk and reception security.

Here at WhosOnLocation, security concepts and techniques have been integral to our design right from the beginning. We continue to invest heavily in security improvements and we regularly carry out security audits, including third-party audits.

Further to these robust processes, and in light of IBM’s recent findings, there are some steps you can take as a customer to make your sign-in process even more secure.

Capture Identifying Information

The first concern IBM raised is how easy it might be for a visitor to sign-in without any identifying information. The WhosOnLocation application offers a setting for “host badge pass authorization”, requiring the host to verify the visitor before their pass can be printed. Your WhosOnLocation administrator can turn this feature on for you.

For further security, we also offer WolScan.

ID scanning for visitor management

This WhosOnLocation add-on provides an extra layer of security to the sign-in process. Using the app, the host can scan a visitor’s passport, driver’s license or other photo ID to capture their information and verify their identity.

Get granular with your access rights

The second concern IBM raised is how easy it is to access other people’s information within a visitor management system.

At the Kiosk, access to the WhosOnLocation application is incredibly limited. Both employee and visitor privacy controls restrict the information available to users when signing in and out from a Kiosk.

In addition to this, no data is stored on the Kiosk itself, so if a visitor was able to gain access to the device, they wouldn’t be able to retrieve any of your WhosOnLocation employee or visitor data.

Within the WhosOnLocation application itself, all access to data is governed by access rights and every user attempting to access your WhosOnLocation account is authenticated by username and password.

So how can you further secure this information? Your WhosOnLocation administrator can define granular access privileges to individual users, so make sure you use this feature. Be selective with who can access data, and make sure only essential access is granted to each user.

Secure your Kiosk

Lastly, IBM questioned is how easy it is for a visitor to break out of the application at the Kiosk and interact with the operating system.

Even if your hardware only hosts your visitor management software, giving visitors access to the operating system could pose a security threat. If a visitor is able to exit the application, there’s a chance they could use tools to install remote access malware.

We’ve been looking into the best way to secure your Kiosk by locking the screen to the application. While this process is quick and easy for iPads, Windows devices can be a little trickier to secure, and may require the help of your organization’s IT team.

To help you on your way, we’ve updated our helpdesk article.

Try WhosOnLocation for 30 days.