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

Getting to know DLC

So far we have seen that to ingest data into QRadar, we need QRadar software to be installed on the VM or bare-metal servers, to have QRadar instances in the cloud, or to have QRadar appliances. But what if a customer does not want to invest in installing QRadar collector software or does not want to have an event collector? Can we still ingest events into QRadar? And if so, how?

Some customers may not have the bandwidth to procure QRadar boxes or maintain them. In this case, they can install an event collection function on a Linux machine that they already have running. This is not a dedicated event collector but a Linux box, which is installed with free software from IBM and is able to send a limited number of logs to QRadar deployment. The customer definitely needs the QRadar console in this case, but they do not require a separate event collector to collect events.

Some of the very high-security networks do not allow any inbound traffic. In such networks...