GuillaumeHemmen/docker-bench-security
1
0
Fork 0
mirror of https://github.com/docker/docker-bench-security.git synced 2025-01-18 16:22:33 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update README.md

Browse source 
Clarified that log files are created inside the container so that new users (ie me) don't spend ages wondering where the logs are!
This commit is contained in:
Jo Cook 2021-02-23 12:15:22 +00:00 committed by GitHub
parent 7c881b4b0b
commit cf7c50bf33
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -83,7 +83,7 @@ version 1.13.0 or later.
```sh ```sh
-b optional Do not print colors -b optional Do not print colors
-h optional Print this help message -h optional Print this help message
-l FILE optional Log output in FILE -l FILE optional Log output in FILE inside docker bench container
-c CHECK optional Comma delimited list of specific check(s) -c CHECK optional Comma delimited list of specific check(s)
-e CHECK optional Comma delimited list of specific check(s) to exclude -e CHECK optional Comma delimited list of specific check(s) to exclude
-i INCLUDE optional Comma delimited list of patterns within a container or image name to check -i INCLUDE optional Comma delimited list of patterns within a container or image name to check
@ -91,7 +91,7 @@ version 1.13.0 or later.
``` ```
By default the Docker Bench for Security script will run all available CIS tests By default the Docker Bench for Security script will run all available CIS tests
and produce logs in the current directory named `docker-bench-security.sh.log.json` and produce logs in the current directory inside the container, named `docker-bench-security.sh.log.json`
and `docker-bench-security.sh.log`. and `docker-bench-security.sh.log`.
The CIS based checks are named `check_<section>_<number>`, e.g. `check_2_6` The CIS based checks are named `check_<section>_<number>`, e.g. `check_2_6`
and community contributed checks are named `check_c_<number>`. and community contributed checks are named `check_c_<number>`.