Related Projects
← Older revision
Revision as of 11:44, 6 November 2014
(9 intermediate revisions by the same user not shown)
Line 6:
Line 6:
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |
−
<span style
=
"color:#ff0000">
+
=
=OWASP Secu-RT Project==
−
Instructions are in RED text and should be removed from your document by deleting
the
text with the span tags
. This
document is intended
to
serve as an example of what is required of an OWASP project wiki page. The text
in
red serves
as
instructions, while the text in black serves as an example. Text in black is expected to
be
replaced entirely with information specific
to
your OWASP project
.
+
The OWASP Secu-RT Project is an attempt to use
the
JVM itself for taint tracking
.
This
project started by a challenge given
to
me at Appsec EU conference
in
Hamburg
as
I said that it should
be
possible
to
do dynamic source-sink analysis in basic Java applications
.
My challengers then told me:
"
Prove it
"
. It took a while
,
but fairly soon I had a simple setup in which I demonstrated simple Log manipulation on
the
commandline and that it
was
detectable
.
This
project
is
the
continuation
of that
proof and
is
aimed at developers to help them detect
security
vulnerabilities using live source-sink analysis
.
It
is
dependent on
the
code coverage
and
not aimed to
be
used in
a
production environment
.
−
</span>
+
−
+
−
==OWASP Code Project Template==
+
−
<span style=
"
color:#ff0000
"
>
+
−
This section should include an overview of what the project is
,
why
the
project
was
started, and what security issue is being addressed by the project deliverable
.
Some readers may be discouraged from looking further at the
project
if they do not understand
the
significance
of
the security concern
that is
being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing
security
terminology, e
.
g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.
+
−
</span>
+
−
+
−
The OWASP Code Template Project
is
a template designed to help Project Leaders create suitable project pages for OWASP Projects. By following
the
instructional text in red (
and
then deleting it) it should
be
easier to understand what information OWASP and the project users are looking for. And it's easy to get started by simply creating
a
new project from the appropriate project template
.
+
==Description==
==Description==
−
<span style="color:#ff0000">
+
This
project aims
to
provide an invisible source-sink analyser/taint tracker
.
It will do this by knowing
the
various sources
and
sinks in each JVM language and displays
the
full trace of
a
string
that
entered through a source
and
exits unmanaged at
a
sink
.
−
This
is where you need
to
add your more robust project description
.
A project description should outline the purpose of
the
project, how it is used,
and the
value it provides to application security. Ideally, project descriptions should be written in such
a
way
that
there is no question what value the project provides to the software security community. This section will be seen
and
used in various places within the Projects Portal. Poorly written project descriptions therefore detract from
a
project’s visibility, so project leaders should ensure that the description is meaningful
.
+
−
</span>
+
−
The Code Project Template is simply a sample
project
that was developed for instructional purposes that can be used to create default project pages for a Code project. After copying this template to your new project, all you have to do
is
follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red. Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category. The information requested is also
intended to
help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort.
+
This
project is
not
intended to be
used in
a
production environment
,
but as an aid in testing
the security
flow during the QA phase
.
−
+
−
Creating a new set of project pages from scratch can
be a
challenging task. By providing a sample layout, with instructional text and examples
, the
OWASP Code Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote
security.
+
==Licensing==
==Licensing==
−
<span style="color:#ff0000">
−
A project must be licensed under a community friendly or open source license. For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses OWASP Licenses]. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects. This example assumes that you want to use the AGPL 3.0 license.
−
</span>
−
−
This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html link GNU Affero General Public License 3.0] as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. OWASP XXX and any contributions are Copyright © by {the Project Leader(s) or OWASP} {Year(s)}.
+
This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html link GNU Affero General Public License 3.0] as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. OWASP XXX and any contributions are Copyright © by Steven van der Baan 2014
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
== Project Resources ==
== Project Resources ==
−
<span style="color:#ff0000">
+
[https://github.com/
vdbaan
/
SecuRT
Source Code]
−
This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc.
+
−
</span>
+
−
+
−
[https://github.com/
SamanthaGroves Compiled DLLs]
+
−
+
−
[https://github.com
/
SamanthaGroves
Source Code
]
+
−
+
−
[https://github.com/SamanthaGroves Documentation]
+
−
+
−
[https://github.com/SamanthaGroves Wiki Home Page]
+
−
+
−
[https://github.com/SamanthaGroves Issue Tracker]
+
−
+
−
[https://github.com/SamanthaGroves Slide Presentation]
+
−
+
−
[https://github.com/SamanthaGroves Video
]
+
== Project Leader ==
== Project Leader ==
−
<span style="color
:
#ff0000">
+
[[User
:
Steven_van_der_Baan|Steven van der Baan]]
−
A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.
+
−
</span>
+
−
+
−
Project leader's name
+
== Related Projects ==
== Related Projects ==
−
<span style="color:#ff0000">
−
This is where you can link to other OWASP Projects that are similar to yours.
−
</span>
−
* [[OWASP_Code_Tool_Template]]
+
−
* [
[OWASP_Documentation_Project_Template]
]
+
* [
https://www.owasp.org/index.php/Category:OWASP_Code_Crawler OWASP Code Crawler
]
==Classifications==
==Classifications==
Line 111:
Line 72:
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
−
<
span style="color:#ff0000">
+
<!
--
−
The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project.
+
−
Be sure to give credit where credit is due, no matter how small
!
This should be a brief list of the most amazing people involved in your project.
+
−
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.
+
−
</span>
+
−
+
The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].
The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].
−
+
-->
The first contributors to the project were:
The first contributors to the project were:
−
* [
https://www.owasp.org/index.php/
User:
Clerkendweller Colin Watson
]
who created the OWASP Cornucopia project that the template was derived from
+
* [
[
User:
Steven_van_der_Baan|Steven van der Baan
]]
−
* [https://www.owasp.org/index.php/User:Chuck_Cooper Chuck Cooper
]
who edited the template to convert it from a documentation project to a Code Project Template
+
−
* '''YOUR NAME BELONGS HERE AND YOU SHOULD REMOVE THE PRIOR 3 NAMES'''
+
= Road Map and Getting Involved =
= Road Map and Getting Involved =