Specifically we look at Microsofts Azure AD and the linked Azure MFA service. Using an external Identity Provider (IdP) and the MFA services linked to this IdP.An MFA vendor/product such as Duo Security, OKTA MFA, … and many more.On the highest level, MFA can be added on top of RDP by using: is SMS as a token as secure as a time-based token generated on a phone?, etc. We’re not making any analysis (or judgement) on which MFA token generation is better than other in this blog: e.g.
Rather than comparing vendors, let’s look into the architecture, the complexity of setup and the cost elements in play. We’ll add some specific vendor solutions, but keep in mind that there are many players in this domain. The purpose of this post is to bring some structure into your options.
At Awingu, we also provided built-in MFA capabilities as part of the product since day 1. However, the opposite is true: the number of options in the MFA space are as plenty as there are fish in the ocean. You‘d think the fact that many businesses are not using MFA on top of the RDP today is because there is a lack of solutions. Note that this is one of but far from the only recommendation. One of the recommendations to protect RDP environment from getting hacked is to add MFA (Multi-Factor Authentication). And these attacks are not isolated: on average, the honeypot RDP environments are attacked every 11 hours. And these antics take can take place really, really fast…Ī “honeypot” experiment from Unit 42 in the summer of 2021 found that 80% (!) of its unprotected RDP setups was hacked within 24 hours. The UK NCSC (National Cyber Security Centre) has identified unprotected RDP to be the #1 reason for ransomware attacks (more on this topic). Unfortunately, using RDP in its simplest forms is a huge security risk.
RDP (Remote Desktop Protocol) is one of the most used technologies for access to server based applications or desktops and to enable remote user access.
0 kommentar(er)
