kingfisher/data/rules/launchdarkly.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
886 B
YAML

rules:
- name: LaunchDarkly Access Token
id: kingfisher.launchdarkly.1
pattern: |
(?xi)
launchdarkly
(?:.|[\n\r]){0,32}?
\b
(
[a-z0-9_\-=]{40}
)
pattern_requirements:
min_digits: 2
min_entropy: 3.2
confidence: medium
examples:
- LAUNCHDARKLY_TOKEN=api-123abc456def789ghi012jkl345mno678pqr
- '"launchdarkly": "ld-abcdefghijklmno1234567890pqrstuvwxzab"'
references:
- https://docs.launchdarkly.com/sdk/api/
validation:
type: Http
content:
request:
method: GET
url: https://app.launchdarkly.com/api/v2/members
headers:
Authorization: '{{ TOKEN }}'
Accept: application/json
response_matcher:
- report_response: true
- type: StatusMatch
status:
- 200