Enterprise security for those who protect others
The same Kubernetes security infrastructure used by Fortune 500 companies — free, open source, and deployed in a single command. Built specifically for journalists, activists, and human rights organizations.
NGOs get hacked.
Constantly.
This is not theoretical. These are real operations targeting critical entities with life-or-death consequences.
515,000+ Records Stolen
The "Restoring Family Links" program was compromised, shutting down humanitarian workflows designed to reunite missing relatives in conflict zones.
State-Sponsored Intrusion
An organization dedicated to exposing human rights abuses was itself monitored and compromised by highly funded threat actors.
Persistent Harassment
The investigative team exposing international war crimes faces continuous cyber espionage aimed at burning sources and deleting archives.
Defense in Depth
Four decoupled operational layers. Each layer isolates and catches whatever threats bypass the previous boundaries.
Every single container image is automatically audited for CVEs before it reaches the pipeline. Build fails on high vulnerabilities.
Trivy EngineValidates requests to the K8s API against highly strict security profiles. Rejects misconfigured manifests prior to deployment.
Kyverno GuardMonitors system calls and behaviors directly inside the kernels of active containers. Instantly flags shell spawns or privilege elevation.
Falco DaemonMaintains Git as the strict state of truth. Restores deleted or weakened defenses from Git within seconds.
ArgoCD CoreActive Threat Coverage
Practical security solutions matching real exploitation scenarios. Straightforward verification with zero security-theater.
Automated Pipeline
Fully declarative architecture. No state is configured manually after executing the primary script.
Enforced Security Directives
Kyverno-enforced rules mapped straight to global Kubernetes hardening standards. Platform namespaces are isolated from user workloads.
disallow-root-user
Forces non-root identity within the container runtimes. Neutering standard root-based escape vectors entirely.
disallow-privileged
Restricts root access onto host hardware namespaces, denying containerized applications direct hardware kernel control.
disallow-latest-tag
Blocks mutable container tags. Forces pinned, predictable deployment artifacts protecting against upstream supply-chain shifts.
require-limits
Enforces explicit limits on host CPU and memory consumption. Defends cluster against hypervisor starvation and denial of service.
readonly-root-fs
Forces container storage to be strictly read-only at the system level. Prevents arbitrary payload injection and persistent file manipulation.
disallow-host-net
Disables direct access from container space to the raw host network interface. Negates packet sniffing and lateral cluster traversal.
disallow-host-namespaces
Blocks sharing the host PID and IPC namespaces. Containers cannot see or signal host processes or read host shared memory.
secure-ephemeral-containers
Debug containers added with kubectl debug must be pinned, non-root, read-only, unprivileged and cannot mount the app's volumes. Closes a side door into running workloads.
disallow-capabilities
Containers cannot add Linux capabilities like SYS_ADMIN or escalate to root through setuid binaries. Only NET_BIND_SERVICE is allowed.
Learn First, Then Enforce
Already running apps? Start in learning mode: Fortress shows every problem and how to fix it, without breaking anything. Switch to enforce when you are ready.
Learning Mode
Insecure workloads are allowed, but every deploy shows a warning that names the container and the line to change.
One Report, Every Problem
fortress audit report lists what does not meet the policies across the cluster, with instructions to fix each one.
Safe Switch to Enforce
fortress mode enforce refuses while any app would stop working after a restart. Debug containers, namespace isolation and Falco stay active in both modes.
Setup Instructions
Deploy a hardened infrastructure in under five minutes. No custom configuration templates required.
Prerequisites Validation
Verify active access onto a running Kubernetes instance configured with kubectl and helm v3+.
Clone Target Repository
Download and clone the Fortress codebase locally onto your terminal workspace.
Execute Interactive Installer
Initialize the interactive automation script. The setup engine will request your target Git repo config, optional alerts configurations, system passwords, and whether to start in learning or enforce mode.
Operational Validation
Secure tunnels map directly to control portals (Grafana dashboard, ArgoCD, and Falcosidekick runtime view).
$ git clone --branch v2.1.0 https://github.com/JoseLorenzana272/fortress-in-a-box.git
$ cd fortress-in-a-box
# Elevate execution rights and build
$ chmod +x install.sh && ./install.sh
# Define Git Repo, Grafana access, Discord Webhook
# Deploying components to cluster namespaces...
[+] SUCCESS: FORTRESS IS DEPLOYED AND ACTIVE
Tactical Security for Vulnerable Missions
MIT Licensed. Completely Free. Fully Transparent Auditable Code.