Hello family, here is a concern I am experiencing: I have correlation searches that are activated or enable, and to verify that they are receiving CIM-compliant data that are required to make it work, when I search their name one-by-one on a Splunk Enterprise Security dashboard pane to make sure the dashboard populates properly, nothing comes out. But when I run the query of this correlation searches on the Search and Reporting pane of Splunk, I will see the events populate. I have gone through the Splunk documentation on CIM-Compliance topics already and watched some You Tube videos, but still don't get it...Please any extra sources from anyone that can help me understand very well will be very welcome.
Thanks and best regards.
Also if some search works in one app/for one user and doesn't work in another app/for another user it's often a permissions issue.
Thanks, I really do appreciate!
@ND1 Agreed with @sainag_splunk
Also,
Most ES dashboard expects data in CIM fields or from a specific data model/summary index.
Check fields
Run your correlation search in Search & Reporting
Use the field picker to see if required CIM fields are present
If not, review your field extractions or data model configurations
Check Datamodel
| datamodel <datamodel_name> search
If the data model is empty, review your data sources and field extractions.
Regards,
Prewin
Splunk Enthusiast | Always happy to help! If this answer helped you, please consider marking it as the solution or giving a kudos/Karma. Thanks!
Thanks, I appreciate it!
Also if some search works in one app/for one user and doesn't work in another app/for another user it's often a permissions issue.
Thanks for feedback I really do appreciate!
@ND1 It's not easy to troubleshoot without a screen share, but typically I recommend:
also check
check out this user guide: https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.0/analytics/available-dashboard...
Additional help: If you have Splunk OnDemand Services credits available, I'd recommend using them to walk through this issue with a Splunk expert who can troubleshoot in real-time.
If this Helps, Pleas Upvote.