OWASP Security Tools for Developers Project - Revision history

Kait Disney-Leugers at 16:48, 17 April 2014

2014-04-17T16:48:15Z

Paulo Coimbra at 13:41, 1 August 2011

2011-08-01T13:41:42Z

Mcurphey at 04:34, 1 August 2011

2011-08-01T04:34:53Z

Mcurphey at 02:06, 1 August 2011

2011-08-01T02:06:40Z

Mcurphey at 02:05, 1 August 2011

2011-08-01T02:05:17Z

Mcurphey at 19:49, 31 July 2011

2011-07-31T19:49:30Z

Mcurphey at 19:48, 31 July 2011

2011-07-31T19:48:28Z

Mcurphey at 19:28, 31 July 2011

2011-07-31T19:28:46Z

Mcurphey at 19:04, 31 July 2011

2011-07-31T19:04:31Z

Mcurphey at 18:49, 31 July 2011

2011-07-31T18:49:54Z

← Older revision		Revision as of 16:48, 17 April 2014
Line 1:		Line 1:
		+	{\|
		+	\|-
		+	! width="700" align="center" \| <br>
		+	! width="500" align="center" \| <br>
		+	\|-
		+	\| align="right" \| [[Image:OWASP Inactive Banner.jpg\|800px\| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]]
		+	\| align="right" \|
		+
		+	\|}
	==== Home ====		==== Home ====

← Older revision		Revision as of 13:41, 1 August 2011
Line 70:		Line 70:
	\|}		\|}

−	~~<br>~~ __NOTOC__ <headertabs />	+	==== Project About ====
		+
		+	{{:Projects/OWASP Security Tools for Developers Project \| Project About}}
		+
		+
		+	__NOTOC__ <headertabs />
		+
		+	[[Category:OWASP_Project\|Security Tools for Developers Project]] [[Category:OWASP_Tool]] [[Category:OWASP_Alpha_Quality_Tool]]

@@ Line 66: / Line 66: @@
 *December - Sprint 4
-In due course (when we have a backlog) well publish a roadmap.&nbsp;
+In due course (when we have a backlog) we will publish a roadmap.&nbsp;
 |}
 <br> __NOTOC__ <headertabs />

@@ Line 7: / Line 7: @@
 |- valign="top"
+|
-This project is focused on defining, designing, developing and configuring security tools for software developmemt teams and their end-to-end software development process. While any reference material or code produced will be focused an open source stack and Agile development techniques,&nbsp;the concepts should be able to be easily applied to other styles of software engineering.&nbsp;
+This project is focused on defining, designing, developing and configuring security tools for software development teams and their end-to-end software development process. While any reference material or code produced will be focused an open source stack and Agile development techniques,&nbsp;the concepts should be able to be easily applied to other styles of software engineering.&nbsp;
 Most people accept that tools can only effectively be applied to a fraction of software issues where the fraction is generally increasing but at a relatively conservative pace. Tools are however an important and widely adopted part of the process needed to produce functional, stable, reliable and scalable software where security is one attribute.&nbsp;Most development teams invest heavily in tools to improve their process and maintain end-to-end development environments including managing requirements and user stories, IDE's, test management, source code management, version control, continuous intregration, deployment and monitoring.
@@ Line 58: / Line 58: @@
 We are planning to run the project like an Agile software project itself by building a backlog and running sprints. We may even try and use Google Hangouts for video stand-up meetings!
 Our current timeline looks like:
 *August - Project Planning
@@ Line 66: / Line 66: @@
 *December - Sprint 4
 In due course (when we have a backlog) well publish a roadmap.&nbsp;
 |}
 <br> __NOTOC__ <headertabs />

@@ Line 9: / Line 9: @@
 This project is focused on defining, designing, developing and configuring security tools for software developmemt teams and their end-to-end software development process. While any reference material or code produced will be focused an open source stack and Agile development techniques,&nbsp;the concepts should be able to be easily applied to other styles of software engineering.&nbsp;
-Most people accept that tools can only effectively be applied to a fraction of software issues where the fraction is generally increasing but at a relatively conservative pace. Tools are however an important and widely adopted part of the process needed to produce fucntional, stable, reliable and scalable software where security is one such attribute.&nbsp;Most development teams invest heavily in tools to improve their process and maintain end-to-end development environments including managing requirements and user stories, IDE's, test management, source code management, version control, continuous intregration, deployment and monitoring.
+Most people accept that tools can only effectively be applied to a fraction of software issues where the fraction is generally increasing but at a relatively conservative pace. Tools are however an important and widely adopted part of the process needed to produce functional, stable, reliable and scalable software where security is one attribute.&nbsp;Most development teams invest heavily in tools to improve their process and maintain end-to-end development environments including managing requirements and user stories, IDE's, test management, source code management, version control, continuous intregration, deployment and monitoring.
-Many security tools today are written by and for security people who often (understandably)&nbsp;have a different lens and different needs from software developers and development teams.
+Most security tools today are written by and for security people who often (understandably)&nbsp;have a different lens and different needs from software developers and development teams.
 This project is operating under the belief that infusing security into the development teams work-flow through effective tools will have a significant impact on improving the security quality of the code they produce.<br>
-You can think of it as a project for developers by developers that just so happens to be about security.&nbsp;
+You can think of it as a project for developers by developers to improver software quality through better tooling that just so happens to be about security.&nbsp;
+|
@@ Line 33: / Line 33: @@
 [[Image:Asvs-bulb.jpg]]'''....join the discussion [https://lists.owasp.org/mailman/listinfo/owasp-std mailing list]'''
-While the project is open to all we are particularly loking for developers who will actively contributing code. We are especially interested in any developers that have experience of customizing Jenkins, extending Git, unit testing frameworks or customizing mangement tools like ScrumDo. We are also interested in any developers interested in extending behaviour driven development testing frameworks like Cucumber.&nbsp;
+While the project is open to all we are particularly looking for developers who will actively contribute code. We are especially interested in any developers that have experience in customizing Jenkins, extending Git, unit testing frameworks or customizing mangement tools like ScrumDo. We are also interested in any developers interested in extending behaviour driven development testing frameworks like JBehave.&nbsp;
 Join the mailing list, hang out and say hi or contact the project leader&nbsp;[mailto:mark@curphey.com?subject=OWASP%20STD%20Project Mark Curphey].
@@ Line 39: / Line 39: @@
 *[https://lists.owasp.org/mailman/listinfo/owasp-std mailing list]
-−
+|
 == What exactly are you producing?  ==
 [[Image:Asvs-bulb.jpg]]'''....the 50,000 ft plan'''
-The project is still in it's infancy but the plan is to produce the following:
+The project is still in its infancy but the plan is to produce the following:
 *Reference Architecture
@@ Line 58: / Line 57: @@
 We are planning to run the project like an Agile software project itself by building a backlog and running sprints. We may even try and use Google Hangouts for video stand-up meetings!
 *August - Project Planning
@@ Line 64: / Line 65: @@
 *November - Sprint 3
 *December - Sprint 4
 |}
 <br> __NOTOC__ <headertabs />

@@ Line 49: / Line 49: @@
 *Reference Implementation
-As part of those two key areas we expect to build or customize tools and develop configuration guides for particular technologies. While we don't yet know exactly what that will inlcude it may inlcude IDE plugins or extensions to common testing frameworks to make integrating security tests easier. &nbsp;<br>
+As part of those two key areas we expect to build or customize tools and develop configuration guides for particular technologies. While we don't yet know exactly what that will include it may include IDE plugins or extensions to common testing frameworks to make integrating security tests easier. &nbsp;<br>
+|

@@ Line 18: / Line 18: @@
+|
-[[Image:Asvs-ad-where-at.png]]
+[[Image:Owasp std.png]]
 |}
@@ Line 39: / Line 39: @@
 *[https://lists.owasp.org/mailman/listinfo/owasp-std mailing list (this is the main list)]
-−
+|
 == What exactly are you producing?  ==

@@ Line 31: / Line 31: @@
 == Wanna get involved?  ==
 [[Image:Asvs-bulb.jpg]]'''....join the discussion'''
 While the project is open to all we are particularly loking for developers who will actively contributing code. We are especially interested in any developers that have experience of customizing Jenkins, extending Git, unit testing frameworks or customizing mangement tools like ScrumDo. We are also interested in any developers interested in extending behaviour driven development testing frameworks like Cucumber.&nbsp;
-Join the mailing list, hang out and say hi or contact the project leader Mark Curphey&nbsp;[mailto:owasp@owasp.org contact us].
+Join the mailing list, hang out and say hi or contact the project leader&nbsp[mailto:mark@curphey.com?subject=OWASP%20STD%20Project Mark Curphey].
 *[https://lists.owasp.org/mailman/listinfo/owasp-std mailing list (this is the main list)]
@@ Line 64: / Line 64: @@
 *December - Sprint 4
 |}
 <br> __NOTOC__ <headertabs />