secureCodeBox is a docker based, modularized toolchain for continuous security scans of your software project. Its goal is to orchestrate and easily automate a bunch of security-testing tools out of the box.

• Purpose of this Project
• Quickstart
• How Does it Work?
• Architecture
• Roadmap

For additional documentation aspects please have a look at our:

• User Guide
• Developer Guide

The typical way to ensure application security is to hire a security specialist (aka penetration tester) at some point in your project to check the application for security bugs and vulnerabilities. Usually, this check is done at a later stage of the project and has two major drawbacks:

1. Nowadays, a lot of projects do continuous delivery, which means the developers deploy new versions multiple times each day. The penetration tester is only able to check a single snapshot, but some further commits could introduce new security issues. To ensure ongoing application security, the penetration tester should also continuously test the application. Unfortunately, such an approach is rarely financially feasible.
2. Due to a typically time boxed analysis, the penetration tester has to focus on trivial security issues (low-hangig fruits) and therefore will not address the serious, non-obvious ones.

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 purpose of secureCodeBox is not to replace the penetration testers or make them obsolete. We strongly recommend to run extensive tests by experienced penetration testers on all your applications.

Important note: The secureCodeBox is no simple one-button-click-solution! You must have a deep understanding of security and how to configure the scanners. Furthermore, an understanding of the scan results and how to interpret them is also necessary.

There is a german article about Security DevOps – Angreifern (immer) einen Schritt voraus in the software engineering journal OBJEKTSpektrum.

• kubernetes

# Deploy redis for the engine
helm install redis stable/redis --set cluster.slaveCount=0 --set cluster.enabled=false

# Deplyo Minio (min.io) for file storage.
# You can configure to use a hosted solution (aws s3 / digitalocean spaces ...) if you don't want to run it your self. Change the config in engine/engine-deployment for that.
helm install minio stable/minio --set defaultBucket.enabled=true --set defaultBucket.name=securecodebox

# NOTE: Before deploying the engine you'll need to either
kubectl apply -f engine/engine-deployment.yaml

# Deploy the ScanJobDefinition and ScanJobs
kubectl apply -f dispatcher/scan-job-crd.yaml -f dispatcher/parse-job-crd.yaml
kubectl apply -f integrations/nmap/nmap-scanjob-definition.yaml -f integrations/amass/amass-scanjob-definition.yaml -f integrations/ssh_scan/ssh-scan-scanjob-definition.yaml

# Deploy the ParseJobDefinition and ParseJobs
kubectl apply -f dispatcher/parse-job-crd.yaml
kubectl apply -f integrations/nmap/nmap-parsejob-definition.yaml -f integrations/amass/amass-parsejob-definition.yaml -f integrations/ssh_scan/ssh-scan-parsejob-definition.yaml

# Deploy Dispatcher
kubectl apply -f dispatcher/dispatcher-deployment.yaml

# Elasticsearch Persistence Provider Deployment
helm install elasticsearch elastic/elasticsearch --version 7.4.0 --set replicas=1 --set minimumMasterNodes=1 --set image=docker.elastic.co/elasticsearch/elasticsearch-oss
helm install kibana elastic/kibana --version 7.4.0 --set image=docker.elastic.co/kibana/kibana-oss

kubectl apply -f persistence/elasticsearch/persistence-elk-deployment.yaml

Code of secureCodeBox is licensed under the Apache License 2.0.

You are welcome, please join us on... 👋

• GitHub
• Slack
• Twitter

secureCodeBox is an official OWASP project.

Contributions are welcome and extremely helpful 🙌

Sponsored by iteratec GmbH - secureCodeBox.io