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

37 lines
966 B
YAML

rules:
- name: SonarCloud API Token
id: kingfisher.sonarcloud.1
pattern: |
(?xi)
\b
sonar
(?:.|[\n\r]){0,32}?
(?:SECRET|PRIVATE|ACCESS|KEY|TOKEN)
(?:.|[\n\r]){0,32}?
\b
(
[0-9a-z]{40}
)
\b
pattern_requirements:
min_digits: 2
min_entropy: 2.5
examples:
- sonar_api_token=abcdef0123456789abcdef0123456789abcdef23
validation:
type: Http
content:
request:
headers:
Authorization: "Basic {{ TOKEN | append: ':' | b64enc }}"
Accept: application/json
method: GET
url: https://sonarcloud.io/api/user_tokens/search
response_matcher:
- report_response: true
- type: StatusMatch
status: [200]
- type: WordMatch
match_all_words: true
words:
- '"tokens":'