Security Code Inspection

From Guidance Share

(Difference between revisions)
Jump to: navigation, search
Revision as of 06:47, 6 March 2007 (edit)
Admin (Talk | contribs)

← Previous diff
Current revision (05:59, 13 December 2007) (edit)
JD (Talk | contribs)

 
Line 1: Line 1:
Security code inspection is an effective mechanism for uncovering security issues before testing or deployment begins. Performing code inspections help you reduce the number of implementation errors in an application before it is deployed to a test team or to a customer. While design issues are the most expensive to fix, implementation issues are the most common. Security code inspection is an effective mechanism for uncovering security issues before testing or deployment begins. Performing code inspections help you reduce the number of implementation errors in an application before it is deployed to a test team or to a customer. While design issues are the most expensive to fix, implementation issues are the most common.
 +----
=== Getting Started === === Getting Started ===
Line 6: Line 7:
-=== Resources ===+=== How To ===
* [[How To: Perform a Security Code Inspection for Managed Code (Baseline Technique)]] * [[How To: Perform a Security Code Inspection for Managed Code (Baseline Technique)]]
-* [[.NET Framework 2.0 Inspection Questions]]+ 
-* [[ASP.NET 2.0 Inspection Questions]]+ 
 +=== Inspection Questions ===
 +* [[.NET Framework 2.0 Security Inspection Questions]]
 +* [[ASP.NET 2.0 Security Inspection Questions]]

Current revision

Security code inspection is an effective mechanism for uncovering security issues before testing or deployment begins. Performing code inspections help you reduce the number of implementation errors in an application before it is deployed to a test team or to a customer. While design issues are the most expensive to fix, implementation issues are the most common.


Getting Started


How To


Inspection Questions

Personal tools