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

33 lines
No EOL
812 B
YAML

rules:
- name: Buildkite API Key
id: kingfisher.buildkite.1
pattern: |
(?xi)
(
bkua_[a-z0-9]{40}
)
\b
pattern_requirements:
min_digits: 2
min_lowercase: 1
min_entropy: 3.5
confidence: medium
examples:
- bkua_3c7019c2e4b6e76fe2e8bdde7c154e3c1a211743
references:
- https://buildkite.com/docs/apis/rest-api/access-token
validation:
type: Http
content:
request:
method: GET
url: https://api.buildkite.com/v2/access-token
headers:
Authorization: "Bearer {{ TOKEN }}"
response_matcher:
- report_response: true
- type: StatusMatch
status: [200]
- type: WordMatch
words: ['"uuid"', '"user"']