Repository navigation
2.8.0: WAF rules for Cloudflare, AWS WAF and Azure WAF
WAF rules (#10). The detections stay the same; this release adds a way to block part of them at the edge.
- New
waf/folder with rules for Cloudflare (dashboard expressions, Rulesets API JSON, IP list, Terraform), AWS WAF (rule group and IP sets as CLI input, CloudFormation and Terraform) and Azure WAF (Application Gateway and Front Door policies in Bicep and ARM, and plain custom rule arrays). - Rule groups by tier. Block: framework user agents, probe markers and framework headers, unsigned
alg:noneJWTs, and the CyberStrikeAI webshell probe in request bodies. Challenge: scanner user agents and reported addresses. Log: AI agent page readers and the Hermes results folder. Opt-in: WSUS services reached from the internet. Addresses are never blocked by default. - Everything is generated by
tools/build_waf.pyfromwaf/signatures.yamlandiocs/indicators.csv. Addresses past theirreview_bydate are left out (21 of 163 on this release). tests/waf/run_tests.pychecks the generated files on every platform: every signature value, every address, hand-written requests (most of them near misses), and a replay of the Suricata test flows so the WAF rules and the Suricata rules they mirror agree. It also checks platform limits, the AWS files against the wafv2 API model, and CI runscfn-lint,terraform validateandaz bicep build.waf/README.mdanswers whether a WAF is needed and where it fits next to the SIEM and IDS content.
Also in this release, from 2.7.3
- Elastic conversions of DNS, proxy and web server rules now use ECS field names:
dns.question.name,url.original,url.domain,url.path,url.queryanduser_agent.original. Before, they kept the Sigma names and matched nothing in an ECS index. Contributed by @tridev-tej in #9, closing #4. tools/validate.pyfails if a generated Elastic query still uses one of those Sigma field names.