Best Practices for Security in the Visual Studio SDK
You need to understand security for VSPackage extensions so that you can create the best products possible.
A secure product helps protect the following:
The confidentiality, integrity, and availability of a customer's information.
The integrity and availability of the resources controlled by the system owner or administrator.
A security vulnerability is a weakness in a product that makes it impossible to prevent an attacker's malicious activities, even when the product is used correctly. Here are some examples:
Obtaining permissions on a computer that are higher than those of the user.
Taking over the operation of a user's computer.
Compromising data on a user's computer.
Never assume that your application will be run only in specific environments. Your application might be used in settings that you did not expect, especially when the application becomes popular. You should assume instead that your code will run in hostile environments, and design, write, and test your code accordingly.
Products and systems that have been designed and built with security as a prime feature are more robust than those written with security as an afterthought. Secure products are also more immune to media criticism, more attractive to users, and less expensive to and support and upgrade.
Calls to some functions can produce unwanted security vulnerabilities if they are used incorrectly, banning their use does not necessarily produce secure code. Nevertheless, some software projects have obtained measurable gains in security by banning functions that are difficult to use safely, as one of many secure-development practices. For more information, see Appendix A of the Microsoft Press book, "Writing Secure Code" by Michael Howard and David LeBlanc.
Most security issues result from trusting input without adequately verifying it. Make sure that you trace data as it comes into your code and question the implications of operations on that data. You can write secure code by using most functions if the data inputs are well-formed and checked for trustworthiness.
The User Account Control (UAC) feature has security implications that you should understand. It reduces the exposure of the operating system and applications to malicious attacks.
For more information about UAC on Windows 7, see What is User Account Control?.
For more information about UAC on Windows 8, see What are User Account Control settings?.
Before the advent of UAC, developers typically ran Visual Studio under administrator permissions even when they were not required. You should do your development and testing of your extension as a normal user, so you can make sure it does not require elevated rights unnecessarily.
Note that UAC also affects deployment. Installation packages must be correctly authored to support UAC. An incorrectly authored package typically causes "access denied" errors because the installer tries to use normal user rights to perform a task that requires elevated rights.