| ID | Technique | Tactic |
|---|
Detection: Cisco AI Defense Allowed Sensitive Response
Description
Detects Cisco AI Defense response events that were allowed and matched a privacy guardrail for personally identifiable information or payment card data. These events may indicate that sensitive information was returned to an AI application user and should be reviewed promptly.
Search
1`cisco_ai_defense`
2event_action="allow"
3event_message_type="response"
4
5
6| eval guardrail_ruleset_type=mvjoin('event_policy_guardrail_assocs{}.policy_guardrail_assoc.guardrail_avail_ruleset.guardrail_ruleset_type', ", "),
7
8 guardrail_entity_name=mvjoin('event_policy_guardrail_assocs{}.policy_guardrail_assoc.guardrail_avail_entity.guardrail_entity_name', ", "),
9
10 application_name=if(isnotnull('genai_application.application_name') AND len(trim('genai_application.application_name'))>0, 'genai_application.application_name', "unknown"),
11
12 connection_name=if(isnotnull('connection.connection_name') AND len(trim('connection.connection_name'))>0, 'connection.connection_name', "unknown"),
13
14 policy_name='policy.policy_name'
15
16
17| where mvfind('event_policy_guardrail_assocs{}.policy_guardrail_assoc.guardrail_avail_ruleset.guardrail_ruleset_type', "(?i)\\bPII\\b
18|personally identifiable information
19|\\bPCI\\b
20|payment card industry")>=0
21
22
23| table _time event_date event_id event_message_type event_action resource_type
24 application_id application_name connection_id connection_name model.model_name
25 policy_name guardrail_ruleset_type guardrail_entity_name
26
27
28| `cisco_ai_defense_allowed_sensitive_response_filter`
Data Source
| Name | Platform | Sourcetype | Source |
|---|---|---|---|
| Cisco AI Defense Alerts | Other | 'cisco:ai:defense' |
'not_applicable' |
Macros Used
| Name | Value |
|---|---|
| cisco_ai_defense | sourcetype=cisco:ai:defense |
| cisco_ai_defense_allowed_sensitive_response_filter | search * |
cisco_ai_defense_allowed_sensitive_response_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Annotations
Default Configuration
This detection is configured by default in Splunk Enterprise Security to run with the following settings:
| Setting | Value |
|---|---|
| Disabled | true |
| Cron Schedule | 0 * * * * |
| Earliest Time | -70m@m |
| Latest Time | -10m@m |
| Schedule Window | auto |
| Creates Finding (Notable) | Yes |
| Rule Title | %name% |
| Rule Description | %description% |
| Notable Event Fields | user, dest |
| Creates Intermediate Finding (Risk Event) | No |
TTP detections generate a Finding (Notable) and may generate Intermediate Findings (Risk Events) for associated entities.
Implementation
Install and configure the Cisco Security Cloud app to ingest Cisco AI Defense alerts into Splunk with the cisco:ai:defense sourcetype. Confirm that extraction is enabled for the required fields as shown in the detection search. Configure the "cisco_ai_defense" macro to match the index, source, and sourcetype used in your environment.
Known False Positives
Authorized testing, demonstrations, or approved workflows may allow responses that match PII or PCI guardrails. Review the application owner, policy, response context, and whether the data was expected to be disclosed.
Associated Analytic Story
Finding
| Title | Entity Field | Entity Type | Risk Score |
|---|---|---|---|
| Cisco AI Defense allowed response [$event_id$] for application [$application_name$] matched privacy guardrail(s) [$guardrail_ruleset_type$] and entity [$guardrail_entity_name$]. | application_name | other | 50 |
Detection Testing
| Test Type | Status | Dataset | Source | Sourcetype |
|---|---|---|---|---|
| Validation | ✅ Passing | N/A | N/A | N/A |
| Unit | ✅ Passing | Dataset | not_applicable |
cisco:ai:defense |
| Integration | ✅ Passing | Dataset | not_applicable |
cisco:ai:defense |
Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI.
Alternatively you can replay a dataset into a Splunk Attack Range
Source: GitHub |
Version: 1