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

35 lines
918 B
YAML

rules:
- name: Infracost API Token
id: kingfisher.infracost.1
pattern: |
(?xi)
\b
(
ico-[a-z0-9]{32}
)
\b
pattern_requirements:
min_digits: 2
min_entropy: 3.3
confidence: medium
examples:
- export INFRACOST_API_KEY=ico-abcdefabcdefabcdefabcdefabcdefab
- '"infracost": "ico-1234567890abcdef1234567890abcdef"'
references:
- https://www.infracost.io/docs/api_reference/
validation:
type: Http
content:
request:
method: POST
url: https://pricing.api.infracost.io/graphql
headers:
X-Api-Key: '{{ TOKEN }}'
Content-Type: application/json
Accept: application/json
body: '{"query":"{ ping }"}'
response_matcher:
- report_response: true
- type: StatusMatch
status:
- 200