Project: secureCodeBox (Provisioning / Security & Compliance)
File: README.DockerHub-Scanner.md

<!-- SPDX-FileCopyrightText: the secureCodeBox authors SPDX-License-Identifier: Apache-2.0 --> <!-- .: IMPORTANT! :. -- This file is generated automatically with `helm-docs` based on the following template files: ./.helm-docs/templates.gotmpl (general template data for all charts) ./chart-folder/.helm-docs.gotmpl (chart specific template data) Please be aware of that and apply your changes only within those template files instead of this file. Otherwise your changes will be reverted/overwritten automatically due to the build process `./.github/workflows/helm-docs.yaml` -- --> <p align="center"> <a href="https://opensource.org/licenses/Apache-2.0"><img alt="License Apache-2.0" src="https://img.shields.io/badge/License-Apache%202.0-blue.svg"/></a> <a href="https://github.com/secureCodeBox/secureCodeBox/releases/latest"><img alt="GitHub release (latest SemVer)" src="https://img.shields.io/github/v/release/secureCodeBox/secureCodeBox?sort=semver"/></a> <a href="https://owasp.org/www-project-securecodebox/"><img alt="OWASP Lab Project" src="https://img.shields.io/badge/OWASP-Lab%20Project-yellow"/></a> <a href="https://artifacthub.io/packages/search?repo=securecodebox"><img alt="Artifact HUB" src="https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/securecodebox"/></a> <a href="https://github.com/secureCodeBox/secureCodeBox/"><img alt="GitHub Repo stars" src="https://img.shields.io/github/stars/secureCodeBox/secureCodeBox?logo=GitHub"/></a> <a href="https://infosec.exchange/@secureCodeBox"><img alt="Mastodon Follower" src="https://img.shields.io/mastodon/follow/111902499714281911?domain=https%3A%2F%2Finfosec.exchange%2F"/></a> </p> <p align="center"> <img alt="secureCodeBox Logo" src="https://www.securecodebox.io/img/Logo_Color.svg" width="250px"/> </p> is an automated and scalable open source solution that can be used to integrate various security vulnerability scanners with a simple and lightweight interface. The secureCodeBox mission is to support DevSecOps Teams to make it easy to automate security vulnerability testing in different scenarios. With the secureCodeBox we provide a toolchain for continuous scanning of applications to find the low-hanging fruit issues early in the development process and free the resources of the penetration tester to concentrate on the major security issues. The secureCodeBox project is running on . To install it you need , a package manager for Kubernetes. It is also possible to start the different integrated security vulnerability scanners based on a docker infrastructure. You can find resources to help you get started on our including instruction on how to and guides to help you with it. `latest` (represents the latest stable release build) tagged releases, e.g. `3.0.0`, `2.9.0`, `2.8.0`, `2.7.0` This `scanner` image is intended to work in combination with the corresponding `parser` image to parse the scanner `findings` to generic secureCodeBox results. For more information details please take a look at the or

```bash docker pull securecodebox/scanner-zap-advanced ``` The Zed Attack Proxy (ZAP) is one of the worlds most popular free security tools and is actively maintained by hundreds of international volunteers*. It can help you automatically find security vulnerabilities in your web applications while you are developing and testing your applications. It's also a great tool for experienced pentesters to use for manual security testing. To learn more about the ZAP scanner itself visit . Listed below are the arguments supported by the `zap-advanced-scan` script. The command line interface can be used to easily run server scans: `-t www.example.com` ```bash usage: zap-client [-h] -z ZAPURL [-a APIKEY] [-c CONFIGFOLDER] -t TARGET [-o OUTPUTFOLDER] [-r XML,XML-plus,JSON,JSON-plus,HTML,HTML-plus,MD] OWASP secureCodeBox ZAP Client (can be used to automate ZAP instances based on YAML configuration files.) optional arguments: -h, --help show this help message and exit -z ZAPURL, --zap-url ZAPURL The ZAP API Url used to call the ZAP API. -a APIKEY, --api-key APIKEY The ZAP API Key used to call the ZAP API. -c CONFIGFOLDER, --config-folder CONFIGFOLDER The path to a local folder containing the additional ZAP configuration YAMLs used to configure ZAP. -t TARGET, --target TARGET The target to scan with ZAP. -o OUTPUTFOLDER, --output-folder OUTPUTFOLDER The path to a local folder used to store the output files, eg. the ZAP Report or logfiles. -r XML,XML-plus,JSON,JSON-plus,HTML,HTML-plus,MD, --report-type XML,XML-plus,JSON,JSON-plus,HTML,HTML-plus,MD The ZAP Report Type. ``` You are welcome, please join us on... secureCodeBox is an official project. ](https://opensource.org/licenses/Apache-2.0) As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained). As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.