Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
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 Accelerate your security operations and detect cyber threats effectively

Arrow left icon
Product type Paperback
Published in Jun 2023
Publisher Packt
ISBN-13 9781801076029
Length 198 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Ashish Kothekar Ashish Kothekar
Author Profile Icon Ashish Kothekar
Ashish Kothekar
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Part 1: Understanding Different QRadar Components and Architecture
2. Chapter 1: QRadar Components FREE CHAPTER 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

What is historical rule correlation?

When you create a rule in QRadar, you would like to test the rule against sample data to understand the number of offenses created, the frequency of the offensees, and the performance impact on the system. The best way to test this is to create a rule and then run a historical correlation to test the rule. The historical correlation rule is run on past data. We can select the range of time for which data was collected to run the rule. For example, a newly created rule can be run on 6-month-old data. Usually, you should run the historical correlation during non-business hours so that the impact, if any, is minimal. Based on the results, you can further tune the rule.

Consider another scenario in which QRadar was down for some time because of, say, a system upgrade activity or any other reason. In such a scenario, we can run a historical correlation and generate the offenses that were lost if there are any.

Historical correlation is also used...

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 €18.99/month. Cancel anytime