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

Scaling QRadar deployments

Every component has limited resources and, hence, a threshold capacity to collect and process data. Data, as we know, is ingested in the form of events and flows. So, every component has a limit on the number of flows and events that the component can collect and process. These thresholds are measured in terms of EPS and FPM. However, there are ways to scale your deployment. Let’s see what they are in the following sections.

Scaling by adding data nodes

If data – that is, the events and flows – have to be retained for more time than planned, what is needed is more disk space. You can also add processors to the deployment and move a few log sources to the new processor. However, this is not the ideal solution in this case. What you should use is the data node. Adding a data node to a processor and/or the Console will not only provide more disk space to store data but also help searches to become faster.

Scaling by adding processors...