OWASP Alchemist Project - Revision history

Kait Disney-Leugers at 20:01, 23 January 2014

2014-01-23T20:01:09Z

Kait Disney-Leugers at 18:44, 23 January 2014

2014-01-23T18:44:01Z

Kait Disney-Leugers at 02:11, 23 January 2014

2014-01-23T02:11:25Z

Bishan Singh at 13:23, 8 September 2010

2010-09-08T13:23:07Z

Bishan Singh at 13:09, 8 September 2010

2010-09-08T13:09:33Z

Bishan Singh at 13:03, 8 September 2010

2010-09-08T13:03:10Z

Bishan Singh at 12:52, 8 September 2010

2010-09-08T12:52:45Z

Bishan Singh at 11:34, 5 September 2010

2010-09-05T11:34:52Z

Chandrakanth Reddy Narreddy at 09:19, 3 September 2010

2010-09-03T09:19:21Z

Bishan Singh at 04:28, 2 September 2010

2010-09-02T04:28:04Z

@@ Line 4: / Line 4: @@
 ! width="500" align="center" | <br>
 |-
-| align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/Category:OWASP_Project]]
+| align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]]
 | align="right" |

@@ Line 1: / Line 1: @@
-[[Image:OWASP Inactive Banner.jpg|1155px]]
+{|
 ==== Main ====
 While there are extensive resources on the Internet about secure architecture and security practices that when implemented effectively across an SDLC produce highly secure and defensible applications. One must acknowledge that their adoption has challenged project teams, one constraint being lack of reference implementations that demonstrate effective realization of highly secure and defensible applications.

← Older revision		Revision as of 02:11, 23 January 2014
Line 1:		Line 1:
		+	[[Image:OWASP Inactive Banner.jpg\|1155px]]
	==== Main ====		==== Main ====
	While there are extensive resources on the Internet about secure architecture and security practices that when implemented effectively across an SDLC produce highly secure and defensible applications. One must acknowledge that their adoption has challenged project teams, one constraint being lack of reference implementations that demonstrate effective realization of highly secure and defensible applications.		While there are extensive resources on the Internet about secure architecture and security practices that when implemented effectively across an SDLC produce highly secure and defensible applications. One must acknowledge that their adoption has challenged project teams, one constraint being lack of reference implementations that demonstrate effective realization of highly secure and defensible applications.

@@ Line 10: / Line 10: @@
 More details on the project, including the high level road-map can be found in the Project About tab. If you'd like to contribute join the [https://lists.owasp.org/mailman/listinfo/owasp-alchemist-project mailing list] and share your ideas and suggestions on the ongoing progress, and of course your proposal for contribution for the ongoing work or work for other programming languages.
 ==== Project About ====
 {{:Projects/OWASP_Alchemist_Project | Project About}}

@@ Line 10: / Line 10: @@
 More details on the project, including the high level road-map can be found in the Project About tab. If you'd like to contribute join the [https://lists.owasp.org/mailman/listinfo/owasp-alchemist-project mailing list] and share your ideas and suggestions on the ongoing progress, and of course your proposal for contribution for the ongoing work or work for other programming languages.
+''NOTE: This project has no sponsors. Please reach us if you wish to sponsor this initiative. Sponsorship goes a long way in speeding up our release cycles and of course spawning other reference implementations sooner than later.
 ==== Project About ====
 {{:Projects/OWASP_Alchemist_Project | Project About}}

@@ Line 4: / Line 4: @@
 Alchemist aims to bridge this gap. Alchemist is a free, open source, enterprise web application security resource that enables software development teams build high secure and defensible applications. Alchemist is structured for easier adoption and learning for software architects and programmers, allowing them to implement strong security practices into their applications.
-The focus is to achieve this objective by architecting and developing a highly secure and defensible enterprise web application. The outcome of this exercise is targeted as a reference implementation for development houses. The overall  objective is to showcase, leveraging secure architecture and practices, secure development implementations with leading technologies and frameworks. In its first exercise, Alchemist proposes to demonstrate a secure J2EE web application that is developed using Spring framework.
+The focus is to achieve this objective by architecting and developing a highly secure and defensible enterprise web application. The outcome of this exercise is targeted as a reference implementation for development houses. The overall  objective is to leverage secure architecture and practices to showcase secure application development implementations with leading technologies and frameworks. In its first exercise, Alchemist proposes to demonstrate a secure J2EE web application that is developed using Spring framework.
 OWASP lists a number of common application security [[:Category:Vulnerability|vulnerabilities]]. These apply to most of the programming languages and platforms. The notable exception being [[Buffer Overflow|buffer overflow]] and related issues that do not apply to J2EE. .Net and the likes. Alchemist is designed to demonstrate effective mitigation of most of these issues in its reference implementations.