Can you identify yourself?

It has long been standard to log into a digital system using just a username and password. Nowadays, it has become more complex to keep your business data safe. Alongside applications that run on premise in the company’s system, employees also use cloud applications such as Office 365 and Salesforce. Obviously they want easy access, they don’t want to log in separately to each application.

It occurs frequently that employees need to log in remotely when they are visiting customers or suppliers. Companies want to keep control of course, so it must be clear who uses which app and when. It is important that accounts are not abused by unauthorized persons, and that employees are not using each other’s account.

When using cloud services, information is sent over the internet. That might lead to the interception of data. A username and password alone are therefore no longer sufficient. Just like online banking, two-factor authentication has become standard: people identify with something they know (the password) and with something they have. The latter means that they have to type in a code that is generated by a card reader or a smartphone.

The user prefers to do that only once a day (single sign on), whether an app is in the cloud or on the company’s server. The solution to this, is a system for identity and access management (IAM). A good example is Okta, one of SecureLink’s vendors. Okta is a system with 4000 apps. All apps will be accessible via one login per employee. By double-clicking on an application, the authentication will take place in the background.

Furthermore, this can be combined with an internal directory of users. If an employee leaves the company for example, and the HR department indicates this in the system, all business accounts will be inaccessible at once, also those in the cloud. The ease of use for the employee and the ease of management for the company will both become reality.  

 

Frank Staut

CTO, SecureLink Group
frank.staut@securelink.be

2017-05-05T10:30:15+00:00 April 25th, 2017|
SecureLink

SecureLink

X