kingfisher/data/rules/duffel.yml
Mick Grove 0f953f59a5 pattern_requirements for rules — Post-regex character-class gating to cut false positives without lookarounds. Authors can now require minimum counts of digits, uppercase, lowercase, and special characters, with an optional custom special-char set.
Why: Hyperscan doesn’t support lookaheads/behinds, so many “must contain X and Y” checks had to be baked into the regex (hurting readability) or were impossible. pattern_requirements applies lightweight, in-memory checks after a match is found, keeping patterns fast and clean.
2025-11-04 13:55:31 -05:00

34 lines
901 B
YAML

rules:
- name: Duffel API Token
id: kingfisher.duffel.1
pattern: |
(?xi)
\b
(
duffel_(?:test|live)_[a-z0-9_\-=]{43}
)
\b
pattern_requirements:
min_digits: 2
min_entropy: 3.2
confidence: medium
examples:
- DUFFEL_TOKEN=duffel_test_qwertyuiopasdfghjklzxcvbnm123456789abcdefgh
- 'Authorization: "Bearer duffel_live_abcd1234efgh5678ijkl9012mnop3456qrstuvwxyza"'
references:
- https://duffel.com/docs/api
validation:
type: Http
content:
request:
method: GET
url: https://api.duffel.com/airlines
headers:
Authorization: 'Bearer {{ TOKEN }}'
Accept: application/json
Duffel-Version: v1
response_matcher:
- report_response: true
- type: StatusMatch
status:
- 200