The hassle of keeping more than one method up to date for people who change phone numbers and/or phones yearly grows exponentially with each multi-factor authentication method added. It’s counter-intuitive for people to have to use one multi-factor authentication method for one system or platform the organization uses, and another method for another.
With Microsoft cloud services on the rise, another problem might also arise: disparate multi-factor authentication methods for users. However, when a malicious person gains access to the ‘secure’ productivity platform of an organization through stuffed credentials. There are many virtual desktop solutions in the market today, but VMware’s Horizon product is the popular choice for organizations.
To adhere to privacy regulations, organizations deploy virtual desktop solutions to provide secure means to achieve productivity with the organization’s sensitive data. Though credential stuffing attacks, they will use these leaked credentials and try them on your organization’s public facing applications and services. However, as cloud applications and services are breached, credential sets fall in the hands of malicious people. Today’s cloud applications and services allow sign-ins with email addresses, as it’s currently the only truly global identifier for people.
Here’s how we secured their VMware Horizon implementation with Azure MFA through the Azure MFA NPS Extension: As the organization leverages VMware Horizon, this implementation needs to be switched to Azure MFA as well. This week, one of my customers is switching to Azure multi-factor authentication as their only multi-factor authentication solution for their employees.
0 kommentar(er)
