windows 11
3 Topics[On demand] How to protect your administrator users on the device
Get tips to help you enforce least privilege with Windows 11—and minimize the risk of admin users making a system-level change by mistake. Watch How to protect your administrator users on the device – now on demand – and join the conversation at https://aka.ms/ProtectAdminUsers. To help you learn more, here are the links referenced in the session: Admin experience: via Intune setting catalog – The feature is configurable in the LocalPoliciesSecurityOptions – policy CSP. Administrator protection on Windows 11 blog For more free technical skilling on the latest in Windows, Windows in the cloud, and Microsoft Intune, view the full Microsoft Technical Takeoff session list.56Views0likes0Comments[On demand] Data protection with hardware-based security and Windows 11
Do you know how to combine Windows 11 security features like Personal Data Encryption and BitLocker integrate with hardware features like TPM 2.0, Microsoft Pluton, and VBS to keep users and data protected? Watch Data protection with hardware-based security and Windows 11 – now on demand – and join the conversation at https://aka.ms/HardwareBasedSecurity. For more free technical skilling on the latest in Windows, Windows in the cloud, and Microsoft Intune, view the full Microsoft Technical Takeoff session list.53Views0likes0CommentsWindows Unquoted Service Path Enumeration - Is this still a case in modern Windows (10, 11) ?
Hi Folks, This could be irrelevant as the issue goes back to few years and Microsoft may have already fixed it but, just wanted verify/confirm. Windows Unquoted Path Enumeration vulnerability was identified back in 2013 (or may be even earlier). In simple terms, when a service is created whose executable path contains spaces and isn’t enclosed within quotes, leads to a vulnerability known as Unquoted Service Path which allows a user to gain SYSTEM privileges (only if the vulnerable service is running with SYSTEM privilege level which most of the time it is). In Windows, if the service is not enclosed within quotes and is having spaces, it would handle the space as a break and pass the rest of the service path as an argument. Ref - https://medium.com/@SumitVerma101/windows-privilege-escalation-part-1-unquoted-service-path-c7a011a8d8ae So my question is, is this still a vulnerability in the modern versions of Windows 10,11? Appreciate any inputs/recommendations!Solved111KViews0likes5Comments