Splunk Enterprise Security

Symantec add on - CIM Compliance error

astatrial
Contributor

Hello,
I am collecting SEP data from the next sources :

  1. symantec:ep:behavior:file
  2. symantec:ep:agent:file
  3. symantec:ep:scan:file
  4. symantec:ep:agt_system:file
  5. symantec:ep:security:file
  6. symantec:ep:risk:file
  7. symantec:ep:scm_system:file
  8. symantec:ep:proactive:file
  9. symantec:ep:policy:file

In my dedicated index "Symantec" i can see events about symantec:ep:scan:file, which supposed to be normalized to "Malware" datamodel according to the docs docs.
I can also see the "malware" tag, as well as the "attack" tag.
For some reason, when i query the datamodel, i don't see any sign for symantec logs.
The Intrusion Detection datamodel for example, does has symantec logs .

Can anyone help me figuring this out ?

Thanks !!

0 Karma

lakshman239
Influencer

You need to configure the index/sourcetypes to be used in the datamodel.

In the Enterprise Security App, navigate to Confgure->CIM Setup and select your Intrusion detection and add your index there. You need to do the same for other datamodels as well as per https://docs.splunk.com/Documentation/AddOns/released/SymantecEP/Sourcetypes

0 Karma

astatrial
Contributor

Is this operation doesn't built in the add-on ?
I will check it though, Thanks !

0 Karma

lakshman239
Influencer

No, generally, the add-ons have sourcetype, but not index, as each customer may choose to have diff ones. So, as part of any data on-boarding /CIM compliance, you would need to do the above step.

0 Karma
Get Updates on the Splunk Community!

Index This | Why did the turkey cross the road?

November 2025 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Feel the Splunk Love: Real Stories from Real Customers

Hello Splunk Community,    What’s the best part of hearing how our customers use Splunk? Easy: the positive ...