secureCodeBox /secureCodeBox
secureCodeBox (SCB) - continuous secure delivery out of the box
★ 994⑂ 185👁 25⑃ 3,132● 650▤ 95
+1
Daily
994
stars
185
forks
25
watchers
3,132
prs
650
issues
95
releases
README
OWASP secureCodeBox _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. Overview - OWASP secureCodeBox - Overview - Purpose of this Project - Quickstart - Architecture Overview - Upgrading - License - Community - Contributing - Sponsors - Author Information For additional documentation aspects please have a look at our documentation website: Purpose of this Project 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-hanging fruit) and therefore will probably 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][secdevops-objspec] in the software engineering journal [OBJEKTSpektrum][objspec]. Quickstart You can find resources to help you get started on our documentation website including instruction on how to install the secureCodeBox and guides to help you run your first scans with it. Architecture Overview !secureCodeBox Architecture Upgrading For the steps required for upgrading your secureCodeBox installation, see Upgrading. License Code of secureCodeBox is licensed under the [Apache License 2.0][scb-license]. Community You are welcome, please join us on... 👋 - [GitHub Discussions (Questions & Feedback)][scb-github-discussions] - [GitHub Issues (Bugs & Featur
Top issues
#2896Make OSS Project More Resillient8 comments · 2025-02-07#2105Hooks are not starting when scan has "Errored" state6 comments · 2023-11-19#995Integrate interaction server as active service into SCB5 comments · 2022-02-22#132Scan Jobs hang if Cluster / Namespace uses Istio5 comments · 2020-09-29#3186Request promotion of project to Production Level.4 comments · 2025-08-07#3139Parser occasionally fails with "The specified key does not exist" due to early startup4 comments · 2025-07-18#2347improve security Deployment Workload4 comments · 2024-03-08#3224Remove legacy ScanCompletionHook migration logic3 comments · 2025-08-20
Discussions
#3837v5.9.00 comments · 2026-09-15#3828v5.9.0-rc.00 comments · 2026-09-10#3717v5.8.00 comments · 2026-07-07#3636v5.7.00 comments · 2026-05-11#3530Installation CA for dependency-track hook0 comments · 2026-02-26#3513v5.6.00 comments · 2026-02-17#3461v5.5.00 comments · 2026-01-14#3436v5.4.00 comments · 2025-12-18
Latest release
v5.9.0 v5.9.0 2026-09-15What's Changed 🦺Important Notices - Minio has unpublished their previous still available official docker images. secureCodeBox 5.9.0 switches the default S3 bucket for the quick start setups to garage for a quick, self hosted S3 bucket in Kubernetes. Setups using a external S3 Buckets e.g. AWS S3, Google Storage, Hetzner Buckets, etc. are unaffected. If you upgrade a instance using the included Minio instance it will be switched to Garage. Any in-progress scans will fail and have to be restarted. Any scans created after the upgrade will then use the new garage bucket. See https://github