πŸ’‘ As you build out your #security program, you should know some of the more critical #Windows Event IDs to monitor and what they mean. Read on to get a list of critical Event IDs for:

πŸ‘‰ Logon events
πŸ‘‰ Privilege use
πŸ‘‰ Windows Server
πŸ‘‰ Microsoft Defender Antivirus

Plus, learn how you can build a single source of log information that enables observability and visibility across your environment. πŸ™Œ

https://graylog.org/post/25-linux-logs-to-collect-and-monitor/ #CyberSecurity #SIEM #InfoSec #GraylogLabs

Is your financial institution as safe as it could be from #ransomware and other cyber threats? πŸ€” Groups like FIN7, Lazarus Group, and Carbanak often specifically target banks with sophisticated attacks, like SWIFT compromises and more. 🏦 πŸ’°

But have no fear, Graylog + Model Context Protocol (MCP) are here to help! 🦸πŸ’ͺ Today, Seth Goldhammer is walking you through a real world example where a bank in the north east, with a simple #Anthropic prompt, learned that it needed to understand the threat landscape and map it to their current log sources β€” to enable threat detection content in their current #Graylog deployment.

See how they mastered the challenge and enabled real-time, context-aware recommendations based on their actual environment, in our latest Graylog Labs article.πŸ‘‡

https://graylog.org/post/how-to-use-mcp-to-optimize-your-graylog-security-detections/

#CyberThreats #FinServ #GraylogLabs #TDIR #ThreatDetection

Let's take a look back today at #Graylog's first-ever Engineering Hackathon! πŸ‘©β€πŸ’» πŸŽ‰ In October, we gave our engineers a full week to build whatever they believed would make #Graylog better. This allowed them to step away from their day-to-day work, explore new ideas, experiment with technologies, and more.

Some highlights included:
🌎 Watching new collaborations take place across our teams & different continents
πŸ’» A project built primarily via vibe coding
πŸ› οΈ The project "Portal Gun" team turning a 10-year old POC into a dynamic, usable UI element that you can try out in Graylog 7.1 Alpha 1

Read all about it, in our latest blog by Dev Team Engineering Directors Rob Curtis and Martina Kohn!πŸ‘‡

https://graylog.org/post/the-first-graylog-engineering-hackathon/ #Hackathon #CyberSecurity #Devs #GraylogLabs

πŸ’‘It's time to learn about some features and fixes that will make your daily work in #Graylog smoother. πŸ‘ In our most recent blog by the Graylog Development Team, we're highlighting a minor but functional enhancement β€” Graylog time-range stepping.

To fix manual time-range adjustment limitations we now have two new time range navigation buttons that let you step forward and backward through your logs, one time range at a time. ⬅️ ➑️ Learn more about this feature here: https://graylog.org/post/sliding-through-log-time-space/

πŸ“» And, stay tuned for more in this series from Konrad Merz and the rest of the Graylog Development Team! #CyberSecurity #SIEM #APISecurity #GraylogLabs

New from #GraylogLabs! Read up on the Caddy Webserver Content Pack that quickly turns raw logs into structured, searchable insights. It's available in Illuminate 6.4 & a Graylog Enterprise or #Security license + delivers ready-to-use parsing rules, streams & dashboards. graylog.org/post/caddy-w...

Caddy Webserver Data in Graylo...
Caddy Webserver Data in Graylog

Discover how to use Graylog 6.4 Illuminate to collect, parse, and analyze Caddy web server logs for enhanced security, insights, and troubleshooting

Graylog

It's time to tune in for the latest from #GraylogLabs! πŸ“Ί 🎊 Today we're taking about the new Caddy Webserver Content Pack. Say what? No, not #Caddyshack! β›³ 🦫 Caddy Webserver! πŸ–₯️

This new content pack is going to help you quickly turn raw logs into structured, searchable insights. πŸ”ŽπŸ’‘ πŸ™Œ It's available in Illuminate 6.4 and a Graylog Enterprise or Graylog #Security license, and delivers ready-to-use parsing rules, streams, and dashboards. 🚚

Read up on:
❓ What this pack does
πŸͺ΅ Getting logs into #Graylog
🫡 Why you should log Caddy Webserver logs
πŸ” How this helps you quickly detect anomalies, identify suspicious requests, and feed relevant data directly into your #TDIR workflows

https://graylog.org/post/caddy-webserver-data-in-graylog/ #cybersecurity #threatdetection #incidentresponse #SIEM

Out now! πŸ‘‰ Our latest #GraylogLabs post on the exploitation of the SharePoint RCE. CVE-2025-53770 and CVE-2025-53771 are critical remote code execution vulnerabilities (CVSS base score 9.8) impacting #Microsoft #SharePoint. In this blog, we simulate the exploitation of this SharePoint RCE vulnerability and analyze the resulting telemetry inside #Graylog. πŸ“Š

Read an overview on this attack, follow along as we emulate the adversary SharePoint RCE, explain the requirements to detect this exploit, review indicators, and more. Plus, learn about actionable threat hunting and detection strategies.πŸ‘‡

https://graylog.org/post/adversary-tradecraft-exploitation-of-the-sharepoint-rce/ #SharePointRCE #CVE #cybersecurity #CVE202553770 #CVE202553771

Do you know the clues to look for? πŸ” When threat actors gain unauthorized access to systems, networks, or devices, they leave behind clues. And your #security team needs to be able to find them to mitigate risk.πŸ•΅ Indicators of compromise (IOCs) can be network-based, host-based, email-based, behavioral, or third-party. πŸ€”

Learn more about IOCs, plus check out this handy list of 17 common IOCs to look out for! πŸ‘€πŸ‘‡

https://graylog.org/post/17-common-indicators-of-compromise/?utm_content=337930088&utm_medium=social&utm_source=linkedin&hss_channel=lcp-2783090 #GraylogLabs #cybersecurity #threatactors

Getting your data from GitLab’s audit logs into #Graylog for centralized analysis is easier than you might think! πŸ€” πŸ˜ƒ Take a look at this two-part guide to learn how. πŸ‘οΈ πŸ‘‡

This guide covers:
πŸ‘‰ Prerequisites for setting up the raw HTTP input for GitLab
πŸ‘‰ Configuring GitLab to stream logs
πŸ‘‰ Configuring the raw HTTP input
πŸ‘‰ Requirements for enriching GitLab logs with Illuminate
πŸ‘‰ Setup Instructions
And more...

Ready to centralize GitLab Logs? Check out the guide to get started with wiring up GitLab’s Audit Event Streaming, and you'll be on your way to visualizing enriched events in a purpose-built dashboard! Let's go...

https://graylog.org/post/bringing-gitlab-logs-into-focus-with-graylog/ #cybersecurity #logmanagement #loganalysis #GraylogLabs

Knowing the most common indicators of compromise (IoCs) can improve your key threat detection and response (TDIR) metrics. πŸ‘ And, if you are keeping an eye out for common IOCs, then you're able to take a more proactive approach to #security. So, let's dig in and learn all about IOCs! πŸ™Œ

IoCs fall into the following categories:
πŸ”Ή Network-based
πŸ”Ή Host-based
πŸ”Ή Email-based
πŸ”Ή Behavioral
πŸ”Ή Third-party

In this blog we outline 17 common indicators of compromise, including:
🚦 Network traffic anomalies
πŸ’» Unusual sign-in attempts
πŸ—ΊοΈ Geographical anomalies
⚠️ Privilege account irregularities
πŸ”„ Changes to systems configurations
πŸ–₯️ Unexpected software installations or updates
πŸ“‚ Numerous requests for the same file
🫴 Unusual Domain Name Systems (DNS) requests
πŸ“– Swells in database read volume
❗ HTML response sizes
πŸš₯ Mismatched port-application traffic
πŸ€” Suspicious registry or system file changes
πŸ“§ Influx of spam emails
⬅️ Moved or aggregated data
πŸ€– Non-human website traffic
πŸ“± Changes to mobile devices
🚫 System outages or reduced performance

Read on and learn about the details for each of these 17 common IoCsβ€”so that you can be ready to search your environment for clues that will help you confirm security incidents and/or data breaches.

https://graylog.org/post/17-common-indicators-of-compromise/ #threatdetection #incidentresponse #cybersecurity #GraylogLabs