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)
1
Part 1: Understanding Different QRadar Components and Architecture
5
Part 2: QRadar Features and Deployment
10
Part 3: Understanding QRadar Apps, Extensions, and Their Deployment

How does QRadar UBA work?

As mentioned earlier, before installing the UBA app, there is the prerequisite that a DSM named IBM Sense is installed on QRadar. We learned what DSMs are in Chapters 4 and 5. To reiterate, DSMs are device support modules installed on QRadar, so that QRadar parses incoming data in a consumable format.

When the UBA app is installed, UBA rules are also added. These UBA rules look for certain event data, and if it is found, a sense event is triggered. This sense event is then consumed by the UBA app. The sense event will have a certain risk value as well as a username associated with it. When UBA consumes this sense event, it in turn increases the risk value of the user. Risk scores are stored in the QRadar PostgreSQL database.

The IBM Sense DSM is used to parse the sense event in this case. Once the Sense DSM parses the event, the event is evaluated against all the rules in QRadar, including the just-added UBA rules too. If the event matches the rule conditions...