The Splunk Threat Research Team recently began evaluating ways to generate security content using native Windows event logging regarding PowerShell Script Block Logging to assist enterprise defenders in finding malicious PowerShell scripts.
Prior to implementing Splunk, the branch was missing a single way to analyze data across their ecosystem and security analysts spent too much time on repetitive, manual tasks. But with Splunk they now ingest and analyze data from multiple sources used for day-to-day operational views and can review and investigate processes much faster while freeing up analyst time to focus on critical tasks.
TruSTAR, acquired by Splunk, recently spoke with Alvin Mills, TBA’s Vice President of Information Technology and Security to learn why the organization selected TruSTAR as its intelligence management platform for data-centric security automation.
By tracking network security analytics, IT teams and security engineers can gain centralized visibility into most of the cyber threats they face. They can also monitor their effectiveness in responding to threats.
Adversaries are using PowerShell attacks, but luckily the Splunk Threat Research Team (STRT) has developed PowerShell analytics for Splunk by using the Splunk Attack Range to collect the generated logs, and hunt for suspicious PowerShell.
These monthly postings will feature the favorite security-centric presentations, white papers and customer case studies from various peeps in the Splunk (or not) security world that WE think everyone should read. If you would like to read other months, please take a peek at previous posts in the "Staff Picks" series!