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

36 lines
882 B
YAML

rules:
- name: New Relic Personal API Key
id: kingfisher.newrelic.1
pattern: |
(?xi)
\b
newrelic
(?:.|[\n\r]){0,32}?
(?:SECRET|PRIVATE|ACCESS|KEY|TOKEN)
(?:.|[\n\r]){0,32}?
\b
(
[A-Z0-9_.]{4}
-
[A-Z0-9_.]{42}
)
\b
pattern_requirements:
min_digits: 2
min_entropy: 3.3
confidence: medium
examples:
- newrelic_key = abcd-1234567890abcdef1234567890abcdef1234dd5678
- newrelic_token = 1234-abcdefghijklmnopqrstuvwxyzABCD2342EFGHIJKL
validation:
type: Http
content:
request:
method: GET
headers:
X-Api-Key: '{{ TOKEN }}'
url: https://api.newrelic.com/v2/servers.json
response_matcher:
- report_response: true
- type: StatusMatch
status: [200]