Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 26.1

Velocity Performance Suite (zVPS)

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Velocity Performance Suite (zVPS) is a performance package for Virtual Machine (z/VM), Linux, Transmission Control Protocol and the Internet Protocol (TCP/IP), and Virtual Storage Extended (z/VSE). zVPS collects and analyzes data from z/VM, your Linux servers, network, z/VSE and operating systems (z/OS).
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v25.7
Decision Date:	07/30/2025 at 03:05:40 UTC
Aliases:	zVPS
Introduced By:	TRM Request
Vendor Name:	Velocity Software
Cage Code:	N/A

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
5.x	03/15/2020

Current Decision Matrix (07/29/2025)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VAIT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized w/ Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unauthorized, Conditions Required^[a] : This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Unauthorized, Conditions Required^[b] : VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Unauthorized, Conditions Required^[c] : The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Any major.minor version that is not listed in the VA Decision Matrix is considered Unauthorized, Conditions Required ^[a] .

<Past

CY2025

CY2026

CY2027

Future>

Release

5.x

Authorized w/ Constraints
[1, 3, 6, 7]

Authorized w/ Constraints
[3, 6, 7, 8, 9]

Note:

At the time of writing, version 5.1.4 is the most current version, released 01/01/2024.

Decision Constraints


[1]	Per the Initial Product Review, users must abide by the following constraints: System administrators must ensure that the underlying infrastructure (Web Server, Operating System (OS), etc.) utilizes a third-party FIPS 140-2 cryptographic module for systems that use zVPS. zVPS must be used with an authorized version of IBM z/VM. The product however does not currently support the authorized version of z/VM, which is 7.1. Velocity Software plans to release zVPS version 5 on March 15, 2020, which will provide support for z/VM 7.1. Authorization and Role-based Access Control (RBAC) must be enforced to ensure only authorized staff have access to zVPS. There must be a delineation of duties of Information Technology (IT) staff supporting and utilizing zVPS and their activities must be monitored and audited regularly.

[3]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[6]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[7]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

[8]	Users must not utilize Secure Sockets Layer (SSL), as it, at the time of writing, requires a POA&M. Per the Initial Product Review, users must abide by the following constraints: zVPS is not Federal Information Processing Standards (FIPS) 140-2 certified. Per vendor: “zVPS leverages SSL, and the latest encryption provided by z/VM, including TLS”.System administrators must ensure that the underlying infrastructure (Web Server, Operating System (OS), etc.) utilizes a third-party FIPS 140-2 cryptographic module for systems that use zVPS. There is potential for unauthorized access to the logs, reports, and other data collected which could contain sensitive information about the VA infrastructure. Authorization and Role-based Access Control (RBAC) must be enforced to ensure only authorized staff have access to zVPS. There must be a delineation of duties of Information Technology (IT) staff supporting and utilizing zVPS and their activities must be monitored and audited regularly.

[9]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.

Name	Description
Monitor analysis and reporting program (zMAP)	zMAP creates reports and performs detailed analysis for zVPS.
Real-time Monitor (zMON)	zMON displays real-time network, Linux, and VM performance.
Transmission Control Protocol (zTCP)	zTCP collects network and Linux performance data.
VM Web Server (zVWS)	zVWS provides Web-based graphical user interface for zVPS.
zALERT	zALERT is alert functions for the zVPS.
zOPERATOR	zOPERATOR is a full operator console for zVPS.
zPORTAL	zPORTAL is a package that can be used to manage certain functions within the zVPS.
zVIEW	zVIEW is a browser-based performance data viewer for zVPS.


Systems Management Systems Management Tools	System Change and Configuration Management

General Analysis

Adoption Benefits

There are minimal other TRM-authorized technologies that provide the same functionality.
At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.
This technology may improve productivity for specific staff whose responsibilities include provisioning servers.

Adoption Risks

The latest version of zVPS is built to support z/VM 6.4. Per the Department of Veterans Affairs (VA) Technical Reference Model, z/VM 6.4 is unapproved for use within the VA.
IPR/SAR Adoption Risk - zVPS is not Federal Information Processing Standards (FIPS) 140-2 certified. Per vendor: “zVPS leverages SSL, and the latest encryption provided by z/VM, including TLS”.
IPR/SAR Adoption Risk - There is potential for unauthorized access to the logs, reports, and other data collected which could contain sensitive information about the VA infrastructure.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
This technology is poorly documented and without clearly defined support options which may result in suboptimal enterprise level support.
The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
This technology can integrate with and alter database technologies.
This technology can potentially use Secure Sockets Layer (SSL) which requires a POA&M for use on the VA network.

Architectural Benefits

This technology is portable as it runs on multiple TRM-authorized operating systems.
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012). (Add Virtualization and Consolidation of Servers (Server Virtualize First) to Supported Standards)

Architectural Risks

This technology does not use a VA-preferred database to store data.

- The information contained on this page is accurate as of the Decision Date (07/30/2025 at 03:05:40 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 26.1

General Information

Vendor Release Information

Current Decision Matrix (07/29/2025)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 26.1

General Information

Vendor Release Information

Current Decision Matrix (07/29/2025)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework