Book Image

Building a Next-Gen SOC with IBM QRadar

By : Ashish M Kothekar
Book Image

Building a Next-Gen SOC with IBM QRadar

By: Ashish M Kothekar

Overview of this book

This comprehensive guide to QRadar will help you build an efficient security operations center (SOC) for threat hunting and need-to-know software updates, as well as understand compliance and reporting and how IBM QRadar stores network data in real time. The book begins with a quick introduction to QRadar components and architecture, teaching you the different ways of deploying QRadar. You’ll grasp the importance of being aware of the major and minor upgrades in software and learn how to scale, upgrade, and maintain QRadar. Once you gain a detailed understanding of QRadar and how its environment is built, the chapters will take you through the features and how they can be tailored to meet specifi c business requirements. You’ll also explore events, flows, and searches with the help of examples. As you advance, you’ll familiarize yourself with predefined QRadar applications and extensions that successfully mine data and find out how to integrate AI in threat management with confidence. Toward the end of this book, you’ll create different types of apps in QRadar, troubleshoot and maintain them, and recognize the current security challenges and address them through QRadar XDR. By the end of this book, you’ll be able to apply IBM QRadar SOC’s prescriptive practices and leverage its capabilities to build a very efficient SOC in your enterprise.
Table of Contents (18 chapters)
Part 1: Understanding Different QRadar Components and Architecture
Part 2: QRadar Features and Deployment
Part 3: Understanding QRadar Apps, Extensions, and Their Deployment

Understanding queues and buffers

We discussed in the previous chapter how if the number of events being ingested in QRadar is more than the license threshold, a system notification is sent by the console on the UI. Let us dig deeper to discover how events are managed in different scenarios.

Persistent queues

QRadar changed its design concept to introduce persistent queues. This was primarily done to avoid event loss. We understand that there are three basic services in the event pipeline:

  • ecs-ec-ingress
  • ecs-ec
  • ecs-ep

Once the events hit the event pipeline, QRadar ensures that they are ingested successfully.

Imagine that the ecs-ec service has crashed. What will happen to the incoming events? ecs-ec-ingress will still be collecting events and trying to send them to ecs-ec for parsing. If the ecs-ec service is down, then the events coming in are stored temporarily in the ingress persistent queue. Once the ecs-ec service is up and running again, the events...