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


Before the 7.3 version of QRadar, there were two types of licenses – one for appliance activation and one for the capacity of the appliance in terms of EPS or FPM. For QRadar version 7.4 and above, the only type of license that exists is for the capacity. All the licenses are added to the console, and it creates a license pool. From the license pool, a QRadar administrator can distribute the license capacity to processors.

Note that licenses are applied to processors and not to collectors. This is because even though data is collected by a collector, it is processed and stored by a processor. If you have a license of 30,000 EPS and the number of EPS received on the collector is more than 30,000, events can be buffered, parsed, and then sent to the processor where they are stored. There is a limit to the number of events that can be buffered. If the number of EPS is consistently more than the license threshold, the administrator will see a License Threshold warning...