If you are an existing client to get support call us on:
If you have 24 hour support please use your dedicated 24 hour support numberOR
Posted on January 22, 2019 by Louise Howland
Multi-Factor Authentication (MFA) is something everyone will have experienced. It’s the additional levels of security used when you sign into a banking app when you try to change a password and a verification code is sent to your mobile phone, or when you are asked to answer additional security questions after already providing your password. All of these examples are multi-step authentications that allow you to prove you are who you say you are. This provides peace of mind to both you and to the company providing the service that hackers can’t impersonate you.
Up until recently, especially with GPDR and similar data protection laws, most organisations have not considered implementing this additional layer of protection into their corporate data. With Office 365, it’s now a realistic, cost-effective option to improve the protection of your business data as flexible working becomes commonplace.
Obviously, the main reason for using MFA is security, if it is set-up correctly, it eliminates the risk of an account being compromised because of a weak, shared or known password. Increasing numbers of accounts (including Office 365) are being compromised, because users have used the same password across different systems. Services, such as LinkedIn and Adobe, have previously had their account databases stolen, giving hackers the ability to hack users’ accounts using the same credentials.
With MFA, even if someone knows your username and password, they are not able to log-in without access to your mobile phone or additional authentication device.
When it comes to setting up MFA in Office 365, one of the biggest barriers is end– user adoption. Fortunately, ramsac can help with the MFA setting up process as part of our Office 365 service. , but if you’re unsure about how your employees or customers may find it, have a read on to find out more about how it looks.
It is possible to set-up MFA to not to be required when logging in from a trusted network, so users won’t become frustrated by having to provide additional authentication when in the office or on a secure device.
Choosing the security verification method in Office 365
When out of the office, a user can log in as normal using their username and password. If they are using an authenticator app on a mobile device, such as Google Authenticator, they get prompted to approve the login. This is by far the least intrusive and easiest option, not only to set up but to use regularly.
Using an authenticator app
If they click ‘approve’ they are logged straight in. Other options are using a code from the authenticator app, being sent a code by text, or a phone call with a recorded message giving a code. Overall, the experience is painless, and easy to understand, even for those who may struggle with technology.
Introducing MFA must be planned as a project as it’s potentially disruptive to end-users and could leave them unable to work. The risks organisations need to consider prior to implementing MFA, to ensure a smooth implementation experience are
When implementing MFA for organisations we follow several golden rules.