LoadRunner

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:	LoadRunner is a software testing product used to test applications and measure system behavior and performance under load. LoadRunner simulates user activity by generating messages between application components or by simulating interactions with the user interface such as keypresses or mouse movements. The messages/interactions to be generated are stored in scripts. LoadRunner can generate the scripts by recording them, such as logging Hypertext Transfer Protocol (HTTP) requests between a client web browser and an application`s web server. There is a Community Edition of this software that allows for 50 free licenses, the Virtual edition which supports virtual users and a pricing option for volume users. This entry covers both editions of this software. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO This technology uses Oracle Database and Microsoft Structured Query Language (SQL) Server to store data. This product had been under the umbrella of HP but is now a software product of Micro Focus.
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 Security Officer (ISO), 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 been assessed by the Section 508 Office and found non-conformant. 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. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v22.4
Decision Date:	04/07/2022 at 01:52:23 UTC
Introduced By:	Extended Tool List (ETL)
Vendor Name:	Micro Focus

Vendor Release Information

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

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
7.8	09/01/2003	06/30/2008	06/30/2008
8.0	08/01/2004	06/30/2008	06/30/2008
8.1	10/01/2005	06/30/2008	06/30/2008
9.0	08/01/2007	12/31/2015	12/31/2015
9.1	02/01/2008	12/31/2015	12/31/2015
9.5	09/29/2009	12/31/2015	12/31/2015
10.0	02/01/2010
11.0	09/01/2010
11.5	12/11/2012
11.52	05/09/2013
12	03/18/2014
12.5	08/15/2015
12.53	05/31/2016
12.55	08/17/2017
12.56	02/27/2018
12.6	08/28/2018
2020	12/17/2019
2021
2022

Current Decision Matrix (03/28/2022)

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 Security Officer (ISO), 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 VA IT 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. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved 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	Unapproved: 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	Divest: 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 unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint: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 approved 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 approved 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.

<Past

CY2018

CY2019

CY2020

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

11.52

Unapproved

12

Unapproved

12.5

Approved w/Constraints
[3, 6, 9]

Approved w/Constraints
[3, 9, 10]

Divest
[3, 9, 10]

Divest
[3, 9, 11]

Divest
[3, 12, 13, 14]

Unapproved

12.53

Approved w/Constraints
[3, 6, 9]

Approved w/Constraints
[3, 9, 10]

Divest
[3, 9, 10]

Divest
[3, 9, 11]

Divest
[3, 12, 13, 14]

Unapproved

12.55

Unapproved

Approved w/Constraints
[3, 9, 10]

Divest
[3, 9, 11]

Divest
[3, 12, 13, 14]

Unapproved

12.56

Unapproved

Approved w/Constraints
[3, 9, 10]

Divest
[3, 9, 11]

Divest
[3, 12, 13, 14]

Unapproved

12.6

Unapproved

Approved w/Constraints
[3, 9, 11]

Divest
[3, 12, 13, 14]

2020

Unapproved

Approved w/Constraints
[3, 12, 13, 14]

2021

Unapproved

2022

Unapproved

Decision Constraints


[1]	The use of this technology is limited for deployment to appropriate Veterans Affairs (VA) approved testing laboratory environments. Performance testing must be done with coordination of test lab system administrators to ensure that performance in the test lab does not adversely affect other services in and out of the test lab`s local environment.

[2]	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.

[3]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[4]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. The Initial Product Review notes that: The software must not be used within the VA production network. Only test data should be used with this software to test and develop systems that have not undergone Security Assessment and Authorization (A&A). Applications developed in HPE LoadRunner must follow safe coding practices in order to prevent the introduction of vulnerabilities in the VA Enterprise environment. The required safe coding controls for VA are available in the VA Handbook 6500, Appendix F `System and Information Integrity`. Because of known vulnerabilities in earlier versions, only version 12.50 should be installed and older versions should be updated.

[5]	Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review.

[6]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This product is not intended to run in a production environment and must be used in test environments that are isolated from impacting production operations.

[7]	Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[8]	Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[9]	Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[10]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This technology must not be used in conjunction with File Transfer Protocol. Per the Initial Product Review, users must abide by the following constraints: The software must not be used within the VA production network. Only test data should be used with this software to test and develop systems that have not undergone Security Assessment and Authorization (A&A). Applications developed in HPE LoadRunner must follow safe coding practices in order to prevent the introduction of vulnerabilities in the VA Enterprise environment. The required safe coding controls for VA are available in the VA Handbook 6500, Appendix F `System and Information Integrity`.

[11]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This technology must not be used in conjunction with File Transfer Protocol. Per the Initial Product Review, users must abide by the following constraints: The software must not be used within the VA production network. Only test data should be used with this software to test and develop systems that have not undergone Security Assessment and Authorization (A&A). Applications developed in HPE LoadRunner must follow safe coding practices in order to prevent the introduction of vulnerabilities in the VA Enterprise environment. The required safe coding controls for VA are available in the VA Handbook 6500, Appendix F `System and Information Integrity`.

[12]	Users must ensure that Firefox, Microsoft .NET Framework, Microsoft Internet Explorer (IE), Microsoft Structured Query Language (SQL) Server, Oracle Database and Microsoft Internet Information Services (IIS) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) If free trialware is utilized, the software must be purchased or removed at the end of the trial period. The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services) Per the Initial Product Review, users must abide by the following constraints: The software must only be used in development or testing environments and must not be used within the VA production environments. Only test data should be used with this software to test and develop systems that have not undergone Security Assessment and Authorization (A&A). Applications developed in Micro Focus LoadRunner must follow safe coding practices to prevent the introduction of vulnerabilities in the VA Enterprise environment. The required safe coding controls for VA are available in the VA Handbook 6500, Appendix F – “System and Information Integrity”.

[13]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) 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 compliant encryption 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 compliant full disk encryption (FOE) must be implemented on the hard drive 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 Security Officer (ISO) 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).

[14]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

Note:

At the time of writing, version 2022 is the most current version.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

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
Analysis	This component consists of graphs and reports for analyzing the load test.
Controller	This component controls the execution of scenarios and Vusers. It includes the online monitors which monitor and display information about the text execution.
Load Generator	This component runs Vusers (including Windows-based GUI Vusers) to generate load.
MI Listener	This component is used for the MI Listener machine used in running Vusers and monitoring over the firewall.
Monitors over Firewall	This component works on the agent machine for monitoring over the firewall.
TrueClient	This component is used for recording and developing test scripts for Web-based applications.
Vuser Generator	This component is LoadRunner`s utility for creating virtual user (Vuser) scripts, primarily through recording. Vuser scripts emulate users without a graphical user interface (GUI) by using direction function calls.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Application Testing Software	Load and Performance Testing Tools

Operating Systems Supported by the Technology

Oracle Linux - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

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 is a well-documented technology.
This is a mature technology.
This technology could improve productivity for specific staff whose duties involve load testing.
This technology supports several industry standard file formats.

Adoption Risks

There is a Cybersecurity Operations Center (CSOC)/Threat & Assessment Analysis Portal (TAAP) bulletin associated with this technology.
There are other approved solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.
This technology can integrate with and alter database technologies.
LoadRunner can modify the performance of an application.
LoadRunner requires .NET 3.5, SP1, 4.5.2 – 4.7.2 or 4.8.
LoadRunner requires Oracle JDK or OpenJDK versions 1.7.x, 1.8.x, or 11.x.
LoadRunner is certified to be installed and run under Amazon Web Services (AWS), Microsoft Azure, and the Google Cloud Platform.
Microsoft Internet Explorer, an optional dependency of this technology, is in a divested state at the time of writing.
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 can potentially use File Transfer Protocol (FTP), an unapproved protocol.
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
Unauthorized access to application development tools could potentially increase the risk of vulnerabilities being introduced into the source code undergoing development.

Architectural Benefits

This technology can use a VA-preferred database.
This technology is portable as it runs on multiple TRM-approved operating systems.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/28/2022)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime 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 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/28/2022)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES