This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of ".NET Security for Developers"
From OWASP
(→Areas of Concern) |
(→References) |
||
| Line 34: | Line 34: | ||
===References=== | ===References=== | ||
| − | + | [http://www.microsoft.com/downloads/details.aspx?familyid=2412c443-27f6-4aac-9883-f55ba5b01814&displaylang=en&Hash=4fZb2FzZ7%2bmaj0VqoUbFZzzw0WW5%2bxWjK3XBVit5eX%2b%2bB90vmLtZlAstlNg9cRu6Pg%2b50DNCMhGT6ADei7DgFg%3d%3d Microsoft Security Development Lifecycle 3.2] | |
===Tools=== | ===Tools=== | ||
[http://www.owasp.org/index.php/Source_Code_Audit_Tools Source Code Analysis Tools] | [http://www.owasp.org/index.php/Source_Code_Audit_Tools Source Code Analysis Tools] | ||
Revision as of 01:24, 16 April 2008
.NET Security for Developers
Developers are responsible for creating secure, trustworthy web applications and services. This section is to provide tools and guidance for the .NET Developer.
Areas of Concern
- Secure Coding
- Partial Trust
- Cross Platform
- Confidentiality, Integrity and Availability in Practice
- Cryptography
- Debugging and Instrumentation
- Adaptive Web Applications and failing gracefully
- Security Features
- Authentication Best Practices
- Authorization
- Security Demands
- Unit Testing
- Test First (TDD) and Design Patterns
- Fuzzing
- .NET Web Technologies
Articles
"How Do I?" Microsoft Security Videos
Community Contributions
Developing ASP.NET in Partial Trust
References
Microsoft Security Development Lifecycle 3.2
