![]() Neither of the above is clearly a good option, so what’s the solution? Windows Subsystem for Linux (WSL) 2 Or we could just block everything and stop the productivity of our developers. It only requires a simple user error to install some virus or otherwise malicious program and the computer is comprimised. The same Windows client that has access to all company resources. The problem is that developers get exceptions to run this in their standard domain-joined Windows clients. ![]() The main issue is not that developers need to execute/install unsigned or generally untrusted tools and compile and execute code. If most of these are exluded from the standard security we have a major issue. From personal experience I see that They are often excluded from the overall security measures or just not joined into the domain at all.Īccording to Stack Overflow about 45% of people identifying as ”Professional Developers” run Windows as their main desktop operating system. Due to this problem businesses often look the other way when it comes to developers and their clients. This can sometimes be an problem when working with developer tools. ![]() ![]() Like most of the users in the world, I’m running a Managed Window 10 client, we enforce many polices such as applocker and more to enforce policies. : Hyper-V, Linux, Microsoft, Other, Powershell, Ubuntu, Windows By Vikingur Saemundsson Translate with Google ⟶
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |