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> |
11.0.x |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
12.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
| | [1] | Per the Initial Product Review/Security Assessment Review, users must abide by the following constraints:
- A vulnerability exists because CE-Deploy version 11.0.5 is not recognized by Windows Defender SmartScreen. To mitigate, an administrator shall monitor the files used by the application with a file integrity tool to ensure no unauthorized changes occur. Trellix is the VA authorized solution and may be used to track file changes to the specified files installed by the application.
- A vulnerability exists because CE-Deploy version 11.0.5 provides automatic/user configurable checks for updates. To mitigate, the administrator shall control the versioning of CE-Deploy version 11.0.5 software and do not allow users to install unapproved versions.
- A vulnerability exists because CE-Deploy version 11.0.5 is Open-Source Software (OSS). To mitigate maintenance and support will be provided for the Open-Source Software used within CE-Deploy version 11.0.5 as per the applications lifecycle.
| | [2] | 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 authorized and the user should take the proper steps to decline those installations. | | [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] | Per the Security Assessment Review, users must abide by the following constraints:
- System Owners/Administrators need to be aware the Windows SmartScreen blocks the installation of the product. Once the file is downloaded, the unblock option must be checked in the file properties to allow installation.
- The use of open-source products, lacking any vendor support, hosting potentially critical VA production systems may pose severe security risks to the VA. Relying on vendor support may result in slow response times and non-timely patches. Users should check with their supervisor, ISSO or local OIT representative for permission to download and use this software.
- Due to potential information security risks, SaaS/PaaS solutions must complete the BIOS process where a collaborative effort between DM,
EPMO IA, DTC, ECSO, CTO, and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and ATO with technical oversight, acquisition, production, and sustainment provided by DTC.
- CE-Deploy will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/ PII or VA sensitive
information.
- System Administrators shall monitor all the .exe files used by the application with a file integrity checker to ensure no unauthorized changes occur.
- System Administrators shall control the versioning of the software and do not allow users to install unapproved versions.
| | [5] | 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 12.4.2 is the most current version, released 11/07/2024. |