Skip to content

Commit 9446ac7

Browse files
committed
updating test
1 parent 6f2ad99 commit 9446ac7

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

detections/application/cisco_ai_defense_security_alerts.yml

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,12 @@ type: Anomaly
88
description: The search surfaces alerts from the Cisco AI Defense product for potential attacks agaisnt the AI models running in your environment. This analytic identifies security events within Cisco AI Defense by examining event messages, actions, and policy names. It focuses on connections and applications associated with specific guardrail entities and ruleset types. By aggregating and analyzing these elements, the search helps detect potential policy violations and security threats, enabling proactive defense measures and ensuring network integrity.
99
data_source:
1010
- Cisco AI Defense Alerts
11-
search: '`cisco_ai_defense ` | 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.connection_name genai_application.application_name application_id| `cisco_ai_defense_security_alerts_filter`'
11+
search: '`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
12+
| eval severity=case(
13+
policy_name="AI Runtime Latency Testing - Prompt Injection", "critical",
14+
policy_name="AI Runtime Latency Testing - Code Detection", "high",
15+
guardrail_ruleset_type IN ("Toxicity"), "medium" )
16+
| table severity policy_name connection_name application_name guardrail_ruleset_type guardrail_entity_name | where severity != "" |`cisco_ai_defense_security_alerts_filter`'
1217
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.
1318
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.
1419
references:
@@ -29,9 +34,6 @@ rba:
2934
- field: application_id
3035
type: other
3136
score: 10
32-
threat_objects:
33-
- field: user_id
34-
type: user
3537
tags:
3638
analytic_story:
3739
- Critical Alerts
@@ -44,7 +46,7 @@ tags:
4446
tests:
4547
- name: True Positive Test
4648
attack_data:
47-
- data: __UPDATE__ the data file to replay. Go to https://github.com/splunk/contentctl/wiki
48-
for information about the format of this field
49-
sourcetype: __UPDATE__ the sourcetype of your data file.
50-
source: __UPDATE__ the source of your datafile
49+
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/suspicious_behaviour/cisco_ai_defense_alerts/cisco_ai_defense.log
50+
source: cisco_ai_defense
51+
sourcetype: cisco:ai:defense
52+

0 commit comments

Comments
 (0)