Least Privileges on SQL Server
I'm a long time subscriber to the notion that users shouldn't run as administrators. It may take some work for a developer to run as non-admin, but I believe that this is worth it. The issue is more than security, it's about forcing coding practices (my code never write to Program Files, buecase it simply not allowed on my machine). I had to make some modifications to the environment (enable debugging for my user, for instance), but it wasn't very hard.
One thing that I did run into is SQL Server. I don't want to use sa/blank, of course. I want to use Windows Authentication (since then at least my connection strings don't contain sensitive information, and I don't need to remember more passwords), but I don't want to give my user any more privileges that it absolutely must have. Right now I've settled on granting my user a db_creator on the server and db_owner for a couple of my databases.
I'm not sure if this is really the least privileges, but I'm currently doing a lot of SQL work, so I'm constantly doing stuff at the database level (restore, backup, drop, create, etc).
Comments
Comment preview