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 Docker Top 10"
Hblankenship (talk | contribs) (Created page with "<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">link=</div> {| style="padding: 0;margin:0;margin-top:10px;text-alig...") |
Dirk Wetter (talk | contribs) (1st draft: About section) |
||
| Line 4: | Line 4: | ||
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | | ||
| − | |||
| − | |||
| − | |||
==Project About== | ==Project About== | ||
<span style="color:#ff0000"> | <span style="color:#ff0000"> | ||
| Line 14: | Line 11: | ||
==About Docker Top 10== | ==About Docker Top 10== | ||
<span style="color:#ff0000"> | <span style="color:#ff0000"> | ||
| − | + | ||
| + | The OWASP Docker Top 10 is giving you ten bullet points to plan and implement a secure docker container environment. The 10 bullet points are ordered by relevance. They don't represent risks as each single point in the OWASP Top 10, they represent security controls. The controls range from baseline security to more advanced controls, depended on your security requirements. | ||
| + | |||
| + | You should use it as a guidance in the design phase as a system specification or for auditing a docker environment. Also for procurement it could provide a basis for specifying requirements in contracts. | ||
| + | |||
</span> | </span> | ||
| − | |||
==Description== | ==Description== | ||
Revision as of 17:11, 31 August 2018
Project About
About Docker Top 10
The OWASP Docker Top 10 is giving you ten bullet points to plan and implement a secure docker container environment. The 10 bullet points are ordered by relevance. They don't represent risks as each single point in the OWASP Top 10, they represent security controls. The controls range from baseline security to more advanced controls, depended on your security requirements. You should use it as a guidance in the design phase as a system specification or for auditing a docker environment. Also for procurement it could provide a basis for specifying requirements in contracts.
DescriptionThis 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. The Documentation Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Documentation 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 Documentation Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security. Contextual custom dictionary builder with character substitution and word variations for pen-testers LicensingA project must be licensed under a community friendly or open source license. For more information on OWASP recommended licenses, please see 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. This program is free software: you can redistribute it and/or modify it under the terms of the 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)}. RoadmapAs of November, 2013, the highest priorities for the next 6 months are:
Subsequent Releases will add
Getting InvolvedInvolvement in the development and promotion of Documentation Project Template is actively encouraged! You do not have to be a security expert or a programmer to contribute. Some of the ways you can help are as follows: |
Project ResourcesThis 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. Project LeaderA 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. Dirk Wetter Related ProjectsThis is where you can link to other OWASP Projects that are similar to yours. Classifications
| ||||||||||||||||||||||||||||||||||||||||||||||||||
