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

All-in-one deployment

In this type of deployment, the processing of the data is done only by the Console. So, there will be no data processors (other than the Console) in this type of deployment, and there will be no separate Event Processor or Flow Processor in the deployment either. Processors, as we know, are responsible for processing and storing data. In all-in-one deployment, the aim is that the Console would be the only component where we will have the data stored or have a Data Node attached to the Console.

Event and Flow Collectors can be added to this type of deployment. Also, QNI can be added, which will collect flows and send data to the Console for processing.

The following diagrams are a few examples of all-in-one deployment.

In the following example, we see a QRadar Console that is collecting data from different Log Sources and Flow Sources. We also have QRadar UI access via a web browser. Administrators and analysts can log in via the QRadar GUI to configure...