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

41 lines
No EOL
1.1 KiB
YAML

rules:
- name: Atlassian API token
id: kingfisher.atlassian.1
pattern: |
(?xi)
\b
atlassian
(?:.|[\n\r]){0,32}?
\b
(
[a-z0-9]{24}
)
\b
pattern_requirements:
min_digits: 2
min_lowercase: 1
min_entropy: 3.5
confidence: medium
examples:
- Atlassian_key = "DjayBenyJrtpvydFCzAphcqc"
- "ATLASSIAN_API_TOKEN:'abcdef1234567890abcdef12'"
references:
- https://developer.atlassian.com/cloud/admin/organization/rest/api-group-orgs/#api-v1-orgs-get
validation:
type: Http
content:
request:
url: https://api.atlassian.com/me
headers:
Authorization: "Bearer {{ TOKEN }}"
Accept: "application/json"
method: GET
response_matcher:
- report_response: true
- status:
- 200
type: StatusMatch
- type: WordMatch
words:
- "Unauthorized"
negative: true