Difference between revisions of "Projects/OWASP Alchemist Project"

From OWASP
Jump to: navigation, search
Line 5: Line 5:
 
| project_description =
 
| project_description =
  
*A large majority of software projects do not incorporate security from the word go. Alchemist intends to help solve this conundrum, by enabling a software development team in realization of highly secure and defensible application with built-in defenses/controls against security‐related design, coding and implementation flaws. Alchemist is focused to present this solution by way of architecting a real-life high stakes software application in J2EE (Spring/Struts) with security built into it right from the inception, step-by-step as it falls under an SDLC. Although this project is more than useful for existing/already developed applications, Alchemist is not the ideal solution to retrofit security into existing applications. It is aimed at offering more to applications that are at least in development, most in design phase. Allowing for language-specific differences, Alchemist builds this application with a strong foundation of security architecture that covers following main practices:
+
A large majority of software projects do not incorporate security from the word go. Alchemist intends to help solve this conundrum, by enabling a software development team in realization of highly secure and defensible application with built-in defenses/controls against security‐related design, coding and implementation flaws.  
**Security Requirements,
+
 
**Threat Risk Modeling,
+
Alchemist is focused to present this solution by way of architecting a real-life high stakes software application in J2EE on top of Spring framework with security built into it right from the inception, step-by-step as it falls under an SDLC. It is important to note that Alchemist is not limited to J2EE or more specifically Spring framework. The idea is to demonstrate the upper spectrum of security practices that are often neglected or are done in bits and pieces by picking a well known widely adopted framework. Spring framework was chosen due to its widespread adoption in the financial products. Since the emphasis is on security architecture and defensibility, the future road-map is to demonstrate the same for applications built on other programming languages and frameworks.
**Use and Abuse Cases,
+
 
**Secure Coding Guideline,
+
Although this project is more than useful for existing/already developed applications, Alchemist is not the ideal solution to retrofit security into existing applications. It is aimed at offering more to applications that are at least in development, most in design phase. Allowing for language-specific differences, Alchemist builds this application with a strong foundation of security architecture that covers following main practices:
 +
 
 +
*Security Requirements
 +
*Threat Risk Modeling
 +
*Use and Abuse Cases
 +
*Secure Coding Guideline
  
 
| project_license = [http://www.gnu.org/licenses/#GPL GNU General Public License]
 
| project_license = [http://www.gnu.org/licenses/#GPL GNU General Public License]

Revision as of 05:56, 5 September 2010

PROJECT INFO
What does this OWASP project offer you?
RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: OWASP Alchemist Project (home page)
Purpose: A large majority of software projects do not incorporate security from the word go. Alchemist intends to help solve this conundrum, by enabling a software development team in realization of highly secure and defensible application with built-in defenses/controls against security‐related design, coding and implementation flaws.

Alchemist is focused to present this solution by way of architecting a real-life high stakes software application in J2EE on top of Spring framework with security built into it right from the inception, step-by-step as it falls under an SDLC. It is important to note that Alchemist is not limited to J2EE or more specifically Spring framework. The idea is to demonstrate the upper spectrum of security practices that are often neglected or are done in bits and pieces by picking a well known widely adopted framework. Spring framework was chosen due to its widespread adoption in the financial products. Since the emphasis is on security architecture and defensibility, the future road-map is to demonstrate the same for applications built on other programming languages and frameworks.

Although this project is more than useful for existing/already developed applications, Alchemist is not the ideal solution to retrofit security into existing applications. It is aimed at offering more to applications that are at least in development, most in design phase. Allowing for language-specific differences, Alchemist builds this application with a strong foundation of security architecture that covers following main practices:

  • Security Requirements
  • Threat Risk Modeling
  • Use and Abuse Cases
  • Secure Coding Guideline
License: GNU General Public License
who is working on this project?
Project Leader(s):
how can you learn more?
Project Pamphlet: View
Project Presentation:
Mailing list: Mailing List Archives
Project Roadmap: View
Key Contacts
  • Contact the GPC to report a problem or concern about this project or to update information.
current release
Alchemist Secure J2EE Spring v1.0 - 13th January 2011 - (no download available)
Release description: A real-world banking application with 5 dynamic pages.
Rating: Yellow button.JPG Not Reviewed - Assessment Details
last reviewed release
Not Yet Reviewed


other releases