NOTE: This Repository contains a work in progress preview of the planned next mayor secureCodeBox Release. You can find the current stable release here https://github.com/secureCodeBox/secureCodeBox. The release of version 2.0 is still at least some month away but you can already get a sneak peak here 😀. The release will contain a mayor re architecture of the secureCodeBox. More details will follow soon in a series of blog articles.
secureCodeBox is a kubernetes 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.
For additional documentation aspects please have a look at our:
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:
- 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.
- 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 (last 4 mayor releases supported:
1.15,1.16,1.17&1.18)
# Deploy secureCodeBox Operator
kubectl create namespace securecodebox-system
helm -n securecodebox-system install securecodebox-operator ./operator/
# Elasticsearch Persistence Provider Deployment
helm install persistence-elastic ./persistence/persistence-elastic/
# Deploy definitions for the integrated scanners
helm install amass ./integrations/amass/
helm install kube-hunter ./integrations/kube-hunter/
helm install nikto ./integrations/nikto
helm install nmap ./integrations/nmap/
helm install ssh-scan ./integrations/ssh_scan/
helm install sslyze ./integrations/sslyze/
helm install zap ./integrations/zap/
# Now everything is installed. You can try deploying scans from the `operator/config/samples/` directory
# E.g. www.securecodebox.io sslyze scan
kubectl apply apply -f operator/config/samples/execution_v1_scan/sslyze_securecodebox_io.yaml
# Then get the current State of the Scan by running:
kubectl get scans
Code of secureCodeBox is licensed under the Apache License 2.0.
You are welcome, please join us on... 👋
secureCodeBox is an official OWASP project.
Contributions are welcome and extremely helpful 🙌
Sponsored by iteratec GmbH - secureCodeBox.io