Splunk Enterprise Security

Drill-down and Next Step are not read in Incident Review

zksvc
Communicator

Hi There, 

I got issue Drill-down and Next Step are not read in Incident Review, i create Splunk Lab for Research And Development by myself. I just install Splunk Enterprise and Enterprise Security (nothing another external apps) and i ingest DVWA to my Splunk. As you know DVWA has various vulnerabilities, and I want to utilize this as a log that I will then manage in Splunk. Therefore, I made a rule regarding uploading inappropriate files. The query is like this 

 

index=lab_web sourcetype="apache:access" 
| rex field=_raw "\[(?<Time>[^\]]+)\] \"(?<Method>\w+) (?<Path>/DVWA/vulnerabilities/upload/[^/]+\.\w+) HTTP/1.1\" (?<Status>\d{3}) \d+ \"(?<Referer>[^\"]+)\" \"(?<UserAgent>[^\"]+)\""
| eval FileName = mvindex(split(Path, "/"), -1)
| eval FullPath = "http://localhost" . Path
| where match(FileName, "\.(?!jpeg$|png$)[a-zA-Z0-9]+$")
| table Time, FileName, FullPath, Status

 

In that correlation, I added notables that were filled in from the drill-down and also the next step. 

zksvc_0-1730344214222.png

But why when I enter the incident review, the drill-down and next steps that I created are not readable?

zksvc_1-1730344526884.png

Maybe there is an application that I haven't installed or something else?

I will attach my full correlation setting include with notable, drill-down, and Next Steps.

 

Splunk Enterprise Version : 9.3.1

Enterprise Security Version : 7.3.2

0 Karma

meetmshah
Builder

Hello @zksvc Was the notable created after you updated the next actions - or was it already generated and later you updated the Correlation Search?

0 Karma

zksvc
Communicator

I create notable manually and i update next actions at the same time when i create notable

0 Karma

zksvc
Communicator

Anyone don't have same problem here ? 

0 Karma
Get Updates on the Splunk Community!

Now Available: Cisco Talos Threat Intelligence Integrations for Splunk Security Cloud ...

At .conf24, we shared that we were in the process of integrating Cisco Talos threat intelligence into Splunk ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Easily Improve Agent Saturation with the Splunk Add-on for OpenTelemetry Collector

Agent Saturation What and Whys In application performance monitoring, saturation is defined as the total load ...