{"id":2529,"date":"2021-05-25T10:35:06","date_gmt":"2021-05-25T10:35:06","guid":{"rendered":"https:\/\/www.securecloudaas.com\/?p=2529"},"modified":"2021-05-25T10:35:12","modified_gmt":"2021-05-25T10:35:12","slug":"passwordless-authentication-security-and-convenience-with-azure-ad","status":"publish","type":"post","link":"https:\/\/www.securecloudaas.com\/passwordless-authentication-security-and-convenience-with-azure-ad\/","title":{"rendered":"Passwordless Authentication \u2013 Security and convenience with Azure AD"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

With 4 in 10 UK businesses<\/a> reporting security breaches in the last 12 months it\ncan be difficult to keep up with the best methods of protecting your business\nand its data. One of the \u2018easiest\u2019 methods of keeping hackers out are long,\ncomplex passwords. Although this is simple in theory, in practice it can be\ndifficult to remember a new complex password for each application, not to\nmention there is still the risk of replay or phishing attacks. This difficulty\nmay explain why the most common password<\/a> is still \u2018123456\u2019. Multi-factor authentication has definitely improved\nsecurity, regardless of the complexity of a password, but it has come at the\ncost of convenience. For passwords, it may seem like security and convenience are\nmutually exclusive terms, but with the advent of passwordless authentication both\nare now possible. <\/p>\n\n\n\n

The term \u2018passwordless authentication\u2019 sounds like a\nsecurity nightmare, however through innovations in biometrics, identity\nprotection and the FIDO alliance, it is now easier and more secure than ever. With\nphishing being the most common form of attack vector for cybersecurity\nincidents, passwordless authentication makes these attacks impossible as there\nis not a password to phish. The security benefits alone make this method of\nauthentication an attractive option for businesses, however it is also more\nconvenient to no longer require a password. Gone are the days of forgetting a\npassword, writing it down on a sticky note or having to change it every 6 weeks.<\/p>\n\n\n\n

There are three methods of passwordless authentication\nthat can be easily deployed in Azure Active Directory that suit a wide range of\nbusiness requirements, a short summary of each is provided below.<\/p>\n\n\n\n

Windows Hello for Business<\/strong><\/p>\n\n\n\n

Windows Hello for Business is an option that utilises\ntwo-factor authentication with a PIN and biometric authentication. If this\noption is deployed when a user reaches a login screen, they are promoted to\nenter their PIN and can either scan their fingerprint or use facial recognition\nto gain access. The PIN rules can be set by an administrator for the minimum\nand maximum length and what requirements it must have. The biometrics can be\neither a fingerprint or facial recognition depending on the hardware and user\u2019s\npreference. This option works by using a public\/private key pair where the\nbiometrics is stored on the local device and is never sent to another device or\nserver making it impossible for a potential hacker to steal biometric\ninformation.<\/p>\n\n\n\n

This method is more secure and convenient than a\ntraditional password as it uses multifactor authentication, and the biometric\nauthentication only requires the user to touch a sensor or look into their\ncamera.<\/p>\n\n\n\n

Microsoft Authenticator App<\/strong><\/p>\n\n\n\n

The Microsoft Authenticator app is another method of\npasswordless authentication that uses either biometrics or a PIN, similar to\nWindows Hello for Business. This option requires users to have the Microsoft\nAuthenticator app installed on in their Android or IOS device. When the user\nreaches the login screen and enters their username a push notification will be\nsent to their phone, opening the Microsoft Authenticator app. They then enter\neither a PIN or use their phone\u2019s native biometric features and Azure AD\nperforms a public\/private key validation and the user is automatically logged\nin. This method is user friendly, secure, and easy to deploy in Azure AD as\nmany users already use the Microsoft Authenticator app.<\/p>\n\n\n\n

FIDO2 Security Keys<\/strong><\/p>\n\n\n\n

FIDO (Fast IDentity Online) Alliance aims to promote\nopen authentication standards and reduce the use of traditional passwords as\nthe main form of authentication. FIDO2 security keys are unphishable and come\nin many form factors, allowing the user to sign into resources without a\nusername or password, using an external security key. This option is similar to\nhow a key works for a house or car, where you must physically have the security\nkey to gain access to a system or resource. The security key is typically a USB\ndevice, but can also be Bluetooth or NFC from a phone. When a user reaches a\nlogin screen they only need to select \u2018Sign in with a security key\u2019 and plug in\ntheir FIDO2 security key and Azure AD will perform a public\/private key\nvalidation and they will be granted access. This option is perfect for\nbusinesses that are particularly security sensitive or have employees that\nwould rather not use biometrics or their phone for authentication.<\/p>\n\n\n\n

The advent of passwordless authentication streamlines\nuser experience whilst greatly increasing security. With multiple options for\nsimple integration with Azure AD, make forgotten passwords and phishing attacks\na thing of the past. If you want to find out more on which passwordless\nauthentication solution is best for you, get in touch today.<\/p>\n","protected":false},"excerpt":{"rendered":"

With 4 in 10 UK businesses reporting security breaches in the last 12 months it can be difficult to keep up with the best methods of protecting your business and … <\/p>\n

Read More<\/a><\/div>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"aioseo_notices":[],"_aioseop_description":"","_aioseop_title":"","_links":{"self":[{"href":"https:\/\/www.securecloudaas.com\/wp-json\/wp\/v2\/posts\/2529"}],"collection":[{"href":"https:\/\/www.securecloudaas.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.securecloudaas.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.securecloudaas.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.securecloudaas.com\/wp-json\/wp\/v2\/comments?post=2529"}],"version-history":[{"count":0,"href":"https:\/\/www.securecloudaas.com\/wp-json\/wp\/v2\/posts\/2529\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.securecloudaas.com\/wp-json\/wp\/v2\/media?parent=2529"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.securecloudaas.com\/wp-json\/wp\/v2\/categories?post=2529"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.securecloudaas.com\/wp-json\/wp\/v2\/tags?post=2529"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}