Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Building a Next-Gen SOC with IBM QRadar

You're reading from  Building a Next-Gen SOC with IBM QRadar

Product type Book
Published in Jun 2023
Publisher Packt
ISBN-13 9781801076029
Pages 198 pages
Edition 1st Edition
Languages
Author (1):
Ashish M Kothekar Ashish M Kothekar
Profile icon Ashish M Kothekar
Toc

Table of Contents (18) Chapters close

Preface 1. Part 1: Understanding Different QRadar Components and Architecture
2. Chapter 1: QRadar Components 3. Chapter 2: How QRadar Components Fit Together 4. Chapter 3: Managing QRadar Deployments 5. Part 2: QRadar Features and Deployment
6. Chapter 4: Integrating Logs and Flows in QRadar 7. Chapter 5: Leaving No Data Behind 8. Chapter 6: QRadar Searches 9. Chapter 7: QRadar Rules and Offenses 10. Part 3: Understanding QRadar Apps, Extensions, and Their Deployment
11. Chapter 8: The Insider Threat – Detection and Mitigation 12. Chapter 9: Integrating AI into Threat Management 13. Chapter 10: Re-Designing User Experience 14. Chapter 11: WinCollect – the Agent for Windows 15. Chapter 12: Troubleshooting QRadar 16. Index 17. Other Books You May Enjoy

Understanding queues and buffers

We discussed in the previous chapter how if the number of events being ingested in QRadar is more than the license threshold, a system notification is sent by the console on the UI. Let us dig deeper to discover how events are managed in different scenarios.

Persistent queues

QRadar changed its design concept to introduce persistent queues. This was primarily done to avoid event loss. We understand that there are three basic services in the event pipeline:

  • ecs-ec-ingress
  • ecs-ec
  • ecs-ep

Once the events hit the event pipeline, QRadar ensures that they are ingested successfully.

Imagine that the ecs-ec service has crashed. What will happen to the incoming events? ecs-ec-ingress will still be collecting events and trying to send them to ecs-ec for parsing. If the ecs-ec service is down, then the events coming in are stored temporarily in the ingress persistent queue. Once the ecs-ec service is up and running again, the events...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime