Category:OWASP .NET Project

The .NET Project is principally about creating deep, rich guidance for NET developers using the Microsoft .NET Framework's security resources.

Detailed Guidance

The following articles describe specific guidance for working with the .NET Framework.

• The .NET Security Cheat Sheet
• .NET Penetration Testing
• Exception Handling
• ASP.NET Request Validation
• ASP.NET Output Encoding
• Using Rfc2898DeriveBytes for PBKDF2
• Anti CSRF Tokens ASP.NET
• Adding two-factor authentication to ASP.NET

Security Guidance

The following sections include general content that can be useful for a specific role in securing .NET web applications and services:

• .NET Security Cheat Sheet
• .NET Penetration Testing
• Deserialization Cheat Sheet

The following sections include specific guidance for particular technological problems related to .NET web applications and services:

• Exception Handling
• ASP.NET Request Validation
• ASP.NET Output Encoding

Components

• ESAPI.NET
• .Net CSRF Guard
• AntiSamy .NET
• .NET AntiXSS Library
• Add Two-Factor to MVC

Recommended Resources

Check out the OWASP .NET Recommended Resources wiki page for a quick list of resources available now for secure .NET development:

OWASP .NET Recommended Resources

Active Projects

OWASP .NET Active Projects

Research Projects

OWASP .NET Research

Overview

The .NET Framework has seen significant security improvement over the last ten years of development. With proper use the core security problems that are seen in web applications, or even Windows executibles, are difficult to exploit.

The key is 'proper use' and that is the goal of the .NET Project - assist with proper use. Education, components and tools that are appropriate for the latest .NET versions should be the focus for output of this project. As tools and information become out of date, they will be moved to a sunset mode, still available to those using older versions of the framework.

Themes

The themes of the .NET Project include:

• Deep, rich guidance for .NET developers using the security features of .NET
• Access to use of OWASP components that are designed for use with .NET
• Information about working with and on OWASP tools built using .NET

Features

Features are parts of the project at a very high level. There are three themes, and they include guidance for developers, components that help to write more secure .NET projects, and tools for general security and testing written in .NET.

Guidance

Guidance is documentation that assists .NET developers implementing the security features of the framework.

In-process guidance

• Windows Identity Foundation
• .NET Memory Management
• Adding two-factor authentication to ASP.NET

Needed guidance

• ASP.NET Identity
• DPAPI
• ClickOnce Deployment
• .NET Callbacks - Vulnerabilities and Remediation
• Dependency Injection
• IoC containers
• Preventing SQL Injection in ADO.NET
• Authenticated Symmetric Encryption in .NET

Components

Components are pieces of software that assist .NET developers in building more secure code. A number of projects exist that are for older versions of .NET. While they are no longer valid for later versions, they are still acceptable for use. Many updates are needed to a number of other projects.

Needed Components

Please suggest needed components.

Projects that use .NET

These are projects that happen to be built in .NET. Many of them could use .NET development assistance:

• OWASP O2 Platform
• WebGOAT.NET

Ideas

Please send your ideas to the OWASP.Net mailing list (owasp-dotnet@lists.owasp.org)

Timeline

• January 2016 - Added the Two Factor Authentication component
• January 2015 - Three more completed articles, and four in progress
• November 2014 - Four completed articles, six in process.
• September 2014 - AppSec USA
• March 2014 - Project Roadmap
• February - 2014 Project Reboot
• May 2009 - Updated tabs, added content recommended by Andre Gironda
• March 2009 - Converted to new tab format, added Project Tracker tab
• February 2009 Added OWASP .NET Research and removed OWASP .NET Vulnerability Research from project page.

Roadmap

You can find the project roadmap here: OWASP .Net Project Roadmap

Questions and answers

Q1

Why are there so many empty projects?

A1

Because YOU haven't worked on them! We need your help!

Q2

Why the focus on specific implementation, rather than on general security? I just need general guidance!

A2

General guidance is platform independent. You should start with the awesome Cheat Sheets for general information. We are focused on specific implementation because these are the tough, unanswered questions that lead to the high risk vulnerabilities.

Q3

Where are the .NET specific security tools.

A3

Nearly everything you need is already in the .NET Framework. It's just a matter of learning where it is and how to use it. That's where the .NET project comes in.

Get involved

To get involved join the mailing list (see How to join Owasp.Net Mailing List)

Already involved

The OWASP .NET project is developed by a worldwide team of volunteers. The original primary contributor is Daniel Brzozowski. Currently the team of advisers and authoors includes:

• Kevin Basista
• Brice Williams
• Marion Nepomuceno
• Dan Wilson
• Jess Vermont
• Jeff Knutson
• Robert Ginsburg
• Kyle Johnson
• Troy Hunt
• Dinis Cruz
• Shamir Charania
• Mohammed Al-Taweel
• Daniel Brzozowski
• Lachlan Barclay
• Bill Sempf
• Barry Dorrans (Microsoft)
• Reid Borsuk (Microsoft)

We need more help. Please join the low volume mailing list at this address to get project announcements.