Thus, they shy away from investing in the solution. Add to that a lack of feature changes, and many have started to call it a dead duck. Though the extended support end date is, the mainstream support end date is. However, they have been wary to adopt due to the lack of nurturing and a fast-approaching end of support life. As advocates of deploying the Microsoft security stack to ease our Windows 10 upgrades and management, we have been trying to sell customers on using MBAM. The problem with MBAM has been it’s been a little neglected over the last few years. It’s a single use key which reduces the attack vector, ensuring that the recovery key retrieved by a user, in the self-service portal, and scribbled down on a post-it note stuck to the screen, quickly becomes obsolete. If a recovery key is used, then a new key is generated for the device. MBAM also provides something called key rotation. This way, if the device is removed from AD or AAD, then my recovery key is gone along with the object. MBAM separates the computer object from the recovery key. Why am I a big fan of MBAM? Well, it provides a more secure and feature driven solution to BitLocker management than the other solutions provided by Microsoft, specifically Active Directory (AD) key storage and Azure Active Directory (AAD) storage. deploy a self-service and helpdesk portal to allow BitLocker key recovery.check compliance of devices in the estate.MBAM is a solution that provides an admin interface for BitLocker drive encryption. For those of you who are unaware of what MBAM is, the official name is Microsoft BitLocker Administration and Monitoring.
0 kommentar(er)
