nuke/lib/policy/expressions
Xe Iaso 22c47f40d1
feat(expressions): add randInt function to allow making rules nondeterministic (#578)
This seems counter-intuitive at first glance, but let me cook.

One of the problems with Anubis is that the rule matching is super
deterministic. This means that attackers can figure out what patterns
they are hitting and change things to bypass them.

The randInt function lets you have rulesets behave nondeterministically.
This is a very easy way to hang yourself, but can be great to
psychologically mess with scraper operators. Consider this rule:

```yaml
- name: deny-lightpanda-sometimes
  action: DENY
  expression:
    all:
      - userAgent.matches("LightPanda")
      - randInt(16) >= 4
```

It would match about 75% of the time.

Signed-off-by: Xe Iaso <me@xeiaso.net>
2025-05-28 16:36:27 -04:00
..
environment.go feat(expressions): add randInt function to allow making rules nondeterministic (#578) 2025-05-28 16:36:27 -04:00
http_headers.go feat(checker): add CEL for matching complicated expressions (#421) 2025-05-03 14:26:54 -04:00
http_headers_test.go feat(checker): add CEL for matching complicated expressions (#421) 2025-05-03 14:26:54 -04:00
join.go feat(checker): add CEL for matching complicated expressions (#421) 2025-05-03 14:26:54 -04:00
join_test.go style: apply structpack & goimport (#469) 2025-05-09 12:54:15 -04:00
README.md feat(checker): add CEL for matching complicated expressions (#421) 2025-05-03 14:26:54 -04:00
url_values.go feat(checker): add CEL for matching complicated expressions (#421) 2025-05-03 14:26:54 -04:00
url_values_test.go feat(checker): add CEL for matching complicated expressions (#421) 2025-05-03 14:26:54 -04:00

Expressions support

The expressions support is based on ideas from go-away but with different opinions about how things should be done.