ChromeDriver

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:	ChromeDriver is an open source technology for automating testing of webapps across many browsers. It also allows users to implement Selenium WebDriver`s wire protocol for Google Chrome. Additionally, it allows users to create web application scripting for dynamic applications and flows, meaning code can be written for applications that require authentication to get to the next screen as part of the application`s navigational flow. This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx
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 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 v23.10
Decision Date:	10/20/2023 at 00:18:11 UTC
Introduced By:	TRM Request
Vendor Name:	Deque Systems

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
2.x	08/06/2013
77.x	08/20/2019
91.x	04/22/2021
92.x	06/11/2021
103.x	07/20/2022
105.x	08/31/2022
108.x	02/11/2022
109.x	12/02/2022
110.x	01/13/2023
111.x	03/08/2023
112.x	03/16/2023
113.x	05/03/2023
114.x
115.x

Current Decision Matrix (10/17/2023)

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

CY2023

CY2024

CY2025

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

2.x

Unapproved

77.x

Unapproved

91.x

Unapproved

92.x

Divest
[5, 6, 7]

Divest
[6, 7, 8, 9, 10, 11]

Unapproved

103.x

Approved w/Constraints
[5, 6, 7]

Divest
[6, 7, 8, 9, 10, 11]

Unapproved

105.x

Approved w/Constraints
[5, 6, 7]

Divest
[6, 7, 8, 9, 10, 11]

Unapproved

108.x

Unapproved

Divest
[6, 7, 8, 9, 10, 11]

Divest
[6, 7, 9, 10, 11, 12]

Unapproved

109.x

Unapproved

Approved w/Constraints
[6, 7, 8, 9, 10, 11]

Divest
[6, 7, 9, 10, 11, 12]

Unapproved

110.x

Unapproved

Approved w/Constraints
[6, 7, 8, 9, 10, 11]

Divest
[6, 7, 9, 10, 11, 12]

Unapproved

111.x

Unapproved

112.x

Unapproved

Approved w/Constraints
[6, 7, 8, 9, 10, 11]

Divest
[6, 7, 9, 10, 11, 12]

Unapproved

113.x

Unapproved

114.x

Unapproved

Approved w/Constraints
[6, 7, 9, 10, 11, 12]

115.x

Unapproved

Approved w/Constraints
[6, 7, 9, 10, 11, 12]

Decision Constraints


[1]	ChromeDriver must not be used for any data containing Protected Health Information/Personally Identifiable Information sensitive information. The administrator or installer must ensure that ChromeDriver is obtained from Chromium`s website with a verifiable web certificate. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Users must check with their supervisor, Information System Security Office (ISSO) or local Office of Information & Technology (OI&T) representative for permission to download and use this software. It is important to continually monitor systems running ChromeDriver and the chromium.org website. Users must use WebDriver`s remote ends to create a new profile when creating a new session to prevent data from being accessible to further new sessions. Users must ensure that only connections from loopback devices are allowed by default. Users must ensure that WebDriver is always disabled when not in use.

[2]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[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]	Per the Initial Product Review (IPR): ChromeDriver must not be used for any data containing Protected Health Information/Personally Identifiable Information sensitive information. The administrator or installer must ensure that ChromeDriver is obtained from Chromium`s website with a verifiable web certificate. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Users must check with their supervisor, Information System Security Office (ISSO) or local Office of Information & Technology (OI&T) representative for permission to download and use this software. It is important to continually monitor systems running ChromeDriver and the chromium.org website. Users must use WebDriver`s remote ends to create a new profile when creating a new session to prevent data from being accessible to further new sessions. Users must ensure that only connections from loopback devices are allowed by default. Users must ensure that WebDriver is always disabled when not in use.

[5]	Users must ensure that Google Chrome is implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Initial Product Review, users must abide by the following constraints: ChromeDriver will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information. Ensure the latest version is used and the product must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches; or set to auto update in order to mitigate vulnerability vectors from outdated software. Due to the frequency of this technology`s updates, the VA may be unable to keep up with the rapid release schedule of this technology and may require a usage model that requires specific versions. The administrator or installer should ensure that ChromeDriver is obtained from Chromium’s website with verifiable web certificate. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Users should check with their supervisor, Information System Security Office (ISSO) or local OI&T representative for permission to download and use this software. It is important to continually monitor systems running ChromeDriver and the chromium.org website. Users must use WebDriver’s remote ends to create a new profile when creating a new session to prevent data from being accessible to further new sessions. Ensure that only connections from loopback devices are allowed by default. Ensure that WebDriver is always disabled when not in use.

[6]	Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[7]	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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

[8]	Users must ensure that Google Chrome is implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Initial Product Review, users must abide by the following constraints: ChromeDriver will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information where applicable. Due to the frequency of this technology`s updates, the VA may be unable to keep up with the rapid release schedule of this technology and may require a usage model that requires specific versions. The administrator or installer should ensure that ChromeDriver is obtained from Chromium’s website with verifiable web certificate. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Users should check with their supervisor, Information System Security Office (ISSO) or local OI&T representative for permission to download and use this software. It is important to continually monitor systems running ChromeDriver and the chromium.org website. Users must use WebDriver’s remote ends to create a new profile when creating a new session to prevent data from being accessible to further new sessions. Ensure that only connections from loopback devices are allowed by default. Ensure that WebDriver is always disabled when not in use.

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

[10]	New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements.

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

[12]	Users must ensure that Google Chrome is implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Initial Product Review, users must abide by the following constraints: ChromeDriver will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information where applicable. Due to the frequency of this technology`s updates, the VA may be unable to keep up with the rapid release schedule of this technology and may require a usage model that requires specific versions. The administrator or installer should ensure that ChromeDriver is obtained from Chromium’s website with verifiable web certificate. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Users should check with their supervisor, Information System Security Office (ISSO) or local OI&T representative for permission to download and use this software. It is important to continually monitor systems running ChromeDriver and the chromium.org website. Users must use WebDriver’s remote ends to create a new profile when creating a new session to prevent data from being accessible to further new sessions. Ensure that only connections from loopback devices are allowed by default. Ensure that WebDriver is always disabled when not in use..

Note:

At the time of writing, version 115.x is the latest version. If you are using Chrome version 114, please download ChromeDriver 114.0.5735.90

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description

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
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Development Tools	Application Development Tools

Open Source

This entry is available as an open source technology.

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Windows Client - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Selenium

Comparable Technologies:

No comparable entries have been identified.

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology is available at no cost through open-source licensing and supports VA`s open source initiative.
This is a well-documented technology.
This technology may improve productivity for specific staff whose responsibilities include web application development.
There is no licensing fee associated with this technology.
This technology has a secure configuration baseline.

Adoption Risks

The administrator or installer should ensure that ChromeDriver is obtained from Chromium’s website with verifiable web certificate. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Users should check with their supervisor, Information System Security Office (ISSO) or local OI&T representative for permission to download and use this software. It is important to continually monitor systems running ChromeDriver and the chromium.org website.
Users must use WebDriver’s remote ends to create a new profile when creating a new session to prevent data from being accessible to further new sessions.
Ensure that only connections from loopback devices are allowed by default.
Ensure that WebDriver is always disabled when not in use.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
Due to the frequency of this technology`s updates, the VA may be unable to keep up with the rapid release schedule of this technology and may require a usage model that requires specific versions.
ChromeDriver will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information where applicable.
ChromeDriver is an open source product which is downloadable from the internet.
As an open source product, ChromeDriver is only supported by a user group and does not have regular vendor support.
Sensitive session data from previous sessions may bleed through to the next session.
If WebDriver is continuously enabled, then it may be accessed by unprivileged users.
This technology may transmit data over the VA Wide Area Network (WAN).
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.

Architectural Benefits

The technology is portable as it runs on multiple VA-approved operating systems.

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 (10/17/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (10/17/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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

EMAIL UPDATES