| 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 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 |
Authorized w/ Constraints (POA&M): 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 |
Authorized w/ Constraints (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 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 |
Authorized w/ Constraints (PLANNING/EVALUATION): 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 Authorized w/ Constraints (POA&M). |
|
<Past |
Future> |
| 5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 6.8.x |
Approved w/Constraints
[3, 5, 6, 8] |
DIVEST
[3, 6, 8, 9, 10] |
DIVEST
[3, 6, 8, 9, 10] |
DIVEST
[3, 6, 8, 9, 10] |
Authorized w/ Constraints (DIVEST)
[3, 6, 8, 9, 10] |
DIVEST
[3, 6, 8, 9, 10] |
DIVEST
[3, 6, 8, 9, 10] |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 6.29.x |
Unapproved |
Approved w/Constraints
[3, 6, 8, 9, 10] |
Approved w/Constraints
[3, 6, 8, 9, 10] |
Approved w/Constraints
[3, 6, 8, 9, 10] |
Authorized w/ Constraints
[3, 6, 8, 9, 10] |
Approved w/Constraints
[3, 6, 8, 9, 10] |
Approved w/Constraints
[3, 6, 8, 9, 10] |
Approved w/Constraints
[3, 6, 8, 9, 10] |
Authorized w/ Constraints
[3, 6, 8, 9, 10] |
Authorized w/ Constraints
[3, 6, 8, 9, 10] |
Authorized w/ Constraints
[3, 6, 8, 9, 10] |
Authorized w/ Constraints
[3, 6, 8, 9, 10] |
| | | | [1] | Users must ensure that Firefox, Google Chrome, Microsoft Internet Explorer (IE), and Safari are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 cryptographic module to secure VA sensitive data in applications and devices that use the Okta Browser plugin.
- The Okta Browser Plugin should only be considered when a VA authorized solution does not meet the necessary requirements, and the use for more specialized tools are warranted.
- Due to potential information security risks, SaaS/Platform as a Service(PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
- VA Solution Delivery, Desktop and Device Engineering manages the browsers reviewed (Chrome, Firefox, Internet Explorer and Edge) standard configurations. The standard is based on the applicable DISA STIG, which requires all extensions to be blocked by default. For browser plugins/extensions to be included in the national standard configuration, a request and a business justification must be submitted to Desktop and Device Engineering at the following URL: https://vaww.eie.va.gov/SysDesign/CS/dtrequests. If authorized and enabled, all VA endpoint browsers will receive the extension. Therefore, all browser extensions must be evaluated to determine how each will affect the browser with all the other authorized extensions as well as performance of the browser.
The Okta browser plugin is not Federal Information Processing Standards (FIPS) 140-2 certified. The plugin does utilize Transport Layer Security (TLS) 1.2 for data in transit. Ensure use of a FIPS 140-2 cryptographic module to secure VA sensitive data in applications and devices that use the Okta Browser plugin.
There are other VA-authorized solutions that can be utilized. The Okta Browser Plugin should only be considered when a VA-authorized solution does not meet the necessary requirements, and the use for more specialized tools are warranted.
Okta is a Federal Information Security Management Act (FISMA) Moderate level Federal Risk and Authorization Management Program (FedRAMP) authorized Software as a Service (SaaS) solution; however, due to potential information security risks, SaaS/Platform as a Service(PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Authority to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
The Okta plugin has not been evaluated by Solution Delivery, Desktop and Device Engineering, which manages the browsers reviewed (Chrome, Firefox, Internet Explorer and Edge) standard configurations. The standard is based on the applicable Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG), which requires all extensions to be blocked by default. For browser plugins/extensions to be included in the national standard configuration, a request and a business justification must be submitted to Desktop and Device Engineering at the following URL: https://vaww.eie.va.gov/SysDesign/CS/dtrequests. If authorized and enabled, all VA endpoint browsers will receive the extension. Therefore, all browser extensions must be evaluated to determine how each will affect the browser with all the other authorized extensions as well as performance of the browser. | | | [2] | 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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [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. | | | [4] | 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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [5] | Users must ensure that Firefox, Google Chrome, Microsoft Internet Explorer (IE), and Safari are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 cryptographic module to secure VA sensitive data in applications and devices that use the Okta Browser plugin.
- The Okta Browser Plugin should only be considered when a VA authorized solution does not meet the necessary requirements, and the use for more specialized tools are warranted.
- Users must Divest the use of Internet Explorer with this technology. Other authorized internet browsers are available. See Category Tab for details.
- Due to potential information security risks, SaaS/Platform as a Service(PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
- VA Solution Delivery, Desktop and Device Engineering manages the browsers reviewed (Chrome, Firefox, Internet Explorer and Edge) standard configurations. The standard is based on the applicable DISA STIG, which requires all extensions to be blocked by default. For browser plugins/extensions to be included in the national standard configuration, a request and a business justification must be submitted to Desktop and Device Engineering at the following URL: https://vaww.eie.va.gov/SysDesign/CS/dtrequests. If authorized and enabled, all VA endpoint browsers will receive the extension. Therefore, all browser extensions must be evaluated to determine how each will affect the browser with all the other authorized extensions as well as performance of the browser.
. | | | [6] | Browser plug-ins and extensions may only be installed by VA IT Operations (ITOPS) and must be used with official VA browser installation packages that are managed by ITOPS. For installation, contact the National Service Desk [Mail Group: National Service Desk - Austin]. Browser extensions must be kept up to date with security patches and enhancements. | | | [7] | 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 VA Handbook 6500. | | | [8] | 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. | | | [9] | Users must ensure that Firefox, Google Chrome, and Microsoft Edge are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must utilize authorized internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize the Secure Hypertext Transfer Protocol (S-HTTP) protocol, as it is unapproved for use on the TRM.
Per the Security Assessment Review, users must abide by the following constraints:
- The Okta browser plugin will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive data.
- The Okta Browser Extension uses permissions that give the extension access to run on all http and https sites. It may be possible to avoid declaring any host permissions by using the activeTab permission. It also uses the Cookies (gives the extension access to the chrome.cookies API), webRequet (gives theextension access to the chrome.webRequest API), privacy (gives the extension access to the chrome.privacy API) and tabs, permissions. The tabs permissiongrants the extension access to privileged fields of the Tab objects used by several API’s. In many circumstances extensions will not need to declare the `tabs` permission to make use of these APIs.
- The administrator or installer should ensure that the Okta browser extensions obtained from the Chrome or Firefox webstore with verifiable web certificates. 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 OIT representative for permission to download and use this software.
| | | [10] | 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. |
|
| Note: |
At the time of writing, version 6.29.0 is the most current version, released 03/01/2024. |
