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 "OWASP Zezengorri Code Project"

From OWASP
Jump to: navigation, search
m
(→‎Main)
Line 4: Line 4:
  
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
−
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
+
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
−
 
 
−
<span style="color:#ff0000">
 
−
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.
 
−
</span>
 
−
 
 
 
==OWASP Code Library Project==
 
==OWASP Code Library Project==
−
<span style="color:#ff0000">
+
This   is   Zezengorri   a   library   to   allows   you   to   add   security   in   the   development   IDE   from   the day   one,   of   the   moment   you   decide   implement  security   development   to   your  projects, starting in design phase of   new projects, and  in  old  projects  for  see  what  you  miss  detecting the   vulnerabilities   of   the   web   server,   the   computer   and   the   programming   language   before starting   the   development   on   in   parallel   with   the   Lifecycle  software  development.
−
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.
 
−
 
 
−
That is Zezengorri a library to allows you to add security in the development IDE from the day one, of the moment you decide implementation security development to the project, starting in design phase of old and new projects, detecting the vulnerabilities of the web server, the computer and the programming language before starting the development on in parallel with the SDLC.
 
−
 
 
−
The initial idea is to deliver through the composer a package for PHP programming language solutions that use any of this framework: Laravel, Symphony and Code Integer. If this version for PHP
 
  
 
==Description==
 
==Description==
−
<span style="color:#ff0000">
+
When  developers,  team  leaders  or  project  managers  add   security  to   a  web  application,   the  first thing  that   comes  up  is   the  question   of  which  technologies  are  handled  in  my  web  project,  what operating  system  the   web  server  supports,  what  version  of  server  or  what  version  of  the database  the   application  uses,   for  this  Owasp  define  the   threat  modeling  (knowing  what  we have).
−
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>
 
  
 +
This  project  Zezengorri  is  a  code  library  is  a  downloadable  package  that  adheres  to  the  root  of the  web  project,  and  from  them  this  can,  analyzes  and  seeks  to  collect  in  a  simple  web  page  the characteristics  of  all  the  security  components  for  examples:  if  our  website  uses  or  not  HSTS,  the versions  of  Chipset  active,  the  use  of  SSL  certificate  for  the  web  page  among  other  securities characteristics  important  measure  in  the  during  the  life  cycle  development  software  .  Each  of these  item  is  display  in  a  new  web page  in  a  list  of  item  any  show  if  is  active  or  not,  the  version  of the  plugin  and  a  web link.  That  links  redirect  to  the  CVE  page  and  the  CVE  score  of  this  item. determine  if  the  project  can  be  promoted  to  the  next  category.  The  information  requested  is  also intended  to  help  Project  Leaders  think  about  the  road map  and  feature  priorities,  and  give guidance  to  the  reviews  as  a  result  of  that  effort.
  
−
When developers, team leaders or project managers add security to a web application, the first thing that comes up is the question of which technologies are handled in my web project, what operating system the web server supports, what version of server or what version of the database the application uses, for this Owasp define the threat modeling (knowing what we have).
+
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.
−
 
 
−
This project Zezengorri for PHP is a downloadable package that adheres to the root of the Lavarel, Symphony, Code Integer projects, analyzes and seeks to collect in a simple web page the characteristics of all the security components for examples: if the site uses or not HSTS, the versions of Chipset active, the use of SSL certificate among other securities characteristics important measure in the moment of S-SDLC . Each of these item is display in a new webpage in a list of item any show if is active or not, the version of the plugin and a weblink. That links redirect to the CVE page and the CVE score of this item.
 
−
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.
 
−
 
 
−
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 &copy; 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 these 
 +
* https://opensource.org/licenses/NPOSL-3.0
 +
* https://creativecommons.org/licenses/by/4.0/
 +
* https://opensource.org/licenses/Frameworx-1.0
 +
as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.  OWASP and any contributions are Copyright &copy; by OWASP Years 2017-2018.   
  
−
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
+
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |
  
 
== Project Resources ==
 
== Project Resources ==
−
<span style="color:#ff0000">
 
−
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 Secure Codding Life Cycle]
  
−
[https://github.com/SamanthaGroves Issue Tracker]
+
[https://github.com/SamanthaGroves Source Codding .Net]
  
−
[https://github.com/SamanthaGroves Slide Presentation]
+
[https://github.com/SamanthaGroves Security Automate Test]
−
 
 
−
[https://github.com/SamanthaGroves Video]
 
  
 
== Project Leader ==
 
== Project Leader ==
−
<span style="color:#ff0000">
 
−
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:Gustavo Nieves Arreaza
 
Project leader's name:Gustavo Nieves Arreaza
  
 
== Related Projects ==
 
== Related Projects ==
−
<span style="color:#ff0000">
+
Owasp  Secure  Coding  Practiques
−
This is where you can link to other OWASP Projects that are similar to yours.
 
−
</span>
 
  
 
* [[OWASP_Code_Tool_Template]]
 
* [[OWASP_Code_Tool_Template]]
Line 81: Line 47:
 
   {| width="200" cellpadding="2"
 
   {| width="200" cellpadding="2"
 
   |-
 
   |-
−
   | colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
+
   | colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
 
   |-
 
   |-
−
   | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
+
   | rowspan="2" width="50%" valign="top" align="center" | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
−
   | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]   
+
   | width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=Builders]]   
 
   |-
 
   |-
−
   | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=Defenders]]
+
   | width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=Defenders]]
 
   |-
 
   |-
−
   | colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
+
   | colspan="2" align="center" |
 
   |}
 
   |}
  
−
| valign="top"  style="padding-left:25px;width:200px;" |  
+
| style="padding-left:25px;width:200px;" valign="top" |  
  
 
== News and Events ==
 
== News and Events ==
−
<span style="color:#ff0000">
+
* [1 Nov 2017] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.
−
This is where you can provide project updates, links to any events like conference presentations, Project Leader interviews, case studies on successful project implementations, and articles written about your project.
+
* [19 Jan 2018] 1.0 Release Candidate is available for download. This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.
−
</span>
 
−
* [18 Dec 2013] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.
 
−
* [20 Nov 2013] 1.0 Beta 2 Release is available for download. This release offers several bug fixes, a few performance improvements, and addressed all outstanding issues from a security audit of the code.
 
−
* [30 Sep 2013] 1.0 Beta 1 Release is available for download.  This release offers the first version with all of the functionality for a minimum viable product.    
 
  
 
|}
 
|}
Line 110: Line 72:
  
 
==How can I participate in your project?==
 
==How can I participate in your project?==
−
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.
+
For  this  first  Phase:  If  you   have   experience  in  web  development  with  languages    such  as  Node.JS, C #,  Java.  
 +
 
 +
And  you   want  to   learn  about  security  on  web  pages.   You  can   participate  please  contact  us  by  the official  mail  of  the   project  leader  Zezengorri
  
 
==If I am not a programmer can I participate in your project?==
 
==If I am not a programmer can I participate in your project?==
−
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.  
+
Yes,   you   can   certainly   participate   in   the   project   if   you   are   not   a   programmer   or   technical.   The project   needs   different   skills   and   expertise   and   different   times   during   its   development.   Currently, we   are   looking   for   researchers   to  like  know  how      computer,server,databases  and  network  work and  how  can  secure,   the  web  applications  whe  these  is  use  this  resources;  and   writers  for document  all  we  are  going  to  do.  
  
 
= Acknowledgements =
 
= Acknowledgements =
Line 119: Line 83:
  
 
<!-- 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   OWASP   Security  Zenzengorri  Principles  project  is   developed  by  a   worldwide  team  of volunteers.   A  live  update  of   project   contributors  is   found  here .
−
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   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
 
−
* [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 =
  
 
<!-- 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">
 
−
A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.
 
−
Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.
 
−
</span>
 
  
−
Planned feature enhancement
+
==Roadmap==
−
• Create the class to enable integration with the Code Integer framework
+
As of '''''february'' , 2017, the highest priorities for the next 6 months''' are:
−
• Add to this application more and more items related to website security
+
<strong></strong>'''● Complete  the  first  draft  of  the  Code   Project  Template'''
  
−
Commercial Roadmap:
+
'''● Get  other  people  to  review  the  Code  Project  Template  and  provide  feedback'''
  
−
-Publish the Code Library Repository
+
'''● Incorporate  feedback  into  changes  in  the   Code   Project  Template'''
−
-Promote the Code Library on our website:  www.seguridadaplicativos.com
 
−
-Present the applications in conferences of Owasp.
 
−
-Present the application in regional Startup´.
 
−
-Rise money for regional Startup
 
  
−
Miles tones:
+
'''● Finalize  the  Code  Project  template  and  have  it  reviewed  to  be  promoted  from  an'''
  
−
-In the project development phase
+
'''Incubator  Project  to  a  Lab  Project'''
  
−
• The amount of security information that we collect from the components that support the website
+
</strong>
  
−
-In the production phase
+
As  of  september  ,  2017,  the highest  priorities  for  the next  6  months  are:<strong>
−
• The number of downloads from the code library
 
  
−
Essential conditions:
+
Release  version  of  library  1.0
  
−
-In the Technical area:
+
'''● Promote  the   library  in  conferences'''
  
−
• That there are still we found security holes in web applications.
+
'''● Get  academic  support'''
−
• That still PHP remains how the most used programming language for web development
 
−
The development team work separately of the support system team, when the develop a web site or app
 
  
−
-Commercial:
+
'''● Recruit  more  volunteers'''</strong>Subsequent  Releases  will  add
−
• Awareness that security IT must be worked from the development IDE
 
−
• Businesses and programmers start investing in software to secure their applications.
 
  
−
Technical Roadmap:
 
−
 
−
Items                                                   Time Tasks                           State of progress
 
−
-Code Library development                          1 weak                                          Finish
 
−
-Collate  information of machine                  2 months                                    In progress 
 
−
web server and others                                                     
 
−
-Presents data  collated                                  2 weaks                                      In progress
 
−
-Search in Web CVE                                      1 month                                      No started                   
 
−
-Functionality to import  Data                        2 weeks                                      No started
 
−
 
−
 
−
 
−
 
−
 
−
==Roadmap==
 
−
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
 
−
<strong>
 
−
* Complete the first draft of the Code Project Template
 
−
* Get other people to review the Code Project Template and provide feedback
 
−
* Incorporate feedback into changes in the Code Project Template
 
−
* Finalize the Code Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
 
 
</strong>
 
</strong>
−
 
+
* Internationalization Support</strong>
−
Subsequent Releases will add
 
−
<strong>
 
−
* Internationalization Support
 
 
* Additional Unit Tests
 
* Additional Unit Tests
−
* Automated Regression tests
+
* Automated Regression tests</strong></strong>
−
</strong>
 
  
 
==Getting Involved==
 
==Getting Involved==
−
Involvement in the development and promotion of <strong>Code Project Template</strong> is actively encouraged!
+
Involvement   in   the   development   and   promotion   of   Code   Project   Template   is   actively encouraged.   Some   of   the   ways   you   can   help   are   as   follows:
−
You do not have to be a security expert or a programmer to contribute.
 
−
Some of the ways you can help are as follows:
 
  
 
===Coding===
 
===Coding===
−
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
+
We   could   implement   some   of   the   later   items   on   the   roadmap   sooner   if   someone   wanted   to   help out   with   unit   or   automated   regression   tests
 
===Localization===
 
===Localization===
−
Are you fluent in another language? Can you help translate the text strings in the <strong>Code Project Template</strong> into that language?
+
Are   you   fluent   in   another   language?   Can   you   help   translate   the   text   strings   in   the   Code   Project Template   into   that   language?
 +
 
 +
German French Russian Portuguese
 +
 
 
===Testing===
 
===Testing===
−
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
+
Do   you   have   a   flair   for   finding   bugs   in   software?   We   want   to   product   a   high   quality   product,   so any   help
 
===Feedback===
 
===Feedback===
 
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
 
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
Line 235: Line 153:
 
=Project About=
 
=Project About=
 
<!-- 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  functionalities  of  this  code  library  are  when  it  is   downloaded  and   implemented.
−
This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager.  
+
* -Detect  vulnerabilities
−
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
+
* -Relate  vulnerabilities,   with  an  updated  database  online.
−
</span>
+
* -Ranking  the   severity  of  vulnerabilities  with  their  critical.
−
 
+
* -Describe  solutions  for  fix  the  vulnerabilities
 +
* -Help  with  the  implementation  of  classes  and  functions  to  implement  secure development
 +
* Teach  about  secure  coding  subject  to  developer  team
 
{{:Projects/OWASP_Example_Project_About_Page}}  
 
{{:Projects/OWASP_Example_Project_About_Page}}  
  
  
−
__NOTOC__ <headertabs />  
+
__NOTOC__ <headertabs></headertabs>  
  
−
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Code]]
+
[[Category:OWASP Project]]   
 +
[[Category:OWASP_Builders]]  
 +
[[Category:OWASP_Defenders]]   
 +
[[Category:OWASP_Code]]

Revision as of 18:09, 25 October 2017

OWASP Project Header.jpg

OWASP Code Library Project

This is Zezengorri a library to allows you to add security in the development IDE from the day one, of the moment you decide implement security development to your projects, starting in design phase of new projects, and in old projects for see what you miss detecting the vulnerabilities of the web server, the computer and the programming language before starting the development on in parallel with the Lifecycle software development.

Description

When developers, team leaders or project managers add security to a web application, the first thing that comes up is the question of which technologies are handled in my web project, what operating system the web server supports, what version of server or what version of the database the application uses, for this Owasp define the threat modeling (knowing what we have).

This project Zezengorri is a code library is a downloadable package that adheres to the root of the web project, and from them this can, analyzes and seeks to collect in a simple web page the characteristics of all the security components for examples: if our website uses or not HSTS, the versions of Chipset active, the use of SSL certificate for the web page among other securities characteristics important measure in the during the life cycle development software . Each of these item is display in a new web page in a list of item any show if is active or not, the version of the plugin and a web link. That links redirect to the CVE page and the CVE score of this item. determine if the project can be promoted to the next category. The information requested is also intended to help Project Leaders think about the road map and feature priorities, and give guidance to the reviews as a result of that effort.

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

This program is free software: you can redistribute it and/or modify it under the terms of these

as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. OWASP and any contributions are Copyright © by OWASP Years 2017-2018.

Project Resources

Secure Codding Life Cycle

Source Codding .Net

Security Automate Test

Project Leader

Project leader's name:Gustavo Nieves Arreaza

Related Projects

Owasp Secure Coding Practiques

Classifications

Project Type Files CODE.jpg
Incubator Project Owasp-builders-small.png
Owasp-defenders-small.png

News and Events

  • [1 Nov 2017] 1.0 Release Candidate is available for download. This release provides final bug fixes and product stabilization. Any feedback (good or bad) in the next few weeks would be greatly appreciated.
  • [19 Jan 2018] 1.0 Release Candidate is available for download. This release provides final bug fixes and product stabilization. Any feedback (good or bad) in the next few weeks would be greatly appreciated.

Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. The point of a document like this are the answers. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'

How can I participate in your project?

For this first Phase: If you have experience in web development with languages such as Node.JS, C #, Java.

And you want to learn about security on web pages. You can participate please contact us by the official mail of the project leader Zezengorri

If I am not a programmer can I participate in your project?

Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers to like know how computer,server,databases and network work and how can secure, the web applications whe these is use this resources; and writers for document all we are going to do.

Volunteers

The OWASP Security Zenzengorri Principles project is developed by a worldwide team of volunteers. A live update of project contributors is found here .

The first contributors to the project were:

Roadmap

As of february , 2017, the highest priorities for the next 6 months are: ● Complete the first draft of the Code Project Template

● Get other people to review the Code Project Template and provide feedback

● Incorporate feedback into changes in the Code Project Template

● Finalize the Code Project template and have it reviewed to be promoted from an

Incubator Project to a Lab Project

</strong>

As of september , 2017, the highest priorities for the next 6 months are:

Release version of library 1.0

● Promote the library in conferences

● Get academic support

● Recruit more volunteersSubsequent Releases will add

</strong>

  • Internationalization Support</strong>
  • Additional Unit Tests
  • Automated Regression tests</strong></strong>

Getting Involved

Involvement in the development and promotion of Code Project Template is actively encouraged. Some of the ways you can help are as follows:

Coding

We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests

Localization

Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?

German French Russian Portuguese

Testing

Do you have a flair for finding bugs in software? We want to product a high quality product, so any help

Feedback

Please use the Code Project Template project mailing list for feedback about:

  • What do like?
  • What don't you like?
  • What features would you like to see prioritized on the roadmap?

This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern. Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap. And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.

The Code Project Template must specify the minimum set of tabs a project should have, provide some an example layout on each tab, provide instructional text on how a project leader should modify the tab, and give some example text that illustrates how to create an actual project.

It would also be ideal if the sample text was translated into different languages.

The functionalities of this code library are when it is downloaded and implemented.

  • -Detect vulnerabilities
  • -Relate vulnerabilities, with an updated database online.
  • -Ranking the severity of vulnerabilities with their critical.
  • -Describe solutions for fix the vulnerabilities
  • -Help with the implementation of classes and functions to implement secure development
  • Teach about secure coding subject to developer team
PROJECT INFO
What does this OWASP project offer you? 		RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: N/A
Purpose: N/A
License: N/A
who is working on this project?
Project Leader(s): N/A
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Key Contacts
  • Contact the GPC to contribute to this project
  • Contact the GPC to review or sponsor this project
current release
pending
last reviewed release
pending


other releases


Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Zezengorri_Code_Project&oldid=234636"