You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following analytic is to leverage alerts from Splunk AppDynamics SecureApp, which identifies and monitors exploit attempts targeting business applications. The primary attack observed involves exploiting vulnerabilities in web applications, including injection attacks (SQL, API abuse), deserialization vulnerabilities, remote code execution attempts, LOG4J and zero day attacks. These attacks are typically aimed at gaining unauthorized access, exfiltrating sensitive data, or disrupting application functionality.
10
+
11
+
Splunk AppDynamics SecureApp provides real-time detection of these threats by analyzing application-layer events and correlating attack behavior with known vulnerability signatures. This detection methodology helps the Security Operations Center (SOC) by:
12
+
13
+
* Identifying active exploitation attempts in real-time, allowing for quicker incident response.
14
+
* Categorizing attack severity to prioritize remediation efforts based on risk level.
15
+
* Providing visibility into attacker tactics, including source IP, attack techniques, and affected applications.
16
+
* Generating risk-based scoring and contextual alerts to enhance decision-making within SOC workflows.
17
+
* Helping analysts determine whether an attack was merely an attempt or if it successfully exploited a vulnerability.
18
+
19
+
By leveraging this information, SOC teams can proactively mitigate security threats, patch vulnerable applications, and enforce security controls to prevent further exploitation.
20
+
data_source:
21
+
- Splunk AppDynamics Secure Application Alert
22
+
search: |-
23
+
`appdynamics_security` blocked=false
24
+
| rename attackEvents{}.* AS *, detailJson.* AS *, vulnerabilityInfo.* AS *
risk_score=0 AND attackOutcome="EXPLOITED", "high",
35
+
risk_score<=50 AND attackOutcome!="OBSERVED", "medium",
36
+
risk_score=0 AND attackOutcome="ATTEMPTED", "medium",
37
+
risk_score=0, "low",
38
+
risk_score=0 AND attackOutcome="OBSERVED", "low"
39
+
)
40
+
| eval risk_message=case(
41
+
(signature="API" OR signature="LOG4J" OR signature="SSRF"), "An attempt to exploit a ".signature." vulnerability was made from a ".src_category." IP address ".src_ip.". The server ".dest_nt_host." hosting application ".app_name." was accessed, and data may have been exfiltrated to ".socketOut.".",
42
+
(signature="MALIP" OR signature="SQL"), "A vulnerability is being ".attackOutcome." from a ".src_category." IP address ".src_ip.". The server ".dest_nt_host." hosting application ".app_name." was accessed.",
43
+
(signature="DESEREAL"), "The application ".app_name." deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Data which is untrusted cannot be trusted to be well-formed. Malformed data or unexpected data could be used to abuse application logic, deny service, or execute arbitrary code, when deserialized."
how_to_implement: In order to properly run this search, you need to ingest alerts data from AppD SecureApp, specifically ingesting data via HEC. You will also need to ensure that the data is going to sourcetype - `appdynamics_security`. You will need to install the Splunk Add-on for AppDynamics.
47
+
known_false_positives: No known false positives for this detection. If the alerts are noisy, consider tuning this detection by using the _filter macro in this search, and/or updating the tool this alert originates from.
- name: View risk events for the last 7 days for - "$app_name$"
56
+
search: '| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$app_name$") starthoursago=168 | stats count min(_time)
57
+
as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message)
58
+
as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all)
59
+
as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics"
60
+
by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
61
+
earliest_offset: $info_min_time$
62
+
latest_offset: $info_max_time$
63
+
rba:
64
+
message: $risk_message$
65
+
risk_objects:
66
+
- field: app_name
67
+
type: other
68
+
score: 10
69
+
threat_objects:
70
+
- field: src_ip
71
+
type: ip_address
72
+
tags:
73
+
analytic_story:
74
+
- Critical Alerts
75
+
asset_type: Web Application
76
+
mitre_attack_id: []
77
+
product:
78
+
- Splunk Enterprise
79
+
- Splunk Enterprise Security
80
+
- Splunk Cloud
81
+
security_domain: threat
82
+
manual_test: We are dynamically creating the risk_score field based on the severity of the alert in the SPL and that supersedes the risk score set in the detection. Setting these to manual test since otherwise we fail integration testing. The detection is also failing on unit-testing as some of the fields set in the observables are empty.
Copy file name to clipboardExpand all lines: detections/deprecated/cisco_secure_application_alerts.yml
+26-27Lines changed: 26 additions & 27 deletions
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
name: Cisco Secure Application Alerts
2
2
id: 9982bff4-fc5d-49a3-ab9e-2dbbab2a711b
3
-
version: 2
4
-
date: '2025-05-02'
3
+
version: 3
4
+
date: '2025-08-04'
5
5
author: Ryan Long, Bhavin Patel, Splunk
6
-
status: production
6
+
status: deprecated
7
7
type: Anomaly
8
8
description: |
9
9
The following analytic is to leverage alerts from Cisco SecureApp, which identifies and monitors exploit attempts targeting business applications. The primary attack observed involves exploiting vulnerabilities in web applications, including injection attacks (SQL, API abuse), deserialization vulnerabilities, remote code execution attempts, LOG4J and zero day attacks. These attacks are typically aimed at gaining unauthorized access, exfiltrating sensitive data, or disrupting application functionality.
@@ -17,31 +17,30 @@ description: |
17
17
* Helping analysts determine whether an attack was merely an attempt or if it successfully exploited a vulnerability.
18
18
19
19
By leveraging this information, SOC teams can proactively mitigate security threats, patch vulnerable applications, and enforce security controls to prevent further exploitation.
20
-
data_source:
21
-
- Cisco Secure Application AppDynamics Alerts
20
+
data_source: []
22
21
search: |-
23
-
`appdynamics_security` blocked=false
24
-
| rename attackEvents{}.attackOutcome AS attackOutcome, "attackEvents{}.vulnerabilityInfo.*" AS *
risk_score=0 AND attackOutcome="EXPLOITED", "high",
35
-
risk_score<=50 AND attackOutcome!="OBSERVED", "medium",
36
-
risk_score=0 AND attackOutcome="ATTEMPTED", "medium",
37
-
risk_score=0, "low",
38
-
risk_score=0 AND attackOutcome="OBSERVED", "low"
39
-
)
40
-
| eval risk_message=case(
41
-
(signature="API" OR signature="LOG4J" OR signature="SSRF"), "An attempt to exploit a ".signature." vulnerability was made from a ".src_category." IP address ".src_ip.". The server ".dest_nt_host." hosting application ".app_name." was accessed, and data may have been exfiltrated to ".socketOut.".",
42
-
(signature="MALIP" OR signature="SQL"), "A vulnerability is being ".attackOutcome." from a ".src_category." IP address ".src_ip.". The server ".dest_nt_host." hosting application ".app_name." was accessed.",
43
-
(signature="DESEREAL"), "The application ".app_name." deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Data which is untrusted cannot be trusted to be well-formed. Malformed data or unexpected data could be used to abuse application logic, deny service, or execute arbitrary code, when deserialized."
44
-
)
22
+
`appdynamics_security`
23
+
| rename attackEvents{}.* AS *, detailJson.* AS *, vulnerabilityInfo.* AS *
risk_score=0 AND attackOutcome="EXPLOITED", "high",
34
+
risk_score<=50 AND attackOutcome!="OBSERVED", "medium",
35
+
risk_score=0 AND attackOutcome="ATTEMPTED", "medium",
36
+
risk_score=0, "low",
37
+
risk_score=0 AND attackOutcome="OBSERVED", "low"
38
+
)
39
+
| eval risk_messege=case(
40
+
(signature="API" OR signature="LOG4J" OR signature="SSRF"), "An attempt to exploit a ".signature." vulnerability was made from a ".src_category." IP address ".src_ip.". The server ".dest_nt_host." hosting application ".app_name." was accessed, and data may have been exfiltrated to ".socketOut.".",
41
+
(signature="MALIP" OR signature="SQL"), "A vulnerability is being ".attackOutcome." from a ".src_category." IP address ".src_ip.". The server ".dest_nt_host." hosting application ".app_name." was accessed.",
42
+
(signature="DESEREAL"), "The application ".app_name." deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Data which is untrusted cannot be trusted to be well-formed. Malformed data or unexpected data could be used to abuse application logic, deny service, or execute arbitrary code, when deserialized."
43
+
)
45
44
| `cisco_secure_application_alerts_filter`
46
45
how_to_implement: In order to properly run this search, you need to ingest alerts data from AppD SecureApp, specifically ingesting data via HEC. You will also need to ensure that the data is going to sourcetype - `appdynamics_security`. You will need to install the Splunk Add-on for AppDynamics.
47
46
known_false_positives: No known false positives for this detection. If the alerts are noisy, consider tuning this detection by using the _filter macro in this search, and/or updating the tool this alert originates from.
0 commit comments