<Past |
Future> |
2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
77.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
91.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
92.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
103.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
105.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
108.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
109.x |
Divest [6, 7, 9, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
110.x |
Divest [6, 7, 9, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
111.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
112.x |
Divest [6, 7, 9, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
113.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
114.x |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
115.x |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
Approved w/Constraints [6, 7, 9, 10, 11, 12] |
| | [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 |