forked from mirrors/kingfisher
0f953f59a5
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.
66 lines
No EOL
1.7 KiB
YAML
66 lines
No EOL
1.7 KiB
YAML
rules:
|
|
- name: Finicity API token
|
|
id: kingfisher.finicity.1
|
|
pattern: |
|
|
(?xi)
|
|
\b
|
|
finicity
|
|
(?:.|[\n\r]){0,32}?
|
|
(?:SECRET|PRIVATE|ACCESS|KEY|TOKEN)
|
|
(?:.|[\n\r]){0,32}?
|
|
\b
|
|
(
|
|
[a-f0-9]{32}
|
|
)
|
|
\b
|
|
pattern_requirements:
|
|
min_digits: 2
|
|
min_entropy: 3.5
|
|
confidence: medium
|
|
examples:
|
|
- finicity_api_token = "5600675afe3e1a0fa76d5b99b30ca7a8"
|
|
validation:
|
|
type: Http
|
|
content:
|
|
request:
|
|
method: GET
|
|
url: https://api.finicity.com/aggregation/v2/transactions
|
|
headers:
|
|
Content-Type: application/json
|
|
x-finicity-app-key: '{{ TOKEN }}'
|
|
response_matcher:
|
|
- report_response: true
|
|
- type: WordMatch
|
|
words:
|
|
- '"transactions":'
|
|
|
|
- name: Finicity client secret
|
|
id: kingfisher.finicity.2
|
|
pattern: |
|
|
(?xi)
|
|
\b
|
|
finicity
|
|
(?:.|[\n\r]){0,64}?
|
|
\b
|
|
(
|
|
[a-z0-9]{20}
|
|
)
|
|
\b
|
|
min_entropy: 3.5
|
|
confidence: medium
|
|
examples:
|
|
- finicity-clientsecret = 'geruj4LFyu0NBeBOnQvo'
|
|
validation:
|
|
type: Http
|
|
content:
|
|
request:
|
|
method: POST
|
|
url: https://api.finicity.com/aggregation/v2/customers
|
|
headers:
|
|
Content-Type: application/json
|
|
x-finicity-secret: '{{ TOKEN }}'
|
|
response_matcher:
|
|
- report_response: true
|
|
- type: StatusMatch
|
|
status:
|
|
- 200 |