Skip to content

IntelMQ is a solution for IT security teams for collecting and processing security feeds using a message queuing protocol.

License

Notifications You must be signed in to change notification settings

certtools/intelmq

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

83313f2 · Jan 13, 2025
Dec 1, 2024
Jun 21, 2021
Jun 21, 2021
Jan 13, 2025
Sep 16, 2024
Jan 3, 2025
Jan 3, 2025
Nov 6, 2023
May 20, 2021
May 20, 2021
Jun 27, 2024
Jun 12, 2023
Jan 3, 2025
May 20, 2021
Aug 27, 2014
May 20, 2021
Nov 30, 2024
Dec 1, 2024
Nov 6, 2023
Nov 6, 2023
Jan 31, 2024
Jan 28, 2022
Nov 6, 2023
Dec 1, 2024

Repository files navigation

IntelMQ

Introduction

IntelMQ is a solution for IT security teams (CERTs & CSIRTs, SOCs abuse departments, etc.) for collecting and processing security feeds (such as log files) using a message queuing protocol. It's a community driven initiative called IHAP1 (Incident Handling Automation Project) which was conceptually designed by European CERTs/CSIRTs during several InfoSec events. Its main goal is to give to incident responders an easy way to collect & process threat intelligence thus improving the incident handling processes of CERTs.

IntelMQ is frequently used for:

  • automated incident handling
  • situational awareness
  • automated notifications
  • as data collector for other tools
  • and more!

The design was influenced by AbuseHelper however it was re-written from scratch and aims at:

  • Reducing the complexity of system administration
  • Reducing the complexity of writing new bots for new data feeds
  • Reducing the probability of events lost in all process with persistence functionality (even system crash)
  • Use and improve the existing Data Harmonization Ontology
  • Use JSON format for all messages
  • Provide easy way to store data into databases and log collectors such as PostgreSQL, Elasticsearch and Splunk
  • Provide easy way to create your own black-lists
  • Provide easy communication with other systems via HTTP RESTful API

It follows the following basic meta-guidelines:

  • Don't break simplicity - KISS
  • Keep it open source - forever
  • Strive for perfection while keeping a deadline
  • Reduce complexity/avoid feature bloat
  • Embrace unit testing
  • Code readability: test with inexperienced programmers
  • Communicate clearly

Contribute

CEF

Footnotes

  1. Incident Handling Automation Project, mailing list: [email protected]