Splunk Enterprise Security

CIM help

splunkcol
Builder

I'm reviewing the logs to make sure the fields match the Splunk Enterprise Security CIM and datamodels.

The query shows me this percentage, understanding that they are the fields that are required versus the fields that it is finding, in this order of ideas, to adjust these fields I must create an alias or I must perform an "extract" either by regular expressions or tabs?

cp_log.png

cp_log2.png

0 Karma
1 Solution

rajashekar_s
Path Finder

Per documentation, for example the action field in network traffic datamodel, prescribed values are allowed, blocked and teardown. But you have many values under action field. As suggested above, you can create a calculated field like

| eval action=case((action="xxx" OR action="yyy"),"allowed",1=1,"blocked")

Doing this on all recommended fields will increase you compliance %

View solution in original post

rajashekar_s
Path Finder

Per documentation, for example the action field in network traffic datamodel, prescribed values are allowed, blocked and teardown. But you have many values under action field. As suggested above, you can create a calculated field like

| eval action=case((action="xxx" OR action="yyy"),"allowed",1=1,"blocked")

Doing this on all recommended fields will increase you compliance %

richgalloway
SplunkTrust
SplunkTrust

Yes, you need to extract fields or create aliases to increase your CIM compliance.

---
If this reply helps you, Karma would be appreciated.
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...