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"

From OWASP
Jump to: navigation, search
(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...")
 
m
 
(12 intermediate revisions by the same user not shown)
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;" |
  
−
<span style="color:#ff0000">
+
==About Docker Top 10==
−
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 Docker Top 10 project is giving you ten bullet points to plan and implement a secure docker container environment. Those 10 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, depending on your security requirements.
−
</span>
 
−
==Project About==
 
−
<span style="color:#ff0000">
 
−
{{:Projects/OWASP_Example_Project_About_Page}}
 
  
 +
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.
  
−
==About Docker Top 10==
+
==Where is it? / Getting Involved ==
−
<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 Documentation 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.
+
The development and discussions take place @  [https://github.com/OWASP/Docker-Security Github]. After release you will find the released version also here.
  
 
==Description==
 
==Description==
 +
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
−
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 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.
+
This guide is for developers, auditors, architects, system and networking engineers. As indicated above you can also use this guide for externals to add formal technical requirements in your contract. The information security officer should have some interest too to meet security requirements.
  
−
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.
+
The 10 bullet points here are about system and network security and also architecture. As a developer you don't have to be an expert in those -- that's what this guide is for. But as indicated above best is to start thinking about those points early. Please do not just start building it.
  
−
Contextual custom dictionary builder with character substitution and word variations for pen-testers
+
Security in Docker environments seemed often to be misunderstood. It was/is a highly disputed matter what the threats are supposed to be. So before diving into the Docker Top 10 bullet points, the threads are modeled. It not only helps understanding the security impacts but also gives you the ability to prioritize your task.
 +
 
 +
</span
 +
 
 +
== Why not "Container Security" ==
 +
 
 +
Albeit the name of this project carries the word "Docker", it also can be used with little abstraction for other containment solutions. Docker is as of now the most popular one, so the in-depth details are focusing for now on Docker. This could change later.
 +
 
 +
== A single container? ==
 +
 
 +
If you run more than 3 containers you probably have an orchestration solution to manage them. '''Specific''' security pitfalls of those are currently beyond the scope of this document. That doesn't mean that this guide just looking at one or a few containers managed manually -- on the contrary. It means only that we're looking at the containers including their networking and their host systems in such an orchestrated environment and not on special pitfalls of e.g. ''Kubernetes'', ''Swarm'', ''Mesos'' or'' OpenShift''.
  
 
==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)}.
+
The Docker OWASP Top 10 document is licensed under the [https://creativecommons.org/licenses/by-nc-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 license] (CC BY-NC-SA 4.0). Some rights reserved.
 +
 
 +
[[File:CC-BY-SA-NC.4.0.size88x31.png|link=https://creativecommons.org/licenses/by-nc-sa/4.0/]]
  
 
==Roadmap==
 
==Roadmap==
−
<span style="color:#ff0000">
+
The highest priorities for the next months are:
−
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
 
 
<strong>
 
<strong>
−
* Complete the first draft of the Documentation Project Template
+
* Publish and work on a first draft of the documentation
−
* Get other people to review the Documentation Project Template and provide feedback
+
* Complete this first draft
−
* Incorporate feedback into changes in the Documentation Project Template
+
* Get other people involved to review the documentation and provide feedback
−
* Finalize the Documentation Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
+
* Incorporate feedback into the documentation
 +
* First Release
 
</strong>
 
</strong>
  
 
Subsequent Releases will add
 
Subsequent Releases will add
 
<strong>
 
<strong>
−
* Internationalization Support
+
* Go from Draft to Release
−
* Additional Unit Tests
+
* Being promoted from an Incubator Project to a Lab Project
−
* Automated Regression tests
 
 
</strong>
 
</strong>
−
 
−
==Getting Involved==
 
−
<span style="color:#ff0000">
 
−
Involvement in the development and promotion of <strong>Documentation Project Template</strong> 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:
 
  
 
| 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">
 
−
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 Installation Package]
 
−
 
−
[https://github.com/SamanthaGroves Source Code]
 
−
 
−
[https://github.com/SamanthaGroves What's New (Revision History)]
 
−
 
−
[https://github.com/SamanthaGroves Documentation]
 
−
 
−
[https://github.com/SamanthaGroves Wiki Home Page]
 
  
−
[https://github.com/SamanthaGroves Issue Tracker]
+
'''Github'''<br />
 +
*  See [https://github.com/OWASP/Docker-Security Github]
 +
<br />
 +
'''Slides'''<br />
 +
* Dirk Wetter: ([https://www.owasp.org/images/f/fd/Dirk_Wetter_-_Docker_Top10-OWASP_KA.pdf long version, talk in Karlsruhe]), ([https://www.owasp.org/images/7/7e/Dirk_Wetter_-_Docker_Security_GOD2018.pdf short version @ German OWASP Day 2018]),
 +
* Dirk Wetter, older talks from [https://www.owasp.org/images/1/17/Dirk_Wetter_-_Docker_Security_Brussels.pdf Belgium Chapter Meeting], [https://2018.appsec.eu/presos/DevOps_Docker_201_Security_Dirk-Wetter_AppSecEU2018.pdf OWASP AppSec Europe 2018]
  
−
[https://github.com/SamanthaGroves Slide Presentation]
 
  
−
[https://github.com/SamanthaGroves Video]
+
* Jack Mannino and Abdullah Munawar: [https://2018.appsec.eu/presos/DevOps_Securing-Containers_Jack-Mannino_Abdullah-Munawar_AppSecEU2018.pptx Slides of Presentation] at OWASP AppSec Europe 2018
  
 
== 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>
 
−
 
 
Dirk Wetter
 
Dirk Wetter
  
 
== 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_Project_Template]]
 
* [[OWASP_Code_Project_Template]]
 
* [[OWASP_Tool_Project_Template]]
 
* [[OWASP_Tool_Project_Template]]
  
 +
--?
 
==Classifications==
 
==Classifications==
  

Latest revision as of 08:33, 8 November 2019

OWASP Project Header.jpg

About Docker Top 10

The OWASP Docker Top 10 project is giving you ten bullet points to plan and implement a secure docker container environment. Those 10 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, depending 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.

Where is it? / Getting Involved

The development and discussions take place @ Github. After release you will find the released version also here.

Description

This guide is for developers, auditors, architects, system and networking engineers. As indicated above you can also use this guide for externals to add formal technical requirements in your contract. The information security officer should have some interest too to meet security requirements.

The 10 bullet points here are about system and network security and also architecture. As a developer you don't have to be an expert in those -- that's what this guide is for. But as indicated above best is to start thinking about those points early. Please do not just start building it.

Security in Docker environments seemed often to be misunderstood. It was/is a highly disputed matter what the threats are supposed to be. So before diving into the Docker Top 10 bullet points, the threads are modeled. It not only helps understanding the security impacts but also gives you the ability to prioritize your task.

</span

Why not "Container Security"

Albeit the name of this project carries the word "Docker", it also can be used with little abstraction for other containment solutions. Docker is as of now the most popular one, so the in-depth details are focusing for now on Docker. This could change later.

A single container?

If you run more than 3 containers you probably have an orchestration solution to manage them. Specific security pitfalls of those are currently beyond the scope of this document. That doesn't mean that this guide just looking at one or a few containers managed manually -- on the contrary. It means only that we're looking at the containers including their networking and their host systems in such an orchestrated environment and not on special pitfalls of e.g. Kubernetes, Swarm, Mesos or OpenShift.

Licensing

The Docker OWASP Top 10 document is licensed under the Creative Commons Attribution-ShareAlike 4.0 license (CC BY-NC-SA 4.0). Some rights reserved.

CC-BY-SA-NC.4.0.size88x31.png

Roadmap

The highest priorities for the next months are:

  • Publish and work on a first draft of the documentation
  • Complete this first draft
  • Get other people involved to review the documentation and provide feedback
  • Incorporate feedback into the documentation
  • First Release

Subsequent Releases will add

  • Go from Draft to Release
  • Being promoted from an Incubator Project to a Lab Project

Project Resources

Github


Slides


Project Leader

Dirk Wetter

Related Projects
Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Docker_Top_10&oldid=255992"