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"
(→Main) (Tag: Visual edit) |
(→Licensing) (Tag: Visual edit) |
||
| Line 27: | Line 27: | ||
== Project Resources == | == Project Resources == | ||
| − | [ | + | [[Https://drive.google.com/file/d/0B6d-UqLnHsOnUTZLTXVLbEZyY0E/view?usp=sharing|Secure Codding Life Cycle]] |
| − | [ | + | [[Https://drive.google.com/file/d/0B6d-UqLnHsOnSDlwQW5tNGRKMkxSblVWX1g0RHZuNTJjM2tV/view?usp=sharing|Source Codding .Net]] |
| − | [ | + | [[Http://www.swtestacademy.com/automated-security-testing-using-zap/|Security Automate Test]] |
== Project Leader == | == Project Leader == | ||
| Line 40: | Line 40: | ||
Owasp Secure Coding Practiques | Owasp Secure Coding Practiques | ||
| − | * [ | + | * [https://www.owasp.org/index.php/Projects/OWASP_Secure_Coding_Practices_-_Qui ck_Reference_Guide/Releases/SCP_v2 Secure_Coding_Practices] |
| − | * [ | + | * [https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project Owasp Zed Attack Framework] |
==Classifications== | ==Classifications== | ||
| Line 60: | Line 60: | ||
== News and Events == | == News and Events == | ||
| − | * [1 Nov 2017] | + | * [1 Nov 2017] Release Page Explain the Concept, with a white Paper |
* [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. | * [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. | ||
| Line 66: | Line 66: | ||
=FAQs= | =FAQs= | ||
| − | <!-- 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.-->==How can I participate in your project?== |
| − | |||
| − | |||
| − | |||
| − | |||
| − | ==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. | For this first Phase: If you have experience in web development with languages such as Node.JS, C #, Java. | ||
| Line 91: | Line 86: | ||
<!-- 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.--> | ||
| − | |||
==Roadmap== | ==Roadmap== | ||
As of '''''february'' , 2017, the highest priorities for the next 6 months''' are: | As of '''''february'' , 2017, the highest priorities for the next 6 months''' are: | ||
| Line 103: | Line 97: | ||
'''Incubator Project to a Lab Project''' | '''Incubator Project to a Lab Project''' | ||
| − | |||
| − | |||
As of september , 2017, the highest priorities for the next 6 months are:<strong> | As of september , 2017, the highest priorities for the next 6 months are:<strong> | ||
| Line 114: | Line 106: | ||
'''● Get academic support''' | '''● Get academic support''' | ||
| − | '''● Recruit more volunteers'''</strong> | + | '''● Recruit more volunteers'''</strong> |
| − | + | Subsequent Releases will add | |
| − | * Internationalization Support | + | |
| + | * Internationalization Support | ||
* Additional Unit Tests | * Additional Unit Tests | ||
| − | * Automated Regression tests | + | * Automated Regression tests |
==Getting Involved== | ==Getting Involved== | ||
| Line 132: | Line 125: | ||
===Testing=== | ===Testing=== | ||
| − | Do you have a flair for finding bugs in software? We want to product a high quality product, so any help | + | 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. |
===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 142: | Line 135: | ||
=Minimal Viable Product= | =Minimal Viable Product= | ||
| − | + | 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 criticality. -Describe solutions for fix the vulnerabilities | |
| − | + | -Help with the implementation of classes and functions to implement secure development | |
=Project About= | =Project About= | ||
Revision as of 19:34, 25 October 2017
OWASP Code Library ProjectThis 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. DescriptionWhen 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. LicensingThis 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 ResourcesProject LeaderProject leader's name:Gustavo Nieves Arreaza Related ProjectsOwasp Secure Coding Practiques Classifications
|
News and Events
| |||||||
