Difference between revisions of "OWASP Container Security Verification Standard (CSVS)"

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...")
 
(initial content for CSVS wiki page)
 
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">
+
== What is CSVS? ==
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>
 
==Project About==
 
<span style="color:#ff0000">
 
{{:Template:Project About
 
  | project_name = Container Security Verification Standard
 
  | leader_name1 = Sven Vetsch
 
}}
 
  
 +
The Container Security Verification Standard (CSVS) is a community-effort to establish a framework of security requirements and controls that focus on normalizing the functional and non-functional security controls required when designing, developing and testing container-based solutions with a focus on Docker.
  
==OWASP Documentation Project Template==
+
== Download CSVS ==
<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.
+
[https://github.com/Redguard/csvs/releases/download/v1.0/container_security_verification_standard_v1.0_en.pdf PDF Download]
  
==Description==
+
[https://github.com/Redguard/csvs/releases/download/v1.0/container_security_verification_standard_v1.0_en.docx Word Download]
<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.
+
[https://github.com/OWASP/Container-Security-Verification-Standard Source Code (GitHub)]
  
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.
+
== Use Cases ==
  
Contextual custom dictionary builder with character substitution and word variations for pen-testers
+
* As Detailed Security Architecture Guidance
 +
*: One of the more common uses for the Container Security Verification Standard is as a resource for security architects. The two major security architecture frameworks, SABSA and TOGAF, are missing a great deal of information that is necessary to complete application and container security architecture review. CSVS can be used to fill in those gaps by allowing security architects to choose better controls for common problems.
 +
* As a Replacement for Off-the-shelf Checklists
 +
*: Many organizations can benefit from adopting the CSVS, by choosing one of the three levels, or by forking CSVS and changing what is required for each risk level in a domain specific way. We encourage this type of forking as long as traceability is maintained.
 +
* For Security Trainings
 +
*: The CSVS can also be used to define characteristics of secure container infrastructure. Many security courses are simply ethical hacking courses with a light smear of operational tips. Security trainings can use the CSVS with its strong focus on the proactive controls to tech about best practices.
  
==Licensing==
+
== FAQ ==
<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 document looks similar to the OWASP Application Security Verification Standard. How is it related?
 +
#: We love the work done by OWASP and indeed the overall structure and e.g. the scripts to export the CSVS to other formats is comming from the ASVS.
 +
# If it's somewhat related to the OWASP ASVS project why not make the CSVS an OWASP project too?
 +
#: That's exactly what we plan to do. Once we've gathered some feedback and have a first version we're looking forward to donate the CSVS in full to OWASP.
 +
# Topic XYZ is missing. Why?
 +
#: Either it didn't cross our minds yet or we thought it is already covered in one of the requirements in the CSVS. Anyway, please [https://github.com/redguard/csvs/issues/new open an issue] to let us know or even better fork the CSVS and send us a pull request with your changes.
 +
# There are already other documents that cover container security like the [https://www.cisecurity.org/benchmark/docker/ CIS Docker Benchmark] or [https://nvlpubs.nist.gov/nistpubs/specialpublications/nist.sp.800-190.pdf NIST Application Container Security Guide]. Why do we need the CSVS?
 +
#: Existing documents often contain more than 100 pages or are using a lot of running text. We think there should be a clear standard that allows you to go through and actually verify your level of security related to container solutions.
 +
# Is there any referencing from the CSVS to other standards and vice-versa?
 +
#: Unfortunately not yet, but we made sure to cover at least the [https://www.cisecurity.org/benchmark/docker/ CIS Docker Benchmark] and [https://nvlpubs.nist.gov/nistpubs/specialpublications/nist.sp.800-190.pdf NIST Application Container Security Guide].
  
==Roadmap==
+
== Related Projects ==
<span style="color:#ff0000">
 
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
 
<strong>
 
* Complete the first draft of the Documentation Project Template
 
* Get other people to review the Documentation Project Template and provide feedback
 
* Incorporate feedback into changes in the Documentation Project Template
 
* Finalize the Documentation Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
 
</strong>
 
  
Subsequent Releases will add
+
[[Image:Asvs-satellite.jpg]]'''OWASP Resources'''
<strong>
 
* Internationalization Support
 
* Additional Unit Tests
 
* Automated Regression tests
 
</strong>
 
  
==Getting Involved==
+
*[https://www.owasp.org/index.php/Category:OWASP_Application_Security_Verification_Standard_Project OWASP ASVS]
<span style="color:#ff0000">
+
*[https://www.owasp.org/index.php/OWASP_Proactive_Controls OWASP Top Ten Proactive Controls (2018)]
Involvement in the development and promotion of <strong>Documentation Project Template</strong> is actively encouraged!
+
*[http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top Ten Risks]
You do not have to be a security expert or a programmer to contribute.
+
*[https://www.owasp.org/index.php/OWASP_Cheat_Sheet_Series OWASP Cheatsheet Series]
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/Redguard/csvs/releases/download/v1.0/container_security_verification_standard_v1.0_en.pdf PDF Download]
  
[https://github.com/SamanthaGroves Source Code]
+
[https://github.com/Redguard/csvs/releases/download/v1.0/container_security_verification_standard_v1.0_en.docx Word Download]
  
[https://github.com/SamanthaGroves What's New (Revision History)]
+
[https://github.com/OWASP/Container-Security-Verification-Standard Source Code (GitHub)]
  
[https://github.com/SamanthaGroves Documentation]
+
== Project Leader ==
 
 
[https://github.com/SamanthaGroves Wiki Home Page]
 
 
 
[https://github.com/SamanthaGroves Issue Tracker]
 
 
 
[https://github.com/SamanthaGroves Slide Presentation]
 
 
 
[https://github.com/SamanthaGroves Video]
 
  
== Project Leader ==
+
Sven Vetsch [mailto:sven.vetsch@owasp.org @]
<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>
 
  
Sven Vetsch
+
== Licensing ==
  
== Related Projects ==
+
[https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution ShareAlike 4.0]
<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_Tool_Project_Template]]
 
  
 
==Classifications==
 
==Classifications==
Line 111: Line 76:
 
   | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=Defenders]]
 
   | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=Defenders]]
 
   |-
 
   |-
   | colspan="2" align="center"  | [[Image:Creative%20Commons.png| 90px | link=https://creativecommons.org/licenses/by-sa/3.0/| Creative Commons Attribution ShareAlike 3.0 License]]
+
   | colspan="2" align="center"  | [[Image:Creative%20Commons.png| 90px | link=https://creativecommons.org/licenses/by-sa/4.0/| Creative Commons Attribution ShareAlike 4.0 License]]
 
   |}
 
   |}
 
|}
 
|}

Latest revision as of 09:34, 28 March 2019

OWASP Project Header.jpg

What is CSVS?

The Container Security Verification Standard (CSVS) is a community-effort to establish a framework of security requirements and controls that focus on normalizing the functional and non-functional security controls required when designing, developing and testing container-based solutions with a focus on Docker.

Download CSVS

PDF Download

Word Download

Source Code (GitHub)

Use Cases

  • As Detailed Security Architecture Guidance
    One of the more common uses for the Container Security Verification Standard is as a resource for security architects. The two major security architecture frameworks, SABSA and TOGAF, are missing a great deal of information that is necessary to complete application and container security architecture review. CSVS can be used to fill in those gaps by allowing security architects to choose better controls for common problems.
  • As a Replacement for Off-the-shelf Checklists
    Many organizations can benefit from adopting the CSVS, by choosing one of the three levels, or by forking CSVS and changing what is required for each risk level in a domain specific way. We encourage this type of forking as long as traceability is maintained.
  • For Security Trainings
    The CSVS can also be used to define characteristics of secure container infrastructure. Many security courses are simply ethical hacking courses with a light smear of operational tips. Security trainings can use the CSVS with its strong focus on the proactive controls to tech about best practices.

FAQ

  1. The document looks similar to the OWASP Application Security Verification Standard. How is it related?
    We love the work done by OWASP and indeed the overall structure and e.g. the scripts to export the CSVS to other formats is comming from the ASVS.
  2. If it's somewhat related to the OWASP ASVS project why not make the CSVS an OWASP project too?
    That's exactly what we plan to do. Once we've gathered some feedback and have a first version we're looking forward to donate the CSVS in full to OWASP.
  3. Topic XYZ is missing. Why?
    Either it didn't cross our minds yet or we thought it is already covered in one of the requirements in the CSVS. Anyway, please open an issue to let us know or even better fork the CSVS and send us a pull request with your changes.
  4. There are already other documents that cover container security like the CIS Docker Benchmark or NIST Application Container Security Guide. Why do we need the CSVS?
    Existing documents often contain more than 100 pages or are using a lot of running text. We think there should be a clear standard that allows you to go through and actually verify your level of security related to container solutions.
  5. Is there any referencing from the CSVS to other standards and vice-versa?
    Unfortunately not yet, but we made sure to cover at least the CIS Docker Benchmark and NIST Application Container Security Guide.

Related Projects

Asvs-satellite.jpgOWASP Resources

Project Resources

PDF Download

Word Download

Source Code (GitHub)

Project Leader

Sven Vetsch @

Licensing

Creative Commons Attribution ShareAlike 4.0

Classifications

Project Type Files DOC.jpg
Incubator Project Owasp-builders-small.png
Owasp-defenders-small.png
Creative Commons Attribution ShareAlike 4.0 License