Repository navigation
Palisade v3.3.3
Install (Linux)
curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo bashPin to this exact version:
curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo PALISADE_VERSION=v3.3.3 bashRe-running the installer is safe. It upgrades the binary and restarts the service without touching your existing config or database.
Docker
docker run -d --name palisade -p 8080:8080 -v coraza-waf-data:/data ghcr.io/sinhaparth5/palisade-waf:3.3.3Multi-arch (linux/amd64, linux/arm64). Persistent state (waf.db, certs/) lives under /data — mount a volume there. Also published to Docker Hub.
Verify checksums
sha256sum --check checksums.txtchecksums.txt and the SBOM are signed with cosign (keyless, GitHub OIDC). The installer checks the signature when cosign is installed, or check it yourself:
cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
--certificate-identity "https://github.com/sinhaparth5/palisade-waf/.github/workflows/ci.yml@refs/tags/v3.3.3" \
--certificate-oidc-issuer https://token.actions.githubusercontent.comWhat's inside the binary
Everything is embedded, so no external files are needed at runtime:
- Admin UI (HTMX + Tailwind templates + minified JS)
- Bundled GeoLite2 Country database (geo blocking)
- Bundled DB-IP ASN Lite database (ISP/org lookup)
- OWASP Core Rule Set (WAF rules)
The only files created on disk at runtime are waf.db (SQLite) and certs/ (TLS, if enabled).