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

Offense generation and management

When the rule conditions match, the rule action triggers. It completely depends on the options selected in the rule action section for an offense to be generated.

Important note

If all the conditions match and if the indexed property is null, an offense is not generated. For example, if the indexed property is a destination port but the event that triggers the offense does not have a destination port value (the value is null), then the offense is not generated.

This note is for a specific design element with which QRadar ensures that no offense is generated even if rule conditions are matched.

Another peculiar design feature is offense-chaining. Offenses are chained together to provide analysts with a deeper understanding of the security incident. It binds one or more offenses based on the offense index field. This helps analysts relate multiple offenses just by looking at one chained offense. Offense-chaining saves analysts a lot of time...