Splunk Enterprise Security

Enterprise security engineering tasks

vikram1583
Explorer

Hi in my company they recently migrated to Spunk(Enterprise Security) from QRador so installation part is done rule creation is done
and Vulnerability center , asset data feed,user data feed,tuning correlation searches,
work flow, run books done, so now they are moving to Engineering on demand work so they asked me to prepare engineering tasks for next few months so i don't have idea what tasks will be i never worked on ES
Can some one help me please.

0 Karma
1 Solution

smoir_splunk
Splunk Employee
Splunk Employee

If you've installed the product, set up correlation searches and asset and identity correlation, plus tuned the searches and confirmed that Vulnerability Center is working, I'd say that the next steps are for the SOC analysts and security teams to actually use the product, and then get engineering-on-demand tasks from those teams.

Are there integrations with tools that those teams use that aren't set up? Are there additional data sources that they might want later? Or some adaptive response or workflow actions that they might want set up so that they can more easily respond to and remediate issues? Those are some tasks that might come up later, but you'll have to work with the security teams to understand their use cases and what they cannot do with ES now that it's set up that might require extending it. You can find documentation about how to write new adaptive response actions on dev.splunk.com: http://dev.splunk.com/view/enterprise-security/SP-CAAAFBF

View solution in original post

smoir_splunk
Splunk Employee
Splunk Employee

If you've installed the product, set up correlation searches and asset and identity correlation, plus tuned the searches and confirmed that Vulnerability Center is working, I'd say that the next steps are for the SOC analysts and security teams to actually use the product, and then get engineering-on-demand tasks from those teams.

Are there integrations with tools that those teams use that aren't set up? Are there additional data sources that they might want later? Or some adaptive response or workflow actions that they might want set up so that they can more easily respond to and remediate issues? Those are some tasks that might come up later, but you'll have to work with the security teams to understand their use cases and what they cannot do with ES now that it's set up that might require extending it. You can find documentation about how to write new adaptive response actions on dev.splunk.com: http://dev.splunk.com/view/enterprise-security/SP-CAAAFBF

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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...