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
m
(getting this started)
Line 5: Line 5:
  
 
==About Docker Top 10==
 
==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, depended on your security requirements.
+
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, depended on your security requirements.
  
 
You should use it as a  
 
You should use it as a  
Line 14: Line 14:
  
 
==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.
 +
 
 +
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? ==
  
−
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.
+
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''.
  
−
Contextual custom dictionary builder with character substitution and word variations for pen-testers
 
−
-->
 
  
 
==Licensing==
 
==Licensing==
  
−
To be decided
+
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.  
−
<!--
 
−
<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)}. 
+
[[File:CC-BY-SA-NC.4.0.size88x31.png|link=https://creativecommons.org/licenses/by-nc-sa/4.0/]]  
−
-->
 
  
 
==Roadmap==
 
==Roadmap==
−
As of <strong>September 2018</strong>, the highest priorities for the next 3 months are:
+
As of <strong>November 2018</strong>, the highest priorities for the next 2 months are:
 
<strong>
 
<strong>
 
* Publish and work on a first draft of the documentation
 
* Publish and work on a first draft of the documentation
Line 55: Line 58:
 
==Getting Involved==
 
==Getting Involved==
  
−
For all communication, releases and more please use [https://github.com/OWASP/Docker-Top-10 Github]
+
For all communication, releases and more please use [https://github.com/OWASP/Docker-Security Github]
  
 
| 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;" |
Line 62: Line 65:
  
 
'''Github'''<br />
 
'''Github'''<br />
−
* Actions take place @ [https://github.com/OWASP/Docker-Top-10 Github]
+
* Actions take place @ [https://github.com/OWASP/Docker-Security Github]
 
<br />
 
<br />
 
'''Slides'''<br />
 
'''Slides'''<br />

Revision as of 10:08, 16 November 2018

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, 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.


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 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.

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

Roadmap

As of November 2018, the highest priorities for the next 2 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

Getting Involved

For all communication, releases and more please use Github

Project Resources

Github


Slides

Project Leader

Dirk Wetter

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