Detection rules › Kusto
Palo Alto Prisma Cloud - Anomalous access key usage
'Detects anomalous API key usage activity.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access |
Rule body
id: bd602b90-f7f9-4ae9-bf8c-3672a24deb39
name: Palo Alto Prisma Cloud - Anomalous access key usage
description: |
'Detects anomalous API key usage activity.'
severity: Medium
status: Available
requiredDataConnectors:
- connectorId: PaloAltoPrismaCloud
dataTypes:
- PaloAltoPrismaCloud
queryFrequency: 1h
queryPeriod: 1h
triggerOperator: gt
triggerThreshold: 0
tactics:
- InitialAccess
relevantTechniques:
- T1078
query: |
let threshold = 10;
PaloAltoPrismaCloud
| where ResourceType =~ 'Login'
| where EventResult =~ 'Failed'
| where EventMessage has 'access key'
| summarize count() by UserName, bin(TimeGenerated, 5m)
| where count_ > threshold
| extend AccountCustomEntity = UserName
entityMappings:
- entityType: Account
fieldMappings:
- identifier: Name
columnName: AccountCustomEntity
version: 1.0.1
kind: Scheduled
Stages and Predicates
Parameters
let threshold = 10;
Stage 1: source
PaloAltoPrismaCloud
Stage 2: where
| where ResourceType =~ 'Login'
Stage 3: where
| where EventResult =~ 'Failed'
Stage 4: where
| where EventMessage has 'access key'
Stage 5: summarize
| summarize count() by UserName, bin(TimeGenerated, 5m)
Stage 6: where
| where count_ > threshold
Stage 7: extend
| extend AccountCustomEntity = UserName
Indicators
These rows show field, operator, and value matches.
| Field | Kind | Values | Search |
|---|---|---|---|
EventMessage | match |
| field:"EventMessage" kind:match value:"access key" |
EventResult | eq |
| field:"EventResult" kind:eq value:"Failed" |
ResourceType | eq |
| field:"ResourceType" kind:eq value:"Login" |
count_ | gt |
| field:"count_" kind:gt value:"10" |
Output fields
These fields are emitted when the rule matches.
| Field | Source |
|---|---|
UserName | summarize |
AccountCustomEntity | extend |