kingfisher/data/rules/airbrake.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

39 lines
No EOL
1,000 B
YAML

rules:
- name: Airbrake User Key
id: kingfisher.airbrake.1
pattern: |
(?xi)
\b
airbrake
(?:.|[\n\r]){0,32}?
(
[A-Z0-9-]{40}
)
\b
pattern_requirements:
min_digits: 2
min_uppercase: 1
min_lowercase: 1
min_entropy: 4.5
confidence: medium
examples:
- airbrake secretKey= a1B2c3D4e5F6g7H8i9J0k1L2m3N4o5P6q7R8s9T0
- "airbrakeToken: 'a1B2c3D4e5F6g7H8i9J0k1L2m3N4o5P6q7R8s9T0'"
references:
- https://docs.airbrake.io/docs/devops-tools/api/#list-projects-v4
validation:
type: Http
content:
request:
headers:
Content-Type: application/json
method: GET
response_matcher:
- report_response: true
- status:
- 200
type: StatusMatch
- words:
- '"id"'
type: WordMatch
url: https://api.airbrake.io/api/v4/projects?key={{ TOKEN }}