This InSpec compliance profile implement the CIS Docker 1.12.0 Benchmark in an automated way to provide security best-practice tests around Docker daemon and containers in a production environment.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
MONEY: indicates if one needs a paying subscription to use that project you could just add ($) next to the name ([my project - $] (link to my project) )
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/veggiemonk/awesome-docker/pull/351
**Author:** [@ghost](https://github.com/ghost)
**Created:** 6/13/2017
**Status:** ✅ Merged
**Merged:** 6/16/2017
**Merged by:** [@veggiemonk](https://github.com/veggiemonk)
**Base:** `master` ← **Head:** `add-project`
---
### 📝 Commits (1)
- [`a4f37e6`](https://github.com/veggiemonk/awesome-docker/commit/a4f37e62e35c9a9242cec30996b461d873e58bc8) Add CIS Docker Benchmark
### 📊 Changes
**1 file changed** (+3 additions, -1 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+3 -1)
</details>
### 📄 Description
<!-- Congrats on creating an Awesome Docker entry! 🎉 -->
<!-- Please fill in the below placeholders -->
**https://github.com/dev-sec/cis-docker-benchmark**
**This [InSpec](https://github.com/chef/inspec) compliance profile implement the CIS Docker 1.12.0 Benchmark in an automated way to provide security best-practice tests around Docker daemon and containers in a production environment.**
# By submitting this pull request I confirm I've read and complied with the below requirements.
**Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.**
- I have read and understood the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md)
- The project submitted is conform to the quality standards outlined in the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md)
- Go to the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md) and read it again.
RULES (because you probably didn't read the guidelines):
* ORDER: The entries are in lexical order (English letter order)
* CREDIT: Each entry must contains the name of the author with a link to its github account!
* LINK: the link should be to the source code (https://github/account/project) not the website (https://myproject.io <- no!)
* MONEY: indicates if one needs a paying subscription to use that project you could just add ($$$) next to the name ([my project - $$$] (link to my project) )
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/veggiemonk/awesome-docker/pull/351
Author: @ghost
Created: 6/13/2017
Status: ✅ Merged
Merged: 6/16/2017
Merged by: @veggiemonk
Base:
master← Head:add-project📝 Commits (1)
a4f37e6Add CIS Docker Benchmark📊 Changes
1 file changed (+3 additions, -1 deletions)
View changed files
📝
README.md(+3 -1)📄 Description
https://github.com/dev-sec/cis-docker-benchmark
This InSpec compliance profile implement the CIS Docker 1.12.0 Benchmark in an automated way to provide security best-practice tests around Docker daemon and containers in a production environment.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
I have read and understood the contribution guidelines
The project submitted is conform to the quality standards outlined in the contribution guidelines
Go to the contribution guidelines and read it again.
RULES (because you probably didn't read the guidelines):
$) next to the name ([my project -$] (link to my project) )🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.