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 "Project Information:template Teachable Static Analysis Workbench"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
 +
{| style="width:100%" border="0" align="center"
 +
! colspan="8" align="center" style="background:#4058A0; color:white"|<font color="white">'''PROJECT IDENTIFICATION'''
 +
|-
 +
| style="width:15%; background:#7B8ABD" align="center"|'''Project Name'''
 +
| colspan="7" style="width:85%; background:#cccccc" align="left"|<font color="black">'''OWASP Teachable Static Analysis Workbench Project'''
 +
|-
 +
| style="width:15%; background:#7B8ABD" align="center"| '''Short Project Description'''
 +
| colspan="6" style="width:85%; background:#cccccc" align="left"|The research will be intended to answer the following questions:
 +
* Can we integrate existing open source static analysis tools (OWASP and third-party) to work altogether? We plan analysis to cover the following tools: LAPSE, Orizon, ESAPI, FindBugs.
 +
* How static analysis workbench can be taught by security analyst?
 +
* How static analysis workbench can support web-applications built using MVC frameworks?
 +
Workbench prototype will be Java-based Eclipse plug-in which aim is to help security analyst/code reviewer validation of web application. At prototype step we suggest to analyze J2EE Web tier applications build on Java Servlets, JSP (without business logic in it) and one MVC framework (Apache Struts). We plan workbench prototype to have the following functionality:
 +
* Input validation vulnerabilities analysis: identification of web application entry points (aka attack surface in P024), call graph for each entry point (see “Packages -> Classes -> Methods -> callsites” in P023), identification of data validation routines, teachable taint analysis.
 +
* Authentification and access control analysis: identification of code related to access control and it’s analysis.
 +
* Pattern-based code analysis.
 +
* Teachability: analyst indicates security-related code (sources of tainted data, sensitive sinks, input validation and sanitizing functions, access control code, etc.) and workbench automatically recomputes possible vulnerabilities list. The second idea is to spread knowledge gathered from analyst to other web applications.
 +
|-
 +
| style="width:15%; background:#7B8ABD" align="center"|'''Key Project Information'''
 +
| style="width:14%; background:#cccccc" align="center"|Project Leader<br>[[:User:Ddk|Dmitry Kozlov]]<br>[mailto:igor.konnov(at)gmail.com '''Igor Konnov''']
 +
| style="width:14%; background:#cccccc" align="center"|Project Contributors<br>(if applicable)
 +
| style="width:14%; background:#cccccc" align="center"|Mailing List<br>[https://lists.owasp.org/mailman/listinfo/owasp-teachable-static-analysis-workbench '''Subscribe here''']<br>[mailto:owasp-teachable-static-analysis-workbench(at)lists.owasp.org '''/Use here''']
 +
| style="width:14%; background:#cccccc" align="center"|License<br>[http://creativecommons.org/licenses/by-sa/3.0/ '''Creative Commons Attribution Share Alike 3.0''']
 +
| style="width:14%; background:#cccccc" align="center"|Project Type<br>[[:Category:OWASP_Project#Alpha_Status_Projects|'''Tool''']]
 +
| style="width:15%; background:#cccccc" align="center"|Sponsors<br>[[OWASP Summer of Code 2008|'''OWASP SoC 08''']]
 +
|}
 +
 +
{| style="width:100%" border="0" align="center"
 +
! align="center" style="background:#7B8ABD; color:white"|<font color="black">'''Release Status'''
 +
! align="center" style="background:#7B8ABD; color:white"|<font color="black">'''Main Links'''
 +
! align="center" style="background:#7B8ABD; color:white"|<font color="black">'''Related Projects'''
 +
|-
 +
| style="width:29%; background:#cccccc" align="center"| '''[[:Category:OWASP_Project_Assessment#Beta_Quality_Documentation_Criteria|Beta Quality]]'''<br>[[:Teachable Static Analysis Workbench - Assessment Frame|Please see here for complete information.]]
 +
| style="width:42%; background:#cccccc" align="center"|
 +
http://code.google.com/p/teachablesa/<br>[https://www.owasp.org/images/6/69/Teachable_static_analysis_workbench.pptx PowerPoint Presentation]
 +
| style="width:29%; background:#cccccc" align="center"|
 +
If any, add link here
 +
|}
 +
 +
 +
 +
 +
 
{| style="width:100%" border="0" align="center"
 
{| style="width:100%" border="0" align="center"
 
  ! colspan="7" align="center" style="background:#4058A0; color:white"|<font color="white">'''PROJECT IDENTIFICATION'''  
 
  ! colspan="7" align="center" style="background:#4058A0; color:white"|<font color="white">'''PROJECT IDENTIFICATION'''  

Revision as of 16:59, 14 January 2009

PROJECT IDENTIFICATION
Project Name OWASP Teachable Static Analysis Workbench Project
Short Project Description The research will be intended to answer the following questions:
  • Can we integrate existing open source static analysis tools (OWASP and third-party) to work altogether? We plan analysis to cover the following tools: LAPSE, Orizon, ESAPI, FindBugs.
  • How static analysis workbench can be taught by security analyst?
  • How static analysis workbench can support web-applications built using MVC frameworks?

Workbench prototype will be Java-based Eclipse plug-in which aim is to help security analyst/code reviewer validation of web application. At prototype step we suggest to analyze J2EE Web tier applications build on Java Servlets, JSP (without business logic in it) and one MVC framework (Apache Struts). We plan workbench prototype to have the following functionality:

  • Input validation vulnerabilities analysis: identification of web application entry points (aka attack surface in P024), call graph for each entry point (see “Packages -> Classes -> Methods -> callsites” in P023), identification of data validation routines, teachable taint analysis.
  • Authentification and access control analysis: identification of code related to access control and it’s analysis.
  • Pattern-based code analysis.
  • Teachability: analyst indicates security-related code (sources of tainted data, sensitive sinks, input validation and sanitizing functions, access control code, etc.) and workbench automatically recomputes possible vulnerabilities list. The second idea is to spread knowledge gathered from analyst to other web applications.
Key Project Information Project Leader
Dmitry Kozlov
Igor Konnov 		Project Contributors
(if applicable) 		Mailing List
Subscribe here
/Use here 		License
Creative Commons Attribution Share Alike 3.0 		Project Type
Tool 		Sponsors
OWASP SoC 08
Release Status Main Links Related Projects
Beta Quality
Please see here for complete information.

http://code.google.com/p/teachablesa/
PowerPoint Presentation

If any, add link here



PROJECT IDENTIFICATION
Project Name OWASP Teachable Static Analysis Workbench Project
Short Project Description The research will be intended to answer the following questions:
  • Can we integrate existing open source static analysis tools (OWASP and third-party) to work altogether? We plan analysis to cover the following tools: LAPSE, Orizon, ESAPI, FindBugs.
  • How static analysis workbench can be taught by security analyst?
  • How static analysis workbench can support web-applications built using MVC frameworks?

Workbench prototype will be Java-based Eclipse plug-in which aim is to help security analyst/code reviewer validation of web application. At prototype step we suggest to analyze J2EE Web tier applications build on Java Servlets, JSP (without business logic in it) and one MVC framework (Apache Struts). We plan workbench prototype to have the following functionality:

  • Input validation vulnerabilities analysis: identification of web application entry points (aka attack surface in P024), call graph for each entry point (see “Packages -> Classes -> Methods -> callsites” in P023), identification of data validation routines, teachable taint analysis.
  • Authentification and access control analysis: identification of code related to access control and it’s analysis.
  • Pattern-based code analysis.
  • Teachability: analyst indicates security-related code (sources of tainted data, sensitive sinks, input validation and sanitizing functions, access control code, etc.) and workbench automatically recomputes possible vulnerabilities list. The second idea is to spread knowledge gathered from analyst to other web applications.
Email Contacts Project Leader
Dmitry Kozlov
Igor Konnov 		Project Contributors
(if applicable)
Name&Email 		Mailing List/Subscribe

Mailing List/Use

First Reviewer
Alex Fry
Profile 		Second Reviewer
Michael Coates 		OWASP Board Member
(if applicable)
Name&Email
PROJECT MAIN LINKS
SPONSORS & GUIDELINES
Sponsor - OWASP Summer of Code 2008 Sponsored Project/Guidelines/Roadmap
ASSESSMENT AND REVIEW PROCESS
Review/Reviewer Author's Self Evaluation
(applicable for Alpha Quality & further) 		First Reviewer
(applicable for Alpha Quality & further) 		Second Reviewer
(applicable for Beta Quality & further) 		OWASP Board Member
(applicable just for Release Quality)
50% Review Objectives & Deliveries reached?
Yes
---------
See&Edit:50% Review/Self-Evaluation (A) 		Objectives & Deliveries reached?
Yes
---------
See&Edit: 50% Review/1st Reviewer (C) 		Objectives & Deliveries reached?
Yes
---------
See&Edit: 50%Review/2nd Reviewer (E) 		X
Final Review Objectives & Deliveries reached?
Yes
---------
Which status has been reached?
Season of Code - (To update)
---------
See&Edit: Final Review/SelfEvaluation (B) 		Objectives & Deliveries reached?
Yes
---------
Which status has been reached?
Season of Code - (To update)
---------
See&Edit: Final Review/1st Reviewer (D) 		Objectives & Deliveries reached?
Yes
---------
Which status has been reached?
Season of Code - (To update)
---------
See&Edit: Final Review/2nd Reviewer (F) 		X

Retrieved from "https://wiki.owasp.org/index.php?title=Project_Information:template_Teachable_Static_Analysis_Workbench&oldid=51180"