| 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> |
| 1.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, 6, 7] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7] |
DIVEST
[2, 3, 4, 6, 7, 8, 9] |
DIVEST
[2, 3, 4, 6, 7, 8, 9] |
DIVEST
[2, 3, 6, 7, 8, 9, 10] |
DIVEST
[2, 3, 6, 7, 8, 9, 10] |
| 2.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[2, 3, 4, 5, 6, 7] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints
[2, 3, 6, 7, 8, 9, 10] |
Approved w/Constraints
[2, 3, 6, 7, 8, 9, 10] |
| | | | [1] | This product includes a Bluetooth capability. If that capability is leveraged by the implementer, the implementer must conform to the Bluetooth standard.
The VA and authorized users must be aware that using this application does not make the effected device FIPS 140-2 compliant and additional measures should be taken to ensure compliance. Ensure the use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices that use Bluetooth.
The following are measures to mitigate security attack vectors for Bluetooth:
- Bluetooth is to be enabled only when required.
- Enable Bluetooth discovery only when necessary, and disable discovery when finished.
- Avoid entering link keys or PINs when unexpectedly prompted to do so.
- Remove paired devices when not in use.
- Regularly update firmware on Bluetooth-enabled devices.
Security Mode 4, Level 4 must be used, with Bluetooth BR/EDR/HS, as it requires Secure Connections, which uses authenticated pairing and encryption using 128-bit strength keys generated using FIPS-authorized Advanced Encryption Standard (AES) encryption as required per VA Handbook 6500 AC-18.
Security Mode 1 Level 4 requires low energy Secure Connections authenticated pairing and encryption using AES-CMAC and P-256 elliptic curve. NIST considers this the most secure of these modes/levels and strongly recommends its use for all low energy connections in 4.2. For 4.0 and 4.1 low energy connections, NIST strongly recommends using Security Mode 1 Level 3 as it requires authenticated pairing and encryption although not as strong (not using P-256 elliptical curve) encryption as Level 4. Security Mode 1 Level 1 is the least secure and should never be used. | | | [2] | This product includes a Bluetooth capability. If that capability is leveraged, the implementer must conform to the Bluetooth Standard. 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] | 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. | | | [4] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: [OIT ITOPS SD Engagement Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | | [5] | 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). | | | [6] | 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. | | | [7] | 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). | | | [8] | Users must ensure that Microsoft .NET Framework, Microsoft Internet Explorer (IE), Microsoft Internet Information Services (IIS) and Microsoft Structured Query Language (SQL) Server 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:
- The VA and authorized users must be aware that using this application does not make the effected device FIPS 140-2 compliant and additional measures should be taken to ensure compliance. Ensure the use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices that use Bluetooth.
- Security Mode 4, Level 4 must be used, with Bluetooth BR/EDR/HS, as it requires Secure Connections, which uses authenticated pairing and encryption using 128-bit strength keys generated using FIPS-authorized Advanced Encryption Standard (AES) encryption as required per VA Handbook 6500 AC-18.
- Security Mode 1 Level 4 requires low energy Secure Connections authenticated pairing and encryption using AES-CMAC and P-256 elliptic curve. NIST considers this the most secure of these modes/levels and strongly recommends its use for all low energy connections in 4.2. For 4.0 and 4.1 low energy connections, NIST strongly recommends using Security Mode 1 Level 3 as it requires authenticated pairing and encryption although not as strong (not using P-256 elliptical curve) encryption as Level 4. Security Mode 1 Level 1 is the least secure and should never be used.
| | | [9] | 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). | | | [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. |
|
| Note: |
At the time of writing, version 2.527 is the most current version and released 04/03/2019. |
