Sendur Sellakumar

The ecosystem of apps and add-ons is a big part of what makes Splunk valuable and useful to so many of our customers. Part of that value is grounded in the portability of apps between our self-managed and full-managed offerings (aka "on-prem" and "Cloud"). However, one area that we've consistently received feedback on is private apps. Specifically, the ability to easily deploy and maintain them in Splunk Cloud Platform in a fully-self-service fashion.

If you’re like most organizations, you’re leveraging Jenkins for all sorts of things. Deployment pipelines, automated API tests, even glorified CRON jobs just to name a few. How Do You Gain Insight Into These Various Types of Pipelines? Build Logs: Good for auditing and troubleshooting but difficult to use for long term metrics trends. Time Series Metrics: Great for establishing the health of Jenkins instances and identifying issues over longer time periods.

This blog is a part of Splunk's Log4j response. For additional resources, check out the Log4Shell Overview and Resources for Log4j Vulnerabilities page. Like most cybersecurity teams, the Splunk Threat Research Team (STRT) has been heads-down attempting to understand, simulate, and detect the Log4j attack vector. This post shares detection opportunities STRT found in different stages of successful Log4Shell exploitation.