IBM QRadar Version 7.3 Planning and Installation Guide

Elias Carabaguiaz · Fabian Alfaro · Francisco Villalobos · Jeffry Arias · Kenneth Gonzalez · Warren Perez · IBM Redbooks

Jan 2018 · IBM Redbooks

About this ebook

With the advances of technology and the reoccurrence of data leaks, cyber security is a bigger challenge than ever before. Cyber attacks evolve as quickly as the technology itself, and hackers are finding more innovative ways to break security controls to access confidential data and to interrupt services. Hackers reinvent themselves using new technology features as a tool to expose companies and individuals. Therefore, cyber security cannot be reactive but must go a step further by implementing proactive security controls that protect one of the most important assets of every organization: the company's information.

This IBM® Redbooks® publication provides information about implementing IBM QRadar® for Security Intelligence and Event Monitoring (SIEM) and protecting an organization's networks through a sophisticated technology, which permits a proactive security posture. It is divided in to the following major sections to facilitate the integration of QRadar with any network architecture:
Chapter 2, "Before the installation" on page 3 provides a review of important requirements before the installation of the product.

Chapter 3, "Installing IBM QRadar V7.3" on page 57 provides step-by-step procedures to guide you through the installation process.

Chapter 4, "After the installation" on page 77 helps you to configure additional features and perform checks after the product is installed.

QRadar is an IBM Security prime product that is designed to be integrated with corporate network devices to keep a real-time monitoring of security events through a centralized console. Through this book, any network or security administrator can understand the product's features and benefits.

Ratings and reviews

Qradar security framework has several modules that counterbalance network heat, excessive data packet injection, recognizition that the spike is message protocol or signal status: no data. It's first in rank goal is preemptive interruption long before the gang up his a network backbone For example, tracing and logging an out-of-sync packet sequence doesn't end with logging the date/time I am a civilian, but Qradar would view recording the exception, not the mandated endpoint. Qradar will ,"grep' a network more than the network

Love to read this book