View source for OWASP Testing Project v3 Review Roadmap

'''This page track all the update to the Testing Guide v3 during the Reviewing phase.'''<br>

In particular the focus is:<br>
- Review the content of each article<br>
- Review the english sintax<br>
- no "attacker", better "tester"<br>
- no "we describe", but "it is described"<br>

Official Testing Guide Reviewers are:
* Nam Nguyen
* Kevin R.Fuller
* if you want to review it add your name please and keep track of updating

'''Nam Review:'''
----
Aug 31, 2008
* Appendix D
* Appendix C
* Appendix B
* Appendix A
* Chapter 5
** [[How to write the report of the testing]]
*** ``TO UPDATE WITH V3 controls`` is still in the article. Has it been updated to v3? '''(Mat: I'm updating it, thanks)'''
* Chapter 4
** Section 4.11 [[Testing for AJAX Vulnerabilities]]
*** There are mentioning of "attackers" but I think they are fine.
*** The subsection on Memory leaks is not complete.
** Section 4.11 [[Testing for AJAX]]
*** The subsection "Intercepting and Debugging JS code with Browsers" is very difficult to understand. I tried to fix it, but I'm afraid what I have might not reflect what the original author wanted to express.

Sep 02, 2008
* Chapter 4
** Section 4.10
*** Subsection [[Testing for WS Replay]] Gray box testing and examples gives incomplete sample code. I believe the call to GetSessionIDMac() missed four parameters. In this same part, using SSL helps in preventing replay attack but it doesnt prevent replay attack by itself. In this same subection, the images show identifiable real Internet address in Hungary, should them be masked off?

Sep 04, 2008
* Chapter 4
** Section 4.9
** Section 4.8
*** I'm not sure if format string could be classified under subsection 4.8.14 "Buffer overflow testing".
*** Subsecion 4.8.3: Incomplete
*** Subsection 4.8.4: Incomplete
*** Subsection 4.8.5: What is "data-plane input"?

Sep 06, 2008
* Chapter 4
** Section 4.8

Sep 07, 2008
* Chapter 4
** Section 4.7
** Section 4.6
*** Subsection 4.6.1: "Review code for path traversal" does not exist in the Code Review Guide, or the link the broken.
** Section 4.5

Sep 10, 2008
* Chapter 4
** Section 4.4
** Section 4.3
** Section 4.2
** Section 4.1
* Chapter 3
* Chapter 2
* Chapter 1
** [[Testing Guide Frontispiece]] still shows v2 editors and reviewers
** [[About The Open Web Application Security Project]] The link to the printed edition of the book is invalid. This page is a generally shared wiki page among all projects.


'''Kevin Review:'''
----
August 27/28th
articles reviewed<br><br>
1. Frontispiece<br>
1.1 About the OWASP Testing Guide Project<br> 
<br>
1.2 About The Open Web Application Security Project<br> 
<br>
2. Introduction<br>
2.1 The OWASP Testing Project<br> 
2.2 Principles of Testing<br> 
2.3 Testing Techniques Explained <br>
2.4 Security requirements test derivation,functional and non functional test requirements,<br> 
and test cases through use and misuse cases<br> 
2.4.1 Security tests integrated in developers and testers workflows<br> 
2.4.2 Developers' security tests: unit tests and component level tests<br> 
2.4.3 Functional testers' security tests: integrated system tests, tests in UAT, and production environment<br> 
2.5 Security test data analysis and reporting: root cause identification and business/role case test data reporting<br> 
<br>
3. The OWASP Testing Framework<br>
3.1. Overview<br> 
3.2. Phase 1: Before Development Begins<br> 
3.3. Phase 2: During Definition and Design<br> 
3.4. Phase 3: During Development<br> 
3.5. Phase 4: During Deployment<br> 
3.6. Phase 5: Maintenance and Operations<br> 
3.7. A Typical SDLC Testing Workflow<br>
<br> 
4.Web Application Penetration Testing<br> 
4.1 Introduction and Objectives<br> 
4.1.1 Testing Checklist<br> 
4.2 Information Gathering<br> 
4.2.1 Spiders, Robots and Crawlers<br> 
4.2.2 Search Engine Discovery/Reconnaissance<br> 
4.2.3 Identify application entry points<br> 
4.2.4 Testing for Web Application Fingerprint<br> 
4.2.5 Application Discovery<br> 
4.2.6 Analysis of Error Codes<br> 
4.3 Configuration Management Testing<br> 
4.3.1 SSL/TLS Testing (SSL Version, Algorithms, Key length, Digital Cert. Validity)<br>
4.3.2 DB Listener Testing<br> 
4.3.3 Infrastructure Configuration Management Testing<br> 
4.3.4 Application Configuration Management Testing<br>
<br> 
* I was concerned about the structure and flow of this section.  It did not read cleanly for me and appeared more "wordy" then the other sections. The format also did not appear to be consistent with the other sections resulting in a disjointed feeling when reading it.<br>
4.3.5 Testing for File Extensions Handling<br> 
4.3.6 Old, Backup and Unreferenced Files<br> 
<br>
03 September, 2008<br>
4.1 Introduction and Objectives<br> 
4.1.1 Testing Checklist<br> 
4.2 Information Gathering<br> 
4.2.1 Spiders, Robots and Crawlers<br> 
4.2.2 Search Engine Discovery/Reconnaissance<br> 
* Changed "GoogleBot" to the "GoogleBot"<br>
4.2.3 Identify application entry points<br> 
4.2.4 Testing for Web Application Fingerprint<br> 
4.2.5 Application Discovery<br> 
<br><br>

10 September, 2008<br>
4.3.7 Infrastructure and Application Admin Interfaces<br> 
4.3.8 Testing for HTTP Methods and XST<br> 
* Grammer change in the section "Arbitrary HTTP Methods". Changed "and / or" to "and/or"
* Grammer change in section "Test XST Potential"  andded a space between bullet number 1 and 2 and the text.

4.4 Business Logic Testing 
* The section read out a little longer then the other sections.  All the content was interestinga nd relevant.  I would suggest taking Example 2 and breaking it out into another example (Example 2.1 or 3?)in order to break up the flow. I found my self losing my train of thought the further I read into it

4.5 Authentication Testing
*What is "provenance"? It might be better to use adifferent, more common word with the same meaning.  An average user might get confused if they do not know what it means. 
4.5.1 Credentials transport over an encrypted channel 
*  I made several grammar related changes (commas and is vs are)and one content change.  Please crosscheck to insure the context is the same and check for additional grammar issues.
4.5.2 Testing for user enumeration 
Questions: (Mat will answer it)<br>