Thursday, December 9, 2021

The Deprecation Of Basic Auth For Exchange And What It Means For VMware's Workspace ONE Customers

After several delays due to Covid-19 Microsoft has finally fixed a date for prohibiting Basic Auth in Exchange Online.  As of October 1st, 2022, Microsoft will begin disabling Basic Auth in all tenants, with short-term temporary disruptions for some customers beginning early 2022.  This news is initially a bit unnerving given that historically a lot of AirWatch/Workspace ONE customers have leveraged Basic Auth within their ActiveSync profiles.  However, it is limited to Exchange Online customers so on-premises Exchange customers, at least for now, need not worry.   Further, for existing Exchange Online WS1 customers leveraging Basic Auth there's a clear path forward through the adoption of Modern Authentication or other OAuth based alternatives.  This post begins with a quick overview of the ActiveSync Basic Auth deprecation and why it's relevant, then details the choice between Microsoft's Modern Auth or other OAuth based solutions for addressing the challenge.   Of all these OAuth based alternatives Workspace ONE Access is certainly my favorite, so I'll detail the magic that happens when you federate Azure AD with Workspace ONE Access and then introduce certificate based authentication with VMware's proprietary Mobile SSO solution. 

A MEM Misnomer: Rumors Of ActiveSync's Death Are Greatly Exaggerated

About a year and a half ago I started hearing grumblings of impending doom for WS1 customers and Mobile Email Management (MEM) in general.    The rumor went something like this: ActiveSync is getting deprecated which will lead to chaos in MEM everywhere, possibly triggering World War 3.   Making it somewhat believable was that ActiveSync hasn't been worked on for years now, with the latest version of 16.1 released in 2016.   Coupled with Microsoft's hyper focus on GRAPH APIs, in a bad mood, with your eyes squinted, it seemed possible ActiveSync could be going away.   However, the truth was more nuanced.  In August of 2020 I reached out to Martin Kniffin for guidance and he didn't fail to impress,  providing me and a handful of colleagues excellent context.   First and foremost he pointed out that it's not ActiveSync that's getting deprecated, but Basic Auth within ActiveSync. (More specifically, it's Basic Auth that's being deprecated almost across the board, not just within ActiveSync.)   When Basic Auth is used with Exchange Online you have the mail client storing a user's typed in credentials and then passing those credentials to Exchange, which in turn proxies those credentials to Azure AD.  These stored credentials on the endpoint device are constantly replayed against Exchange Online throughout the course of email access.   
Basic Authentication - Image taken from, "Disable Basic Authentication In Exchange Online"
So it's not ActiveSync that's dying off but rather this very rudimentary Basic Auth model that's going away, initially only in Exchange Online environments, not on-premises.   This deprecation has been in the works for awhile. Plans to disable Basic Auth in Exchange Online were first announced in Sept of 2019 with a target date of Oct 2020.   However, in response to Covid-19 it was postponed till the second half of 2021. Then in February of 2021 Microsoft indicated they would postpone until further notice.   At the same time they announced plans to begin disabling Basic Auth for tenants not currently using it.  Now, finally in late September of 2021, it was announced that Basic Auth would be disabled on all tenants starting October 2022, with more formal guidance coming out early November this year.  So, this hasn't exactly been a meteor the size of Texas hurling towards earth from out of nowhere.   More like The Blob, a really, really, really slow moving blob that, nonetheless, needs to be addressed. 

While ActiveSync payloads with Basic Auth have been wildly popular amongst Workspace ONE customers there's a clear path forward: leverage the OAuth ActiveSync payload setting for use with Microsoft's Modern Auth or a 3rd party federated IDP.    

Leveraging Microsoft Modern Auth With The ActiveSync OAuth Payload Setting

If your Office 365 tenant is purely leveraging Azure for identity, with no federation, both Basic Auth and Modern Auth are currently options for email access.   Modern Authentication is a Microsoft solution, "based on the Active Directory Authentication Library (ADAL) and Oauth 2.0."  With Modern Auth users authenticate with their AD credentials to Azure and then are issued a token granting access to Office 365.   So instead of having credentials stored within a mail client and proxied through Exchange Online, users are redirected to Azure at and upon successful authentication are issued a token that grants access to email, as well as the entire Office 365 suite.    

Modern Authentication Workflow - Image Borrowed From Shehan Perera's Tech Blog

In the diagram above you have a representation of Modern Auth in the context of a hybrid identity model that merges on-premises AD environments with an Azure tenant, allowing users to leverage their on-premises AD credentials when authenticating to Azure.  It starts with an on-premises Azure AD Connect instance that syncs accounts from on-premises with Azure. Then for authentication there's what's referred to as managed authentication, with a choice between password hash authentication (PHS) and pass-through authentication. (PTA)  With PHS hashes of your AD passwords are synchronized from your on-premises AD environment to the cloud. 

With PTA instead of having hashed passwords stored in the cloud validation occurs directly against your on-premises AD environment via an on-premises agent.  

Either model is supported with Modern Auth and the ActiveSync, "Use OAuth," payload setting. It's just a matter of personal taste for the organization. With both models you're extending your on-premises authentication to Azure and either one can work with the OAuth payload. As far as the ActiveSync payload settings in WS1 goes, all you have to do is check the box for, "Use OAuth, " and your email users will start getting prompted for Modern Auth. The, "OAuth Sign In URL," and, "OAuth Token URL," fields are not mandatory and can be left blank.  When you leaves these fields blank an autodiscovery process kicks in, one that first redirects

The redirect to creates a slightly different experience from the traditional Basic Auth workflow, but it's not insurmountable.  Below is a recording that compares and contrast the two experiences with the built in iOS mail client. 

Also, there's certainly support for Modern Auth from most other mail clients as well, such as Boxer or Outlook. Here's what the process looks like for Boxer: 


Leveraging Workspace ONE Access With The ActiveSync OAuth Payload Setting

Along with Modern Auth, this, "Use OAuth," feature supports authentication against Workspace ONE Access, as well as various other federated IDPs such as ADFS, Okta or Ping.  When it's time to authenticate the user first hits, then based on their email address gets redirected to a federated IDP.    In this example, AD authentication occurs through an instance of WS1 Access that's been federated with Azure.   It's very similar to Microsoft's Modern Auth model, except there's a redirection to a WS1 Access tenant where credentials are manually entered.  Here's a demonstration: 

For a more ideal experience you can accommodate authentication with  Mobile SSO for iOS, an incredibly compelling proprietary VMware solution that combines WS1 UEM with WS1 Access to provide SSO for mobiles apps. 

First and foremost, VMware's Mobile SSO solution provides an incredibly convenient certificate based single sign-on experience.  It also lays the ground work for the adoption of device compliance policies that allow us to factor in device enrollment and device posture while providing contextual authentication through conditional access policies.  Further, this solution extends device compliance security against the entire Office 365 suite, not just email access.  Even more exciting, since Mobile SSO for iOS or Android works for pretty much any Mobile App that supports SAML, adopting this solution for Office 365 puts into place a capability for securing mobile SaaS adoption across the board.  Combine this with VMware's certificate based authentication for modern management and you have a complete solution for layering zero trust security on top of SaaS adoption across most conceivable device types.  

One caveat to be aware of is that federation with an IDP like WS1 Access or other 3rd party solution is an all-or-nothing commitment.   You can't just have a subset of users handled by the federated IDP.  All of them will get initially redirected to the 3rd party IDP.    So before actually federating with another IDP you need to make sure that all your Office 365 users can be properly handled by it.  Further, federation will break Basic Auth, so you'd need to prepare accordingly.  


SEG For Office 365 Access

Many folks have quite a visceral response to the deployment model I'm about to mention. There are indeed some organizations that leverage SEG for Office 365 access.  I know, I know. While I can't throughly explain or exhaustively defend the design decision, to my understanding there are some use cases where this is a valid and legitimate option.  More customers than you'd image have needed it. 

I only bring it up here in the context of this ActiveSync discussion because with this model there is some authentication against Exchange Online, so it's possible a subset of folks with this type of deployment could be using Basic Auth.  Fortunately, these users can migrate to OAuth access as well.  Here's a sample from my own lab:

The Only Way Through Is Through - Tick Tock, Tick Tock

In a nutshell, the deprecation of Basic Auth is forcing customers to fall back to Modern Auth/OAuth, or, more accurately, fall forward to Modern Auth/OAuth.  As easy as it's been to just leverage Basic Auth we really should have already been marching away from it anyway, regardless of deprecation plans.  While I don't normally feel the need to defend a monster corporation like Microsoft, technically, it sounds like they're just forcing customers to do what they ought do.  Regardless, Workspace ONE/AirWatch has helped customer's navigate their mobile email management needs for over 10 years and is well positioned to assist with this challenge.  

There's no doubt in my mind that some VMware customers may still have some planning to do.  As of the time of this writing, early December 2021, customers have about 9 and half months to act.  Fortunately, Basic Auth is not dead yet, though the writing is certainly on the wall.  

Sunday, October 10, 2021

Securing Horizon With Cloud Hosted Workspace ONE And Carbon Black

For over a decade VMware's VDI solution has served up on-premises Windows desktops to remote Windows and Mac devices.  While the original solution at its core has stayed relatively the same, the ability to secure Horizon sessions through a tightly integrated SaaS stack represents a dramatic shift.  Using cloud instances of Workspace ONE Access, UEM, Intelligence and Carbon Black customers wrap comprehensive security around an already stellar remote Horizon user experience.   The cloudiness of these offerings means this security is easily layered onto existing Horizon environments non-disruptively, with minimal on-premises footprint. 

Base Image Stolen From Andreano "The Moose With The Juice" Lanusse

This ideal remote access scenario begins with Horizon making virtual desktops and published applications available to the external world through Unified Access Gateway.  Authentication for these Horizon sessions is brokered by a cloud instance of Workspace ONE Access that enforces contextual authentication requirements through conditional access policies.  Workspace ONE UEM informs these policies with device posture insight, while also actively managing and securing these remote endpoint devices.  Additionally, Carbon Black provides Next-Gen Antivirus protection not only for Win10 or macOS endpoint devices, but also for the virtual desktops or RDS hosts remotely accessed through Horizon.   Finally, WS1 Intelligence pulls these solutions together, enhancing automation while further calibrating conditional access policies with information regarding anomalous or risky behavior. 

This post is a primer on how cloud instances of Workspace ONE and Carbon Black are layered onto Horizon deployments to beef up security for remote access.  It starts with a brief overview of Horizon remote access, then elaborates on the security enhancements provided by these cloud services.  I'll essentially break down and explain the image above with, yet, more stolen images!  Yes, for this post I've gathered some of the best images I've ever stolen, modified or otherwise used and abused in the name of love and technical clarity.  After using these images to illustrate the security enhancements enabled for Horizon from the cloud, I’ll move on to review VMware’s Secure Access, a key component of the Anywhere Workspace offering.  VMware Secure Access offers an interesting alternative to Horizon, one that extends the benefits of SD-WAN and SASE to a less centralized remote access deployment. 

Delivering Windows Desktops Or Published Applications Through Horizon

Stolen From Todd Dayton

The above graphic presents a rudimentary but conceptually useful breakdown of VMware Horizon.  To begin with, you have a desktop or RDSH image living within a VM, supported on the same vSphere technology used for traditional server workloads.  A Horizon Connection Server, very much the brains of a Horizon deployment, has full admin access to this vSphere environment, using those rights for provisioning and inventory purposes.  This Connection Server also acts as a broker for incoming connections, routing users to their assigned desktops or RDS hosts after they've been authenticated.  User's eventually view and remotely control their desktops or published applications through display protocols like Blast or PCoIP. 

So, to extend vSphere goodness to desktops we've had to bring the desktops to the vSphere infrastructure, with the desktop OS and supported apps shifting locality from the endpoint to the datacenter.  From there, the Windows desktop is essentially converted into a service that can be consumed from pretty much any device that has network connectivity to the Horizon environment.  The benefits of this model really start to pop when folks are mobile or shifting across various devices.  While your device and network location may change, your virtual desktop stays the same, maintaining the Windows desktop session state.  This leads to a consistent and reliable user experience often referred to as a "Follow-Me" desktop, a concept that's been breaking hearts and taking names in healthcare for over a decade. 

With doctors and nurses highly mobile within the walls of a hospital this "Follow-Me" desktop experience really shines, especially when combined with a badge access solution like Imprivata.  As a 13 year veteran from the mean streets of non-profit healthcare IT, I'd say this user experience is impossible to beat when supporting clinicians and is what drives a lot of VDI adoption in healthcare.  Here's a quick demo: 

High mobility, along with the need to share work areas, make clinicians uniquely suited to benefit from this model.  That said, if you're an office worker with a dedicated cubicle and a dedicated workstation tethered to it, and all your work is done within that cubicle, then the "Follow-Me" desktop lacks wow factor.  However, as soon as you throw in any kind of mobility, even if it's just between cubicles, the question of, "Why bother with Horizon?" starts to melt away.  Throw in remote access from home, possibly in a BYOD scenario, and the question is completely obliterated.  In those scenarios, a "Follow-Me" desktop, one that follows you from work to home, then back, makes for the most ideal Windows user experience imaginable. 

Original Image From: Using Horizon To Access Physical Machines

The path these remote Horizon sessions take to your trusted network from user's homes is provided and secured through Unified Access Gateway.

Providing Remote Access To Your Horizon Service

Remote Horizon access is enabled through Unified Access Gateway (UAG), a Linux virtual appliance that's typically deployed in a DMZ.  It acts as a gateway for your external Horizon users, ensuring all traffic from the remote endpoint device to the virtual desktop or RDS host is on behalf of a strongly authenticated user.  Below is a depiction of Blast, Horizon's display protocol of choice, as it traverses a UAG appliance after successful authentication.  Encryption of this traffic is handled end to end for the entire session through the Blast protocol itself. 

Now, as far as the initial authentication goes, there's various options with UAG.  The default authentication method is passthrough against Horizon's local AD environment by typing in an AD username and password.  However, when Workspace ONE mode is enabled on Horizon Connection Servers, UAG passes SAML traffic for authentication instead, ensuring all Horizon Blast traffic passing through the UAG appliance is for users that have been authenticated according to conditional access policies defined in Access.  Leveraging WS1 Access in this fashion provides admins with the most flexibility and widest range of options when it comes to securing remote access to Horizon.

Brokering Authentication For Horizon Using Workspace ONE Access

Conversations around Workspace ONE Access typically focus on the portal and SSO experience it provides for Horizon and 3rd party SaaS apps.  What's often neglected is how WS1 Access acts as broker for different authentication methods as someone initially logs into the portal or accesses a specific app.  Through conditional access policies admins enforce contextual authentication against the various security solutions WS1 Access has been integrated with.  Auth requirements for any particular app will be determined by the specifics of theses policies and a user's current context.  App access may be a simple SSO experience or as complex as MFA from a fully enrolled and compliant device.  For a deeper dive on conditional access polices and SAML check out this overview on youtube. 

Base Image Stolen From Peter Bjork

Several of the inbound authentication options detailed above are made possible through the deployment of a Workspace ONE Access connector in the customers trusted network.  This connector is key to an integration with an AD environment, syncing AD users to Workspace ONE access and providing the ability to authenticate to AD.  It also enables your tenants integration with on-premises resources such as your Horizon environments or security solutions that support RADIUS. Depending on the specifics of your deployment these WS1 Access Connectors may be the only necessary additional on-premises resources required for securing Horizon from the cloud. 

Now when it comes to integrating WS1 Access with 3rd party security solutions, SAML chaining allows for integration with popular names like Okta, Ping, Azure, as well as any other solutions that support SAML.   After configuring these 3rd party solutions as trusted IDPs for WS1 Access we can  leverage their authentication mechanisms for applications managed through Access.  Below is an example of this process for an Okta integration, something I'm seeing a lot of nowadays.  With a fully documented process for configuring Okta as an IDP, "Integrating VMware Workspace ONE With Okta,"  it's a very accessible option for Workspace ONE customers who already leverage Okta for MFA.  

WS1 Access is basically integration goo, allowing you to integrate Horizon, or any other SAML compliant apps, with whatever security solutions you already have in place.  By linking up with these 3rd party solutions we enjoy a richer set of conditional access policies, as we pick and choose amongst various auth requirements for Horizon across different use cases and scenarios.  This ability to integrate with the security solutions customers are already using to protect their environments makes WS1 Access truly compelling.  You end up with something a bit motley and Frankenstein-ish, or pickle-Rick-ish if you will,  but arguably that's sort of unavoidable when you're stitching together disparate solutions from across your enterprise.  

A WS1 Access deployment is only as interesting as the solutions it's been integrated with.  While support for SAML and RADIUS integrations with 3rd parties offer many alternatives,  where things get really exciting is with the built-in support for Workspace ONE UEM.  When looking at the Inbound/Outbound graphic above, mechanisms like, "Certificate," "Mobile SSO For Android," "Mobile SSO For iOS," and "Device Compliance," result from the integration between Workspace ONE Access and Workspace ONE UEM.

Informing Conditional Access Policies With Device Status Insight From UEM

When Workspace ONE Access and UEM are integrated Horizon access can be predicated on enrollment or even device compliance. This leads to a much more discerning, richer set of conditional access policies.  Essentially, we're taking WS1 Access conditional access policies and juicing them with UEM insight, leading to more informed polices to drive contextual authentication.

Stolen Image From Andreano Lanusse

This progression towards zero trust begins with the various certificate based authentication options supported by the integration of UEM and WS1 Access.   Going back to the Inbound/Outbound graphic of the previous section, the arrows for, "Mobile SSO for iOS," "Mobile SSO for Android," and "Certificates," for Win10 and macOS, are enabled through the integration of WS1 UEM and Access.   While these methods are enforced through Access, the certificates are delivered through UEM, effectively mandating device enrollment in UEM for access to Horizon.  Further, "Device Compliance," can only work in conjunction with one of these authentication methods.  So, in the case of modern management, we're talking about a combination of Certificate auth through WS1 Access, certs delivered through UEM, as well as UEM device compliance policies for Win10 and macOS.  

While device compliance policies wonderfully highlight the ability to interrogate devices with UEM, WS1 UEM enrollment actually MAKES devices more secure.  It's not just about interrogation, but also the ability to help the device course correct and achieve a secure posture.  The nitty gritty, under appreciated work that is, none the less, absolutely critical to security, like patching, firewall configuration,  device encryption and general configuration management falls right in the wheelhouse of WS1 UEM.  So along with vouching for the state of the device it's also literally making it more secure.  This management and control is further extended through an integrated deployment of Carbon Black, a Next-Gen Antivirus solution for Win10 and macOS.

Carbon Black

While UEM management addresses security concerns from the perspective of system configuration and maintenance, Carbon Black addresses security head on when it comes to fighting off hackers, malware and Ransomware.  Core to the suite is cloud based Next-Gen antivirus and behavioral EDR, with an option to fall back to more traditional signature protection.  Carbon Black's NGAV and EDR entail the application of machine learning and AI against data aggregated from millions of customer endpoints. We're talking over 500 TB of endpoint data, over 1 Trillion events a day, getting reported to and processed in the Carbon Black cloud.  This insight is then brought to bare when controlling behavior on endpoint devices.

While cloud is core to Carbon Black's security insight, it has the added benefit of making Carbon Black easier to deploy and manage.  For a typical customer there's zero on-premises infrastructure to be concerned with.  You have a cloud tenant to configure and an agent to deploy to your Win10 or macOS devices and that's the extent of your concern.   For Horizon VDI environments you can simply add the agent to your gold images and you're off to the races. For endpoint devices Workspace ONE UEM itself can easily distribute the agent to managed endpoints.  

Workspace ONE Intelligence and VMware Carbon Black: Automating Device Quarantine Feature Walkthrough

Even more exciting is the ability to trigger actions in Workspace ONE UEM based on threats detected by Carbon Black on managed endpoint devices.  So, for example, if a threat is detected on a device not only can Carbon Black respond, but additional measures can be automatically executed through WS1 UEM to remediate the endpoint.   This is made possible by WS1 Intelligence and the ruthless automation it can enable for  WS1 environments.  

Workspace ONE Intelligence - Gelling It Together Even Further

For this ideal remote access Horizon scenario, Workspace ONE Intelligence introduces ruthless automation while also informing conditional access policies with User Risk Scores and Login Risk Scores.  As mentioned above, we can trigger automated workflows within Intelligence based on threats detected by Carbon Black.  We can also trigger this automation based on device info gather from WS1 UEM, which includes over 200 data points.  Should you require data not collected by UEM out of the box, you can collect additional attributes using custom Sensors for your modern management scenarios.  Sensors enable this extensibility using PowerShell scripts on Win10 or bash, python and Zsh scripts on macOS.  

The data collected within the Intelligence data lake drives ruthless automation that ensures Win10 and macOS devices are properly configured.   This data is also leveraged to generate User Risk Scores and Login Risk Scores ingested by conditional access policies.  In this manner, WS1 Intelligence Risk Analytics enable WS1 Access to calibrate contextual authentication with data regarding anomalous or risky behavior.   

VMware Anywhere Workspace 

Cloud instances of WS1 and Carbon Black offer existing Horizon customers a clear path forward for enhancing security.  However, if Horizon isn't viable but you still have a remote use case you'd like to enhance with the security capabilities  discussed so far, then you probably want to check out VMware's Anywhere Workspace. Workspace ONE and Carbon Black are core to the Anywhere Workspace solution and can enhance VMware Secure Access with some of the same benefits they lend to Horizon. Secure Access marries together Workspace ONE with VMware's SASE solution based on SD-WAN by VeloCloud, offering an alternative that overlaps with remote Horizon access but, more notably, enhances connectivity and security for remote endpoints from the cloud. 

Where Secure Access first differs from Horizon is that instead of providing remote connectivity to a desktop or RDS host back in the datacenter, you're running applications locally on your modern managed Win10 or macOS devices. Workspace ONE UEM can provision these applications as well as provide them remote access back to your trusted network through Workspace ONE UEM's Per-App VPN.  With this model a TLS session is automatically established back to your trusted network for specific applications based on device compliance policies.  This is ideal for a traditional client/server application running locally on your endpoint or perhaps a browser hitting an internal site.  Per-App VPN has always distinguished itself from traditional VPN solutions by limiting VPN connectivity to specific defined apps, rather than the whole device.  Further, it simplifies access because there's no need for a user to manually launch a VPN client. Instead, a TLS session is automagically established on behalf of the users when the enabled app is launched.

Deploying VMware Workspace ONE Tunnel: Workspace ONE Operational Tutorial

Per-App VPN has been part of the AirWatch portfolio for over half a decade, supporting modern management use cases for years.  Secure Access innovates by delivering this Per-App VPN capability through VMware's SASE offering, merging WS1 with VMware's SD-WAN solution. (Velo-Cloud). With this model instead of supporting Per-App VPN through VMware Tunnel on a UAG appliance sitting in the customers DMZ, the VMware Tunnel Service is hosted on behalf of the customer within SASE PoPs.   In a nutshell, VMware Tunnel is hosted as a service, in containers, simultaneously across various SASE PoPs.  Per-App connections are routed from the Tunnel app on endpoint devices to the closest SASE PoP, with most users able to find one within 10 milliseconds of latency.  Once traffic hit's this PoP the benefits of VeloCloud SD-WAN are extended to this VPN access, with optimized connectivity to corporate data centers as well as SaaS and cloud service providers.    

Along with enhancing network connectivity we're getting security enhancement from within the SASE PoP through Cloud Web Security.  This new offering introduces features like SSL inspection, URL filtering and content filtering.  So with the VMware Secure Access model you're not only farming out management of VPN concentrators or UAG instances, you're also moving traditional security security services from on-premises to the cloud.  Running these services within the SASE PoPs circumvents the need for hair pinning internet traffic back through your on-premises network for inspection, certainly a boon for remote performance.  

Though there's overlap between Horizon and VMware Secure Access capabilities, they are very different solutions with different strengths and caveats.  If you're looking to offer a highly curated Windows experience, particularly one that supports a traditional client/server app hosted internally, Horizon is compelling.  All that nitty gritty, unsexy, and persnickety Windows management, in particular customization of Windows applications, is centrally handled and managed by Horizon in a model that's over a decade old. Further with Horizon itself supporting SAML, you're extended the full breadth of WS1 Access capabilities when protecting legacy Windows applications. That said, VMware Secure Access is certainly an intriguing proposition, offering optimized connectivity to corporate networks and the cloud while moving security services closer to remote users.  Ideally, as a customer I'd want Horizon around for the more meticulous Windows requirements, while leveraging Secure Access for everything else.  


Final Thoughts

A couple months ago I presented this best case scenario for remote Horizon access to a session full of jaded, cynical and curmudgeonly IT veterans.  As we digested the current state of the entire VMware EUC stack regarding remote access, I think our collective experience was similar to a parent who has just realized, "holly cow, my baby has grown up and baby is bad!"  While VDI over the last 5 years, at its score, has stayed largely the same, albeit with tons of polish and stability enhancements, the methods for securing its remote consumption have very much changed and evolved. A decade ago it was all about, "slap a horizon client on whatever you want, no data will be at rest on that remote device, so, don't worry, be happy." Fast forward to 2021, we can now ensure that a device remotely accessing Horizon is absolutely secure and virus free, while authenticating a user from that device according to a wide range of contextual authentication options. This is all achieved leveraging mature and proven solutions delivered from the cloud, services that not only radically improved remote Horizon security but are also the foundation of VMware's new Anywhere Workspace offering.  

VMworld 2021 Announcement

Several VMworld 2021 announcement regarding futures certainly shore up the already impressive story covered in this post.  Continuous authentication, enhanced conditional access policies and support for Horizon on SASE show a lot of promise and further reenforce overall confidence in the VMware remote access vision.  Additionally, cloud driven enhancements for simplifying on-premises Horizon management further elucidates a general trend of, "if you can't bring desktops to the cloud, bring cloud services to the desktops."  I only failed to mention these announcements till now because, as a drearily sane engineer from healthcare IT, if a technology wasn't at least 6 months old, I just couldn't take it seriously.  Along those lines,  everything covered in this post up till this section is grounded in the here and now of what is GA'd and available.  Yes, there are some shiny improvements on the way, but there's plenty to be accomplished with the stack as it stands today.