In part 2 of our 3-part series, we walk you through how to use Splunk Security-Content, Attack Range and CircleCI to do detection development, continuous testing and deployment as a workflow in your SOC.
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.
Today, we’re excited to reveal the first iteration of this new way forward for security operations, with the general availability (GA) of Splunk Mission Control.
Security leaders, including chief information security officers (CISOs) face new security challenges as well as opportunities. They need to start by contemplating the long-term impact of the COVID-19 crisis on various aspects of the security program.
Using Splunk Enterprise to check for CVE-2020-1350 vulnerabilities and detect exploitation attempts using wire data on Windows DNS servers.
This blog is part 1 of a 3 part series that includes a step-by-step walk-through of how to use Splunk Security-Content, Attack Range and CircleCI to do detection development, continuous testing, and deployment as a workflow in your security operation center.