It’s finally here! Check out the agenda for #SuriCon2025 in Montreal, Canada. We deliver to you a breakdown of all the insightful experiences we’re offering this year! https://suricon.net/agenda-montreal/

Don’t miss out on this jam-packed event! Register here: https://www.eventbrite.com/e/suricon2025-montreal-canada-tickets-1299841513959

#Suricata

Hear from Jason Ish (@jish) , on the new Lua capabilities and Suricata library features from Suricata 8. He lets us know why he’s happy to see these improvements and more in the video below!

Tune in:
https://www.youtube.com/watch?v=QzfrIflsEJw&t=2s

#Suricata #Suricata8

Building a network traffic analysis system: Deploying Malcolm on Amazon EC2

This is the first of two blog posts on the AWS Public Sector Blog about deploying Malcolm on Amazon AWS. It covers installing Malcolm on a single EC2 instance. The next post will cover deploying Malcolm on EKS.

For those of you more interested in scaling Malcolm using Kubernetes, you can check out our "still-in-beta" Helm chart and share your feedback in the issue tracker on that repo.

#AWS #EC2 #Malcolm #Zeek #Arkime #NetBox #OpenSearch #Elasticsearch #Suricata #PCAP #NetworkTrafficAnalysis #networksecuritymonitoring #OT #ICS #icssecurity #CyberSecurity #Cyber #Infosec #INL #DHS #CISA #CISAgov

Building a network traffic analysis system: Deploying Malcolm on Amazon EC2 | Amazon Web Services

In this post, we provide step-by-step guidance for deploying Malcolm—an open source network traffic analysis suite—natively on Amazon Elastic Compute Cloud (Amazon EC2), using the on-demand compute, elasticity, and scalability of AWS to eliminate traditional infrastructure overhead. This approach is particularly beneficial for cost-conscious public sector (federal, state, and local), utility, and industrial customers who require network and security monitoring to deliver on their missions.

Amazon Web Services

We were onsite at BSides Las Vegas!
We hope some of you got to see Lukas Sismis and say hi before the conference is over! He’s happy to chat about all things Suricata 8 and SuriCon!

He had some cool #Suricata swag with him.

Peter Manev, Suricata Evangelist, recently spoke on why you should attend SuriCon. He even gave the top three reasons to join the team in Montreal this year. Learn this and more about Suricata 8 in the video below but also at SuriCon this year.

Sign up today!

#SuriCon2025 #Suricata

A big thank you to @greynoise for sponsoring #SuriCon2025 as a Community Partner! They provide real-time, verifiable threat intelligence powered by the largest and most sophisticated internet sensor network. Thank you for supporting this year’s SuriCon!

Learn more about GreyNoise: www.greynoise.io

#SuriCon2025 #Suricata

We’re excited to welcome NEOX as the newest member of the OISF Consortium!

NEOX joins a global network of industry leaders who understand that supporting Suricata is more than goodwill—it’s a vote of confidence in the power and future of open-source. As a provider of high-performance, scalable network visibility solutions, NEOX is committed to driving digital transformation, modernization, and business continuity.

Consortium Members aren’t just users of Suricata—they’re strategic partners investing in its long-term sustainability and innovation. Their support helps keep Suricata free, community-driven, and enterprise-ready.

Learn more about NEOX here:
https://neoxnetworks.com/

#Suricata

Malcolm v25.07.0 includes quite a few new features and enhancements, performance improvements, bug fixes, and component version updates.

If you are updating from a version older than v25.06.0, please read those release notes prior to updating to this version.

  • ✨ Features and enhancements
    • Add IANA service name and description enrichment to Zeek's known_services.log (#705)
    • Improve the speed of pruning files (#710)
    • allow multiple instance of Suricata in PCAP processing mode via UNIX socket (#707)
    • expose Arkime WISE tagging features to the user (#377)
    • handle comma- or semicolon-separated directories for PCAP_PROCESSED_DIRECTORY (to support new live PCAP processing method in Malcolm-Helm) (#702)
    • handle new OPCUA Binary summary logs (#709)
    • incorporate new ANSI C12.22 parser and add corresponding dashboard (#708)
    • overhauled instructions for Deploying Malcolm on Amazon Web Services (AWS) including deploying Malcolm on Amazon Elastic Kubernetes Service (EKS) in Auto Mode
    • install.py script is now a bit more robust in trying to help ensure the correct packages and Python libraries are installed
  • ✅ Component version updates
    • Fluent Bit to v4.0.5
    • Arkime v5.7.1
    • Supercronic v0.2.34
    • OpenSearch and OpenSearch Dashboards v3.1.0
    • Keycloak v26.2.5
    • yq v4.47.1
    • NetBox v4.3.4
      • NetBox Initializers plugin v4.3.0
      • NetBox Topology Views plugin v4.3.0
    • Zeek v7.2.2
    • Spicy v1.13.2
    • urllib3 Python Library to v2.5.0 (addresses CVE-2025-50181)
    • ICSNPP Zeek network analyzer updates
      • BACnet parser fixes for previously unsupported services (see cisagov/icsnpp-bacnet#50 and cisagov/icsnpp-bacnet#51)
      • Ethernet/IP various fixes (cisagov/icsnpp-enip#34 (partial); cisagov/icsnpp-enip#35; cisagov/icsnpp-enip#36; cisagov/icsnpp-enip#37; cisagov/icsnpp-enip#38)
      • GENISYS minor updates (cisagov/icsnpp-genisys#25)
      • OPCUA Binary summary logs (cisagov/icsnpp-opcua-binary#102)
      • S7comm fixes for ACK message processing (cisagov/icsnpp-s7comm#19; cisagov/icsnpp-s7comm#20)
  • 🐛 Bug fixes
    • zeek logs not cleaned by clean-processed-folder.py due to MIME type mismatch (#712)
    • packet capture statistics dashboard not working in Kibana (#704)
    • need to adjust shared object creation script (e.g., dashboards import) for new versions of Kibana (#713)
    • log fingerprinting needs to be examined to avoid unintentional collisions (#715)
    • install.py issues in Rocky Linux, Almalinux (#385)
    • OpenSearch container health check issue when OpenSearch is disabled (#716)
    • investigate NetBox API access via Malcolm's netbox endpoint and mapi endpoint (#701)

Malcolm is a powerful, easily deployable network 🖧 traffic analysis tool suite for network security monitoring 🕵🏻‍♀️.

Malcolm operates as a cluster of containers 📦, isolated sandboxes which each serve a dedicated function of the system. This makes Malcolm deployable with frameworks like Docker 🐋, Podman 🦭, and Kubernetes ⎈. Check out the Quick Start guide for examples on how to get up and running.

Alternatively, dedicated official ISO installer images 💿 for Malcolm and Hedgehog Linux 🦔 can be downloaded from Malcolm's releases page on GitHub. Due to limits on individual files in GitHub releases, these ISO files have been split 🪓 into 2GB chunks and can be reassembled with scripts provided for both Bash 🐧 (release_cleaver.sh) and PowerShell 🪟 (release_cleaver.ps1). See Downloading Malcolm - Installer ISOs for instructions.

As always, join us on the Malcolm discussions board 💬 to engage with the community, or pop some corn 🍿 and watch a video 📼.

#Malcolm #HedgehogLinux #Zeek #Arkime #NetBox #OpenSearch #Elasticsearch #Suricata #PCAP #NetworkTrafficAnalysis #networksecuritymonitoring #OT #ICS #icssecurity #CyberSecurity #Cyber #Infosec #INL #DHS #CISA #CISAgov

Explore how @suricata and CrowdSec work together in this webinar replay hosted by CrowdSec ambassador @flaviuvlaicu 🎉

You'll get a step-by-step walkthrough of the integration and a deep dive into best practices.

Whether you're a security professional, DevOps engineer, or IT administrator, this video is packed with practical insights to help you strengthen your defenses with ease.

🎥 Watch now: https://youtube.com/watch?v=GxR1jqGdN5A

#Suricata #cybersecurity #infosec #community

Proactive Defense: CrowdSec & Suricata Made Easy

YouTube

@gary_alderson hehe thanks! I really wasn't sure what I was getting into, and still have only mastered the basics, but #suricata via #pfSense was luckily pretty straightforward to set up and IPS was ok to get it going.

I do feel like I need to go through the alerts logs quite frequently, but I do enjoy that. After a couple of weeks of custom making the dropsid.conf, you actually can monitor it less and less, just does its thing :)