Discusses security from the perspective of the developer, end user, and administrator, as well as the benefits of using the security features provided by the Microsoft .NET Framework.

Describes some issues to consider regarding security best practices for Visual Studio Tools for Office solutions, including adding conditions to security policy, checking the current policy, setting default policy.

Provides recommendations to help you use the security features provided by the Microsoft .NET Framework and Microsoft Office 2003 to help protect against possible security threats.

Describes how to use the Microsoft .NET Framework 2.0 Configuration tool or the Code Access Security Policy tool (Caspol.exe) to change security settings for the purpose of developing assemblies on your own computer.

Describes the two methods you can use to remove trust from folders and assemblies.

Discusses how you can use the Office Document Membership Condition to grant permissions only to the documents and workbooks that are in a specific location, rather than to all content, if the location is not secure, or if you are not sure who has permission to upload content.

Demonstrates step-by-step how to remove the default permissions granted during project creation and add permissions based on strong name.

Provides links to other topics in Visual Studio that discuss security risks, as well as techniques used to help prevent unauthorized access to your applications and ensure data integrity.

Provides links to information on what is needed to create projects using Visual Studio Tools for Office.

Provides information about deploying Word or Excel documents to users, including issues involved in choosing a local or network deployment model as well as security considerations.

Provides links to information on how Visual Studio Tools for Office solutions work, including information on the custom document properties, the data model, and the Runtime Storage Control.