One of the biggest challenges in the field of log analysis is being able to connect the dots and understand the underlying story connecting them. Applications and machines are generating an increasing amount of log data, making it extremely difficult to separate the wheat from the chaff.
WordPress may power the majority or the internet, but Joomla! is the second most popular CMS on the planet, representing 6.1% of all known CMS websites. So we felt it was important to integrate it directly into our external website security and vulnerability scanner. Sitting alongside special checks for WordPress, Drupal and SilverStripe websites, we scan potential issues with the core version of Joomla! and any plugins installed.
Today, we are excited to announce the beta release of Stackdriver Kubernetes Monitoring, which lets you observe Kubernetes in a comprehensive fashion, simplifying operations for both developers and operators.
April brought us new bugfix releases of Icinga 2 v2.8 and Icinga Web v2.5. Carsten released new versions for the Grafana module for Icinga Web 2.
You’ve always been able to get observability for your Ruby apps by instrumenting them with our SDK, affectionately known as libhoney. Unfortunately, instrumenting code you’ve already written is nobody’s favourite job. If only there were some way to automate the repetitive parts, so you could get instant insight into what your app is doing in production, and then focus your effort on augmenting that insight with the information that’s unique to your app!
In my last post, I gave a high-level overview how to select a threat intelligence vendor and how to integrate indicators of compromise (IOCs) into your SIEM or log management environment. In this post, I will describe in detail how to use the Threat Intelligence plugin that ships with Graylog. I’ll start with the steps necessary to prepare your data, then explain how to activate the feature and how to configure it for use.
