IBM Cloud Pak for Security Gen 3 License Guide

This document provides information about licensing and entitlements for IBM Cloud Pak for Security Gen 3.

Note: This License Guide is intended to provide only supplementary information to assist you in deploying the Program(s) you have licensed from IBM® within your purchased entitlement. Your license agreement (such as the IBM International Program License Agreement (IPLA) or equivalent and its transaction documents, including the License Information for IBM Cloud Pak for Security Gen 3, is the sole and complete agreement between you and IBM regarding use of the Program.

Listing of licenses by type

These licenses are used when creating instances of the IBM Cloud Pak for Security Gen 2 components in the spec.license.license field of each custom resource:

Full License
Full Licenses include OpenShift® Container Platform support entitlements. These licenses can be deployed in the Production or Non-production environment. See Products that can be deployed on Red Hat OpenShift for more details on Red Hat® OpenShift Container Platform support entitlements.
Disaster Recovery License
Disaster Recovery Licenses include OpenShift Container Platform support entitlements. These licenses are meant to be deployed for use in Disaster Recovery environments. See Products that can be deployed on Red Hat OpenShift for more details on Red Hat OpenShift Container Platform support entitlements.

The following table shows license versions.

Table 1. License versions
License Usage Description

L-QAXS-3Q3M77

Production or Non-production IBM Cloud Pak for Security Gen 3

L-LUJZ-GNH86D

Disaster recovery IBM Cloud Pak for Security Gen 3 - Disaster Recovery

What do you get with your purchase of IBM Cloud Pak for Security Gen 3 and what is your entitlement?

IBM Cloud Pak for Security Gen 3 helps your organization detect and investigate threats, orchestrate, and automate actions; and respond faster to security incidents across hybrid multi-cloud environments. It includes enterprise ready, containerized and non-containerized software programs/capabilities. The containerized software requires Red Hat OpenShift. Containerized software is supported on Linux® 64-bit (X86_64) only today.

The following containerized and non-containerized software are bundled in with the IBM Cloud Pak for Security Gen 3 Program.

Table 2. Bundled programs and deployent options
Bundled programs Deployment in containerized format Deployment in non-containerized format
QRadar® SOAR QRadar SOAR
IBM® Security SOAR Platform
IBM Security SOAR Breach Response Add-onIBM Security QRadar SOAR Team Management Add-on
IBM Security QRadar SOAR MSSP Add-on
IBM Security QRadar SOAR Actions Enterprise
IBM Security QRadar SOAR App Host
QRadar SOAR Breach Response Add-on QRadar SOAR Breach Response Add-on QRadar SOAR Breach Response Add-on
QRadar SIEM Not available
IBM Security QRadar Suite SoftwareIBM Security QRadar Data StoreIBM Security QRadar Capacity - EventsIBM Security QRadar Suite Software NodeIBM Security QRadar Data Synchronization
IBM Security QRadar High Availability Software
QRadar NDR Not available IBM Security QRadar Network Insights SoftwareIBM Security QRadar Capacity - FlowsIBM Security QRadar Software NodeIBM Security QRadar Data SynchronizationIBM Security QRadar High Availability Software
QRadar Data Store Not available
IBM Security QRadar Data StoreIBM Security QRadar Software NodeIBM Security QRadar Data SynchronizationIBM Security QRadar High Availability Software
Risk Manager Risk Manager Not available
Data Explorer Data Explorer Not available
Threat Intelligence Insights Threat Intelligence Insights Not available
Threat Investigator Threat Investigator Not available
Guardium® Data Protection Not available
IBM Security Guardium Aggregator Software Appliance
IBM Security Guardium Collector Software Appliance
IBM Security Guardium Data Protection for Big Data
IBM Security Guardium Data Protection for Databases
IBM Security Guardium Data Protection for Database Services
IBM Security Guardium Data Protection for Data Warehouses
IBM Security Guardium Data Protection for Files
IBM Security Guardium Data Protection for z/OS
IBM Security Guardium Data Protection for SAP HANA
Guardium Vulnerability Assessment Not available IBM Security Guardium Vulnerability Assessment for Databases
Guardium Insights IBM Security Guardium Insights for IBM Cloud Pak for Security Not available

When deploying any of the bundled offerings under the IBM Cloud Pak for Security Gen 3, licensee must not exceed the maximum entitlement at any time. Deployments can include a mix of different deployed products, either deployment in containerized format, or deployment in non-containerized format, or a combination of both. Licensee can change the deployed offerings at any time as long as they never exceed their maximum entitlement. See Products that can be deployed on Red Hat OpenShift to learn more about which deployments require the Red Hat OpenShift Container Platform.

Note: All deployments of IBM Cloud Pak for Security Gen 3 that are deployed onRed Hat OpenShift Container Platform must have sufficient entitlement for the Red Hat OpenShift Container Platform cores that are used.

License options and pricing models for IBM Cloud Pak for Security Gen 3

Licensee can purchase Resource Units and apply them to the products and pricing model of choice. Licensee has the option to pick from the following two pricing models.

When licensing any of the following products: QRadar SIEM, NDR, SOAR, Breach Response , Data Explorer, Threat Investigator and Threat Intelligence Insights, the following pricing models apply.

Enterprise model
This model offers predictable pricing at enterprise scale, and is based on the size of the IT infrastructure. The pricing metric is Managed Virtual Servers (MVS). All Physical and Virtual Server are counted in the customer environment. This model offers unlimited users, actions, and data ingestion.
Usage model
This model is usage-based, and is ideal for starting small and scaling as you grow. Pricing metrics vary based on the product. See usage pricing metric under each product section.

License cannot mix or match pricing models across the same product in the package. Licensee cannot mix license entitlements for IBM Cloud Pak for Security Gen 3 program and the stand-alone products. For example, IBM Security QRadar SIEM from the Gen 3 package and IIBM Security QRadar Capacity stand-alone license entitlement.

License must license a minimum of 100 MVS to use the Enterprise license. For example: If a Licensee has 80 servers in their organization, they should use the Usage model.

When licensing any of the following products: Guardium Data Protection, GVA and GI the following pricing models apply.

Licensee can purchase Resource Units and apply them to the programs and pricing model of their choice. Licensee has the option to pick from the following two models and can mix the two models across the same program in Guardium Package (except for SOAR, SOAR Breach Response, and Risk Manager programs).

Enterprise model
The pricing metric is Managed Virtual Servers (MVS). Here the number of the servers in the enterprise that the Guardium programs (Guardium Data Protection, Guardium Vulnerability Assessment, and Guardium Insights) protect are counted. MVS metric is used to support data sources, which are on-premises, including cloud hosted IaaS deployments, yet is not limited to those data sources.
Usage model
The unit of measure is primarily Virtual Processor Core (VPC). Here the number of processor cores that are allocated to the data sources (for example, DBaaS) that Guardium programs (Guardium Data Protection, Guardium Vulnerability Assessment, and Guardium Insights) protect are counted. For cloud-based (Cloud DBaaS) and containerized data sources, VPC (compute assigned) metric is typically more relevant and is easier to find and report yet does not need to be used for these data sources.

See License ratios for information on MVS and VPC license metrics.

License ratios

Deployed instances of products in IBM Cloud Pak for Security Gen 3 are charged at different rates based on their ratios.

Entitlements of IBM Cloud Pak for Security Gen 3 that are deployed can be redeployed to other products, as long as the total entitlement is not exceeded, using the ratios to calculate your total entitlements. There is no limit to the number of times that entitlements can be used in different combinations.

The following table shows the license ratios.

Table 3. License ratios
Product RU ratio (Enterprise model) RU ratio (Usage model)
Data Explorer 1 MVS:1 RU 1 AU: 250 RU
Threat Intelligence Insights 1 MVS: 1 RU 1 AU: 250 RU
Threat Investigator 1 MVS: 1 RU 1 AU: 250 RU
QRadar SOAR 1 MVS: 5 RU 1 AU: 1000 RU
QRadar Breach Response 1 MVS: 1 RU 1 AU: 150 RU
QRadar SIEM 1 MVS: 12 RU 100 EPS: 120 RU
QRadar NDR 1 MVS: 7 RU 10k FPM: 300 RU
QRadar Data Store 1 MVS: 2 RU 1 AU: 500 RU
Guardium Data Protection 1 MVS: 360 RU 1 VPC: 36 RU
Guardium Vulnerability Assessment 1 MVS: 40 RU 1 VPC: 4 RU
Guardium Insights 1 MVS: 100 RU 1 VPC: 10 RU
Risk Manager 1 MVS: 2 RU 1 MVS: 2 RU

Products that can be deployed on Red Hat OpenShift

The following Bundled programs require the deployment of Red Hat OpenShift Container Platform.

  • QRadar SOAR
  • QRadar SOAR Breach Response -Add On
  • QRadar EDR
  • QRadar EDR Enterprise
  • Risk Manager
  • Guardium Insights
  • Data Explorer
  • Threat Intelligence Insights
  • Threat Investigator
Note: QRadar SOAR and QRadar SOAR Breach Response have the option of being deployed as a virtual image (non-containerized) as well.

The following capabilities are now included with QRadar SOAR, QRadar SIEM, and QRadar NDR entitlements. There are no additional license entitlements that are required to use these capabilities.

  • Data Explorer
  • Threat Investigator
  • Threat Intelligence Insights

Red Hat OpenShift Container Platform entitlements

For the purpose of this section “entitlement” to the Red Hat OpenShift Container Platform means the software subscription and support for the Red Hat OpenShift Container Platform. “Restricted license entitlement” means that software subscription and support for the Red Hat OpenShift Container Platform acquired pursuant to your IBM Cloud Pak for Security Gen 3 license is only provided for use of the Red Hat OpenShift Container Platform specifically for IBM Cloud Pak for Security Gen 3 and not non-IBM Cloud Pak for Security Gen 3 workloads.

When deploying programs under the containerized deployment, as part of an IBM Cloud Pak for Security Gen 3 deployment, deployment of Red Hat OpenShift is required. Restricted license entitlement for the Red Hat OpenShift is provided as follows:

  • 50 VPCs of Red Hat OpenShift Container Platform if Licensee obtains 0-25,000 RU entitlement(s) of the Program
  • 100 VPCs of Red Hat OpenShift Container Platform if Licensee obtains 25,001-100,000 RU entitlement(s) of the Program
  • 200 VPCs of Red Hat OpenShift Container Platform if Licensee obtains 100,001 or more RU entitlement(s) of the Program

The above licenses can be used only for deployments of IBM Cloud Pak for Security Gen 3 instances, not for other third-party deployments or custom code. If you deploy other code or components (such as agents used for monitoring IBM Cloud Pak for Security Gen 3 capabilities), you must purchase separate Red Hat OpenShift entitlements to make available to the cluster, or the deployment of the non-IBM Cloud Pak for Security Gen 3 workload on those Red Hat OpenShift licenses will result in those Red Hat OpenShift cores, and potentially the workload itself, being unsupported. These additional Red Hat OpenShift entitlements for running non-IBM Cloud Pak for Security Gen 3 workload must be procured separately from the Red Hat OpenShift entitlements granted through IBM Cloud Pak for Security Gen 3. The workload that you run on separately purchased Red Hat OpenShift entitlement doesn’t need to be deployed separately from IBM Cloud Pak for Security Gen 3 workload running on IBM Cloud Pak for Security Gen 3-procured Red Hat OpenShift cores. But the number of separately purchased Red Hat OpenShift cores must be equal to or greater than the number of cores of non-IBM Cloud Pak for Security Gen 3 workloads deployed on them in order to receive support for the complete deployment of non-IBM Cloud Pak for Security Gen 3 workloads.

An example of IBM Cloud Pak for Security Gen 3 workload might be agents for monitoring. These agents, which run alongside the IBM Cloud Pak for Security Gen 3 components and then send the monitoring data out to a separate monitoring server component, can be run in the same nodes or namespaces as components running in Red Hat OpenShift cores using entitlements under IBM Cloud Pak for Security Gen 3. For all non-IBM Cloud Pak for Security Gen 3 workloads, not just monitoring agents, you are recommended to ensure you have separately-procured software subscription and support entitlements

The number of cores of Red Hat OpenShift entitled with IBM Cloud Pak for Security Gen 3 varies by the number of Resource Units purchased & doesn’t vary by the ratio of the bundled offerings, which are deployed under IBM Cloud Pak for Security Gen 3 entitlement. Therefore, the number of cores that are required for deployment of bundled offerings IBM Cloud Pak for Security Gen 3 can, in some scenarios, exceed the number of Red Hat OpenShift cores available as part of the entitlement for IBM Cloud Pak for Security Gen 3. In such cases, the customer should acquire additional entitlement for Red Hat OpenShift to ensure that they are always correctly licensed. Only Red Hat OpenShift cores that are deployed as worker nodes count against the Red Hat OpenShift entitlement.

Note: Organizations deploying IBM Cloud Pak for Security Gen 3 on managed Red Hat OpenShift environments in public clouds such as AWS ROSA, IBM ROKS or Azure ARO may get discounts on the cost of Red Hat OpenShift on worker nodes where IBM Cloud Pak for Security Gen 3 is deployed based on the Red Hat OpenShift entitlements that are included in IBM Cloud Pak for Security Gen 3 entitlements. Customers should verify with their public cloud service provider to establish if a discount is available.

IBM Storage Fusion additional flat entitlement

Limited entitlements of IBM Storage Fusion are included with IBM Cloud Pak for Security Gen 3. Max usable capacity of 12 Terabytes (TB) per Red Hat OpenShift cluster is included. Use of IBM Storage Fusion as part of IBM Cloud Pak for Security Gen 3 entitlement is limited to Fusion Data Foundation in internal deployment mode only, and when in internal deployment mode, also excludes disaster recovery, backup components, data cataloguing, and advanced encryption with KMS.

IBM Security QRadar SOAR

Licensee has the choice of installing QRadar SOAR using one of the following options:

  • Install the containerized QRadar SOAR application on Red Hat OpenShift
  • Install stand-alone QRadar SOAR on a virtual appliance.
  • Install stand-alone QRadar SOAR on RHEL - Bring Your Own License (BYOL).
Important: Red Hat OpenShift is not a prerequisite for the installation of the stand-alone installation option of QRadar SOAR. However, it is a prerequisite for the SOAR deployment on the IBM Security Platform.

The following capabilities - Data Explorer, Threat Investigator, and Threat Intelligence Insights are included as part of the QRadar SOAR Entitlement. If the licensee plans to install any of these capabilities, the licensee will need to deploy the Red Hat OpenShift Container Platform.

A license key is required to access QRadar SOAR capabilities. Once the QRadar SOAR installation is complete, the licensee must install the SOAR license Key. For more information, see Installing the Orchestration & Automation license.

To acquire a license key for QRadar SOAR or SOAR Breach Response entitlements, send an email to q1pd@us.ibm.com and include the following information in your request:

  • IBM Customer Number (IBM Content Navigator)
  • Site ID or your Proof of Entitlement (POE)

To acquire a License key for our Enterprise Licensing Agreement (ELA) Customers, contact your IBM Sales Representative.

Licensee must have entitlement for QRadar SOAR to use the QRadar SOAR Breach Response add-on. Licensee must license a matching set of entitlements for QRadar SOAR and QRadar SOAR Breach Response.

QRadar SOAR and QRadar SOAR Breach Response are licensed on either Enterprise Pricing Model or Usage Model. For more information, see License options and pricing models for QRadar Suite Software. Pricing Metric for Enterprise Model is Managed Virtual Server and the Pricing Metric for the Usage model is Authorized User. Licensee is required to license a minimum quantity of two (2) the Authorized Users when licensing by the Usage Model.

QRadar SOAR and QRadar SOAR Breach Response can only be licensed on MVS metric if Licensee is licensing the QRadar SIEM under the same metric.

IBM Security QRadar SIEM and QRadar NDR

QRadar SIEM or QRadar NDR is available as a virtual appliance only. This is available as a virtual appliance and hence does not require deployment of the Red Hat OpenShift Container Platform.

Note: This is what we refer to as SIEM (Classic).

A license key is required to access IBM QRadar SIEM or QRadar NDR capabilities.

To acquire a license key, contact q1pd@us.ibm.com and include the following information in your request:

  • IBM Customer Number (ICN).
  • Site ID or your Proof of Entitlement (POE).
  • For QRadar SIEM, include the quantity of Multiple Virtual Storage (MVS™) or Events per Second (EPS) purchased.
  • For QRadar NDR, include the quantity of MVS or flows per minute (FPM) purchased.

QRadar SIEM and QRadar NDR are licensed on either Enterprise Pricing Model or Usage Model. For more details, see License options and pricing models for QRadar Suite Software. Pricing Metric for Enterprise Model is Managed Virtual Server (MVS) and the Pricing Metric for the Usage model is Events per Second (EPS) for SIEM and Flow Per Minute (FPM) for NDR.

Note: Licensee must obtain MVS entitlements for each physical or virtual server, managed directly or indirectly by QRadar SIEM. Every IP address from a log source that is ingested directly or indirectly by QRadar SIEM, excluding Network Infrastructure & Client Devices (see below), is counted as a physical or a virtual server. If licensee is unable to determine the count of all servers, then we recommend them to use the EPS/FPM metric.

Physical and Virtual Servers exclude Network Infrastructure and Client Devices, even if the IP address appears in QRadar SIEM as a log source.

Here is what is included in those categories:
Network Infrastructure
Switches, Routers, Audio-Visual (AV), File Integrity Monitoring (FIM), Proxies, Intrusion Prevention Systems (IPS), File Activity Monitoring (FAM), Data Loss Prevention (DLP), load balancers, firewalls.
Client Devices
A Client Device is a single user computing device or special purpose sensor or telemetry device that requests the execution of or receives for execution a set of commands, procedures, or applications from or provides data to another computer system that is typically referred to as a server or is otherwise managed by the server. Multiple Client Devices may share access to a common server. A Client Device may have some processing capability or be programmable to allow a user to do work. Examples include, but are not limited to actuators, appliances, automated teller machines, automatic meter readers, cash registers, disk drives, desktop computers, kiosks, notebook computers, personal digital assistant, point-of-sale terminals, sensors, smart meters, tape drives, and technical workstations.
The following image is an example of what is counted as an MVS.
Figure 1. What is counted as an MVS?
image that shows what is counted as an MVS for licensing

The following capabilities - Data Explorer, Threat Investigator, and Threat Intelligence Insights are included as part of the QRadar SIEM or QRadar NDR entitlement. If the licensee plans to install any of these capabilities, the licensee will need to deploy Red Hat OpenShift Container Platform.

IBM Security Risk Manager

IBM Security Risk Manager is only available on the IBM Security Platform and hence requires deployment of the Red Hat OpenShift Container Platform.

Risk Manager is licensed on either Enterprise Pricing Model or Usage Model. Pricing Metric for Enterprise and Usage Model is Managed Virtual. In case of the Enterprise Model licensee need to count all physical and virtual servers in the Enterprise, and in case of Usage they count only the managed physical and virtual servers in the Enterprise.

IBM Security Data Explorer

IBM Security Data Explorer is only available on the IBM Security Platform and hence requires deployment of the Red Hat OpenShift Container Platform.

Data Explorer is licensed on either Enterprise Pricing Model or Usage Model. Pricing Metric for Enterprise Model is Managed Virtual Server and for Usage Model is Authorized User.

Data Explorer is now included with QRadar SOAR, QRadar SIEM and QRadar NDR and if deployed with any of these programs, it will not consume any entitlements.

IBM Security Threat Intelligence Insights

IBM Security Threat Intelligence Insights is only available on the IBM Security Platform and hence requires deployment of the Red Hat OpenShift Container Platform.

Threat Intelligence Insights is licensed on either Enterprise Pricing Model or Usage Model. Pricing Metric for Enterprise Model is Managed Virtual Server and for Usage Model is Authorized User.

Threat Intelligence Insights is now included with QRadar SOAR, QRadar SIEM and QRadar NDR and if deployed with any of these programs, it will not consume any entitlements.

IBM Security Threat Investigator

IBM Security Threat Investigator is only available on the IBM Security Platform and hence requires deployment of the Red Hat OpenShift Container Platform.

Threat Investigator is licensed on either Enterprise Pricing Model or Usage Model. Pricing Metric for Enterprise Model is Managed Virtual Server and for Usage Model is Authorized User.

Threat Investigator is now included with QRadar SOAR, QRadar SIEM and QRadar NDR and if deployed with any of these programs, it will not consume any entitlements.

IBM Security Guardium Data Protection

Guardium Data Protection is available as a virtual appliance only. It is not available on the IBM Security Platform and hence does not require deployment of the Red Hat OpenShift Container Platform.

A license key is required to access Guardium Data Protection capabilities and is provided in the software download. For more information, see https://www.ibm.com/docs/en/guardium/12.0?topic=system-license-keys.

Licensees who wish to allocate RUs to the Guardium Data Protection capabilities can use any of the following bundled programs:
  • IBM Security Guardium Aggregator Software Appliance
  • IBM Security Guardium Collector Software Appliance
  • IBM Security Guardium Data Protection for Big Data
  • IBM Security Guardium Data Protection for Databases
  • IBM Security Guardium Data Protection for Database Services
  • IBM Security Guardium Data Protection for Data Warehouses
  • IBM Security Guardium Data Protection for Files
  • IBM Security Guardium Data Protection for z/OS®
  • IBM Security Guardium Data Protection for SAP HANA

The Licensee must obtain the sufficient quantity of Enterprise Model and/or Usage Model needed to protect their data.

Nonproduction activities for IBM Security Guardium Data Protection are defined as anything other than actively monitoring or protecting data. For clarity, monitoring or protecting data in a nonproduction environment is considered productive use, and therefore requires sufficient entitlements.

For details on how to report on Guardium Data Protection license usage see the Guardium Data Protection Usage Reporting Guide.

For example, applied to Guardium Data Protection, consider the following scenarios:

Scenario 1: An organization chooses to use only the enterprise model, with a predictable scaling approach at enterprise scale, based on IT infrastructure.
Data sources Metric Ratio # of RU
100 on-premises database servers 100 MVS 1 MVS: 360 RU 36,000 RU
12 Azure data sets totaling 96 vCPUs 12 MVS 1 MVS: 360 RU 4,320 RU
400 VPC of Data Warehouse & Big Data 400 VPC 1 VPC: 36 RU 14,400 RU
Total RUs 54,720 RU
Result: 548 license entitlements needed (packs of 100 RUs)
Scenario 2: An organization uses a combination of the enterprise and usage models. This hybrid approach can offer flexibility and simplify what is counted in the customer environment. In this example, an organization chooses to use the usage model to apply entitlements for a subset of their DbaaS data sets and potentially expand later.
Data sources Metric Ratio # of RU
80 on-premises database servers 80 MVS 1 MVS: 360 RU 28,800 RU
48 vCPUs for a subset of their Azure data sets 48 VPC 1 VPC: 36 RU 1,728 RU
400 VPC of Data Warehouse & Big Data 400 VPC 1 VPC: 36 RU 14,400 RU
Total RUs 44,928 RU
450 license entitlements needed (packs of 100 RUs)

IBM Security Guardium Vulnerability Assessment

Guardium Vulnerability Assessment is available as a virtual appliance only. It is not available on the IBM Security Platform and hence does not require deployment of the Red Hat OpenShift Container Platform.

An Append license key is required to access Guardium Vulnerability Assessment capabilities and is provided in the software download. For more information, see https://www.ibm.com/docs/en/guardium/12.0?topic=system-license-keys.

Licensee must obtain sufficient quantity of Enterprise Model and/or Usage Model needed to protect their data.

Nonproduction activities for Guardium Vulnerability Assessment are defined as anything other than running scans to harden the environment. For clarity, scanning data in a nonproduction environment is considered productive use, and therefore requires sufficient entitlements.

For details on how to report on Guardium Vulnerability Assessment license usage see the Guardium Data Protection Usage Reporting Guide.

For example, applied to Guardium Vulnerability Assessment, consider the following scenarios:

Scenario 1: An organization opts to use only the enterprise model based on IT infrastructure.
Data sources Metric Ratio # of RU
100 on-premises database servers 100 MVS 1 MVS: 40 RU 4,000 RU
15 Cloud DbaaS instances/nodes 15 MVS 1 MVS: 40 RU 600 RU
Total RUs 4,600 RU
= 46 license entitlements needed (packs of 100 RUs)
Scenario 2: An organization opts to use a combination of enterprise and usage models, counting applicable data sources.
Data sources Metric Ratio # of RU
100 on-premises database servers 100 MVS 1 MVS: 40 RU 4,000 RU
5 Cloud DbaaS instances/nodes across 60 vCPUs 20 VPC 1 VPC: 4 RU 80 RU
Total RUs 4,080 RU
= 41 license entitlements needed (packs of 100 RUs)

IBM Security Guardium Insights

Guardium Insights is a containerized program and hence requires deployment of the Red Hat OpenShift Container Platform.

Guardium Insights does not use license keys.

Licensee must obtain sufficient Resource Unit (RU) allocation that is needed to protect the data sources in their deployed environments. Guardium Insights for Cloud Pak for Security is the bundled program in Guardium Package.

Guardium Insights software today does not offer software functionality to track the number of data sources protected. An organization needs to count the number of data sources to ensure sufficient entitlements, applying the definitions of the MVS and/or VPC unit of measures and then mapping to Resource Units (see License ratios).

Typically, the MVS unit of measure is applied to data sources, which are on-premises, including cloud hosted IaaS deployments. First, determine the data sources to be protected by Guardium Insights. Then, calculate the associated number of data base physical / virtual servers that are associated with those data sources. For the cloud-based data sources (cloud DBaaS) and containerized data sources, the VPC unit of measure is typically more relevant and straightforward to determine, based on the quantity of processor cores used for the relevant data sources.

For example, consider the following scenario for Guardium Insights. An organization chooses to use a combination of the enterprise model (for on-premises database servers in their deployed environment) and the usage model (for DbaaS data servers that they opt to include).

Data sources Metric Ratio # of RU
100 on-premises database servers 100 MVS 1 MVS: 100 RU 10,000 RU
15 Cloud DbaaS data sets across 50 vCPUs 50 VPC 1 VPC: 10 RU 500 RU
Total RUs 10,500 RU
= 105 license entitlements needed (packs of 100 RUs)

Nonproduction activities for Guardium Insights are defined as anything other than actively monitoring or protecting data. For clarity, monitoring or protecting data in a nonproduction environment is considered productive use, and therefore requires sufficient entitlements.

Non-Guardium Package customers may have existing Guardium Insights entitlements through other license part numbers. For reference purposes only, see the table below for the license metric that is associated with those license entitlements:
Description License Metric License
Guardium Insights for Cloud Pak for Security Resource Value Unit / VPC (Virtual Processor Core) Program # = 5737-L66 License
Guardium Insights for Guardium Data Protection for Z/OS Resource Value Unit / MSU (Million Service Units)
IBM Security Guardium Insights Resource Value Unit / MAPC (Managed Activated Processor Core)
Note: Guardium Insights entitlements from other Licenses cannot be applied to Guardium Package License entitlements.