Example scenarios

The following section lists the example scenarios for calculating entitlements.

Note: These examples are not exhaustive in terms of different database deployment architectures.

Example 1: Counting MVS (Managed Virtual Server) by hostname/IP

If you use Guardium Vulnerability Assessment to scan 100 database servers, each with a unique IP address or hostname, you need entitlements that support 100 MVS.

If you use Guardium Vulnerability Assessment to scan more than 100 database servers with unique IP address or hostname, you need an additional entitlements that support 100 MVS.

Example 2: Counting multinode systems

If you have an on-prem database system with 3 nodes for high availability as shown in the following figure, you require 3 MVS of Guardium Vulnerability Assessment.

Example 3: Counting DB systems deployed by different DB vendors

If you have an on-prem server with 3 different DBs deployed, you require 3 MVS of Guardium Vulnerability Assessment regardless of the IP configuration of these database instances.

Example 4: Counting multiple databases across multiple instances (non z/OS)

If you have an on-prem DBMS with 2 instances deployed and each of the DB instance has 3 databases, you need 2 MVS of Guardium Vulnerability Assessment.

Example 5: Counting Db2 running on z/OS

If you use Guardium Vulnerability Assessment to scan 2 Db2 for z/OS subsystems, you need an entitlement that supports 2 MVS.

Note: A subsystem on Db2 z/OS is similar to an instance of Db2 running on Linux, UNIX, and Windows systems. The subsystem provides a separate Db2 environment and configuration. Guardium Vulnerability Assessment has two separate part numbers; one for Linux, UNIX, and Windows (LUW) and another for Db2 for z/OS. So, ensure that you use the correct part number for scanning these systems.

Example 6: Counting databases on cloud DBaaS

If you use Guardium Vulnerability Assessment to scan 3 databases in your AWS Relational Database Service (RDS) environment, each with a unique IP address or hostname, you need 3 MVS of Guardium Vulnerability Assessment regardless of the compute power allocated to each of these databases.

Example 7: Counting databases on Snowflake environment

If you are use Guardium Vulnerability Assessment to scan 3 instances in your Snowflake environment, you need 3 MVS of Guardium Vulnerability Assessment regardless of the instance size.

The exact number of Resource Value Units (RVUs) for all these scenarios can be calculated by using the VUE Table 103A mentioned in License Information.