AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Does desktop destroyer need admin rights12/15/2023 Give up and let developers run as full admins all the time.Sometimes easing the multiple elevation log-ons is all it takes to satisfy both sides. Require an authentication method for elevation that isn't as problematic as long, complex passwords - for example, biometrics or a smartcard and PIN.This removes the need for elevation altogether. Modify the developer workstreams and tasks so that they don't require elevation all the time, such as modifying registry and file permissions.If using Windows, modify UAC (user account control) to do silent elevation (pretty insecure, but a choice).Let developers use privilege management software, which can automatically elevate pre-assigned development tasks.I've seen this used a fair amount in big companies, but it has lots of exploit opportunities. Create a custom app service where the developer can request elevated credentials or a particular predefined application or task for a certain period of time.Let developers be full admins only on a local virtual instance that has no access to the local network or Internet.The admin box should be network shunted and allowed access to only the necessary resources. The other can be their normal computer that they use with the nonadmin account. They should use only the admin account on the developer box, which is locked down. Give developers two separate accounts, one regular and one admin, and two different computers. With that said, here are solutions I've seen in the real world. It depends on the company's operational goals and priorities, as well as its risk tolerances. This is a necessary side effect of improving security.īeyond that, there's no single solution to the developer dilemma. How do you satisfy both sides? First, you need to recognize that the world where everyone is an administrator is gone forever - and whatever the solution, it won't be as convenient. But much of what developers do (such as installing drivers, writing to system directories, running installation programs, and so on) absolutely requires admin rights and permissions, and without them, productivity drops. The rationale is obvious: Limiting the number of administrators reduces security risk and makes it harder for successful exploitations to occur and for attackers to do bad things if they are successful. Not only are they being forced to develop applications in which users will not always have admin rights, but the dastardly system administrators aren't letting developers run with full administrator rights all the time, either. Almost every customer I deal with has unhappy developers who feel constrained.
0 Comments
Read More
Leave a Reply. |