EdgeAegis
EdgeAegis
Protect several services with one SecLang engine
EdgeAegis runs native OWASP CRS before a request reaches your business. Configure multiple internal functions, VPS origins and load-balancer hostnames in one routing file, with separate credentials for each trust boundary.
Real terminal, real HTTP responses
The isolated VM recording uses curl against two functions and three authenticated HTTPS origins. A SQL injection receives 403 without another origin access; a five-second demonstration ban then expires. The five-second TTL is for this lab, not the production default.
Rules and routing stay separate
Rules and routing stay separate
rules/config.yml selects native rules, policy and your allowlist. origin/config.yml maps public hostname/path patterns to destinations. secret/credentials.yml holds independent origin keys in your private deployment repository.
Internal functions stay behind inspection
A configured function:<business> selects origin/<platform>/<business>/index.js. The shared firewall entry point inspects the request before calling the function, then inspects its response. External origins must verify their own selected key.
Measure the boundaries
Complete CRS compilation and execution are checked before rule updates. Unknown semantics fail visibly. Resource bounds and platform limits still apply; upgraded WebSocket payloads are opaque to SecLang and Worker-only counters are local to an engine instance.
EdgeAegis notes
One firewall, several business origins
EdgeAegis runs native OWASP CRS before a request reaches your business. Configure multiple internal functions, VPS origins and load-balancer hostnames in one routing file, with separate credentials for each trust boundary.