Product integration

You can integrate IBM® Guardium® with other products.

Configure BIG-IP Application Security Manager (ASM) to communicate with Guardium system
Use the Big-IP ASM (from F5 Networks) together with Guardium’s real-time database activity monitoring to solve the problem of identity propagation between web application and database application server layers.
Embedded integrations
You can use available integrations with Guardium UNIX and Linux® systems.
PIM Integration with Guardium DAM
Privileged Information Management (PIM) helps organizations to automate and track the use of shared privileged identities and monitor the usage of these shared privileged identities.
Configuring an external ticketing system
Use an external ticketing system such as ServiceNow or IBM Resilient to track incidents, problems, and tasks discovered by Guardium.
Configuring vulnerability scanner agents
Common Vulnerabilities and Exposures (CVE) scanner agents, such as Nessus and Qualys, gather information about the Guardium system and send it to their third-party portal, which analyzes and generates reports. If the agent can run as root directly on the Guardium system, the resulting report is much more accurate with fewer false positive results. Use scanner_agent CLI commands to install and manage root access to CVE scan tools.
Installing and integrating Splunk
Configure Guardium to push data to Splunk. The Guardium collected data is exported to Splunk by sending archived .csv files using the SCP protocol.
QRadar and Guardium integration
QRadar and Guardium can work together in a two-way information flow to have the Guardium data protection policies updated automatically and nearly in real-time in response to security intelligence events from QRadar.
OPTIM to Guardium Interface
An OPTIM to Guardium interface, using Protobuf (Universal Feed Agent), sends Optim activity logs to Guardium.
Combining real-time alerts and correlation analysis with SIEM products
Distribute contextual knowledge of database activity patterns, structures, and protocols directly to the third-party database of the SIEM system.
CEF Mapping
The CEF standard from ArcSight defines a set of required fields, and a set of optional fields.
LEEF Mapping
Log Event Extended Format (LEEF) from QRadar