Splunk Enterprise Security

Splunk Security Content - How to implement/ create macros?

inventsekar
SplunkTrust
SplunkTrust

Hi All.. 

As you may be aware of Splunk's Security Content.. for example, for linux user creation https://research.splunk.com/endpoint/51fbcaf2-6259-11ec-b0f3-acde48001122/
on this, there are 2 macros they use.. one macro is:

https://github.com/splunk/security_content/blob/develop/macros/security_content_summariesonly.yml

actually how to implement/create this macro please. 

 

thanks and best regards,
Sekar

PS - If this or any post helped you in any way, pls consider upvoting, thanks for reading !
Labels (1)
0 Karma

meetmshah
Builder

More often than not, you will have macro already available from the app (ESCU/SSE/ES), all you need to do is update the parameters from Settings -> Advance Search -> Search macros -> Select Macro and update the same.

 

Please note that in the cases like whitelisting indexes for CIM or other such applications, there would be configuration page where it will ask you for the list of indexes and it will automatically update the Macro.

 

If this answer have helped you, feel free to accept the same 🙂

0 Karma

meetmshah
Builder

Hello, Just checking through if the issue was resolved or you have any further questions?

0 Karma

PickleRick
SplunkTrust
SplunkTrust

But what's the problem? You implement this macro as if you did with any other macro.

https://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Definesearchmacros

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...