Skip to content

Highlight WAF protection in README #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BB-AI-Arena merged 1 commit into from
Aug 12, 2026
Merged

Highlight WAF protection in README #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,9 @@

</div>

> [!TIP]
> **WAF-protected by default.** The Docker deployment puts the official **OWASP ModSecurity Core Rule Set 4.25 LTS** in blocking mode in front of every published Intent Gate API route. The backend has no host port, while SQL injection probes, unsupported methods, malformed JSON, and oversized payloads are rejected at the edge. [Explore the WAF design and tuning guide →](docs/WAF.md)

> [!IMPORTANT]
> User Intent AI Security is an early proof of concept, not a standalone security boundary. Reliable enforcement requires integration at a command broker, shell host, agent tool API, container runtime, or privileged-operation choke point that cannot be bypassed.

Expand Down
Loading