Skip to content
Merged
10 changes: 8 additions & 2 deletions contentctl.yml
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,12 @@ apps:
version: 3.0.0
description: description of app
hardcoded_path: https://attack-range-appbinaries.s3.us-west-2.amazonaws.com/splunk-add-on-for-okta-identity-cloud_300.tgz
- uid: 7404
title: Cisco Security Cloud
appid: CiscoSecurityCloud
version: 3.0.1
description: description of app
hardcoded_path: https://attack-range-appbinaries.s3.us-west-2.amazonaws.com/cisco-security-cloud_301.tgz
- uid: 6652
title: Add-on for Linux Sysmon
appid: Splunk_TA_linux_sysmon
Expand Down Expand Up @@ -77,9 +83,9 @@ apps:
- uid: 5579
title: Splunk Add-on for CrowdStrike FDR
appid: Splunk_TA_CrowdStrike_FDR
version: 2.0.4
version: 2.0.3
description: description of app
hardcoded_path: https://attack-range-appbinaries.s3.us-west-2.amazonaws.com/splunk-add-on-for-crowdstrike-fdr_204.tgz
hardcoded_path: https://attack-range-appbinaries.s3.us-west-2.amazonaws.com/splunk-add-on-for-crowdstrike-fdr_203.tgz
- uid: 3185
title: Splunk Add-on for Microsoft IIS
appid: SPLUNK_TA_FOR_IIS
Expand Down
14 changes: 14 additions & 0 deletions data_sources/cisco_ai_defense_alerts.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
name: Cisco AI Defense Alerts
id: cbb06880-9dd9-4542-ac60-bd6e1d3c3e4e
version: 1
date: '2024-07-18'
author: Bhavin Patel
description: Data source object for Cisco AI Defense Alerts
source: cisco_ai_defense
sourcetype: cisco:ai:defense
separator:
supported_TA:
- name: Cisco Security Cloud
url: https://splunkbase.splunk.com/app/7404
version: 3.0.1
fields:
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
name: Cisco AI Defense Security Alerts by Application Name
id: 105e4a69-ec55-49fc-be1f-902467435ea8
version: 1
date: '2025-02-14'
author: Bhavin Patel, Splunk
status: experimental
type: Anomaly
description: The search surfaces alerts from the Cisco AI Defense product for potential attacks against 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.
data_source:
- Cisco AI Defense Alerts
search: |-
`cisco_ai_defense`
| rename genai_application.application_name as application_name
| rename connection.connection_name as connection_name
```Aggregating data by model name, connection name, application name, application ID, and user ID```
| stats count
values(user_id) as user_id
values(event_message_type) as event_message_type
values(event_action) as 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 model.model_name connection_name application_name application_id
```Evaluating severity based on policy name and guardrail ruleset type```
| eval severity=case(
policy_name IN ("AI Runtime Latency Testing - Prompt Injection"), "critical",
policy_name IN ("AI Runtime Latency Testing - Code Detection"), "high",
guardrail_ruleset_type IN ("Toxicity"), "medium",
true(), "low"
)
```Calculating risk score based on severity level```
| eval risk_score=case(
severity="critical", 100,
severity="high", 75,
severity="medium", 50,
severity="low", 25
)
| 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_by_application_name_filter`'
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.
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.
references:
- https://www.robustintelligence.com/blog-posts/prompt-injection-attack-on-gpt-4
- https://docs.aws.amazon.com/prescriptive-guidance/latest/llm-prompt-engineering-best-practices/common-attacks.html
drilldown_searches:
- name: View risk events for the last 7 days for - "$application_id$"
search: '| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$application_id$" ) starthoursago=168 | stats count min(_time)
as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message)
as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all)
as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics"
by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
earliest_offset: $info_min_time$
latest_offset: $info_max_time$
rba:
message: Cisco AI Defense Security Alert has been action - [$event_action$] for the application name - [$application_name$]
risk_objects:
- field: application_name
type: other
score: 10
threat_objects: []
tags:
analytic_story:
- Critical Alerts
asset_type: Web Application
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/suspicious_behaviour/cisco_ai_defense_alerts/cisco_ai_defense.log
source: cisco_ai_defense
sourcetype: cisco:ai:defense
4 changes: 4 additions & 0 deletions macros/cisco_ai_defense.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
definition: sourcetype=cisco:ai:defense
description: customer specific splunk configurations(eg- index, source, sourcetype).
Replace the macro definition with configurations for your Splunk Environment.
name: cisco_ai_defense