Skip to content

Commit a7425f0

Browse files
authored
Update cisco_ai_defense_security_alerts.yml
1 parent 44ffd97 commit a7425f0

File tree

1 file changed

+26
-6
lines changed

1 file changed

+26
-6
lines changed

detections/application/cisco_ai_defense_security_alerts.yml

Lines changed: 26 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,32 @@ description: The search surfaces alerts from the Cisco AI Defense product for po
99
data_source:
1010
- Cisco AI Defense Alerts
1111
search: |-
12-
`cisco_ai_defense`| rename genai_application.application_name as application_name | rename connection.connection_name as connection_name | stats count values(event_message_type) values(event_action) values(policy.policy_name) as policy_name values(event_policy_guardrail_assocs{}.policy_guardrail_assoc.guardrail_avail_entity.guardrail_entity_name) as guardrail_entity_name values(event_policy_guardrail_assocs{}.policy_guardrail_assoc.guardrail_avail_ruleset.guardrail_ruleset_type) as guardrail_ruleset_type by connection_name application_name
13-
| eval severity=case(
14-
policy_name="AI Runtime Latency Testing - Prompt Injection", "critical",
15-
policy_name="AI Runtime Latency Testing - Code Detection", "high",
16-
guardrail_ruleset_type IN ("Toxicity"), "medium" )
17-
| table severity policy_name connection_name application_name guardrail_ruleset_type guardrail_entity_name | where severity != "" |`cisco_ai_defense_security_alerts_filter`'
12+
`cisco_ai_defense`
13+
| rename genai_application.application_name as application_name
14+
| rename connection.connection_name as connection_name
15+
```Aggregating data by model name, connection name, application name, application ID, and user ID```
16+
| stats count
17+
values(event_message_type) as event_message_type
18+
values(event_action) as event_action
19+
values(policy.policy_name) as policy_name
20+
values(event_policy_guardrail_assocs{}.policy_guardrail_assoc.guardrail_avail_entity.guardrail_entity_name) as guardrail_entity_name
21+
values(event_policy_guardrail_assocs{}.policy_guardrail_assoc.guardrail_avail_ruleset.guardrail_ruleset_type) as guardrail_ruleset_type
22+
by model.model_name connection_name application_name application_id user_id
23+
```Evaluating severity based on policy name and guardrail ruleset type```
24+
| eval severity=case(
25+
policy_name IN ("AI Runtime Latency Testing - Prompt Injection"), "critical",
26+
policy_name IN ("AI Runtime Latency Testing - Code Detection"), "high",
27+
guardrail_ruleset_type IN ("Toxicity"), "medium",
28+
true(), "low"
29+
)
30+
```Calculating risk score based on severity level```
31+
| eval risk_score=case(
32+
severity="critical", 100,
33+
severity="high", 75,
34+
severity="medium", 50,
35+
severity="low", 25
36+
)
37+
| table model.model_name, user_id, event_action, application_id, application_name, severity, risk_score, policy_name, connection_name, guardrail_ruleset_type, guardrail_entity_name |`cisco_ai_defense_security_alerts_filter`'
1838
how_to_implement: To enable this detection, you need to ingest alerts from the Cisco AI Defense product. This can be done by using this app from splunkbase - Cisco Security Cloud and ingest alerts into the cisco:ai:defense sourcetype.
1939
known_false_positives: False positives may vary based on Cisco AI Defense configuration; monitor and filter out the alerts that are not relevant to your environment.
2040
references:

0 commit comments

Comments
 (0)