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> |
3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.0 |
Unapproved |
DIVEST [1, 2, 3, 4, 5, 6] |
DIVEST [1, 2, 3, 4, 5, 6] |
DIVEST [1, 2, 3, 4, 5, 6] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.4 |
Unapproved |
Approved w/Constraints [1, 2, 3, 4, 5, 6] |
Approved w/Constraints [1, 2, 3, 4, 5, 6] |
Approved w/Constraints [1, 2, 3, 4, 5, 6] |
DIVEST [3, 4, 5, 6, 7, 8] |
DIVEST [3, 4, 5, 6, 7, 8] |
DIVEST [3, 4, 5, 6, 7, 8] |
DIVEST [3, 4, 5, 6, 7, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5, 6, 7, 8] |
Approved w/Constraints [3, 4, 5, 6, 7, 8] |
Approved w/Constraints [3, 4, 5, 6, 7, 8] |
DIVEST [3, 4, 5, 6, 7, 8] |
DIVEST [3, 4, 5, 7, 8, 9] |
DIVEST [3, 4, 5, 7, 8, 9] |
DIVEST [3, 4, 5, 7, 9, 10] |
DIVEST [3, 4, 5, 9, 10, 11] |
4.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5, 6, 7, 8] |
Approved w/Constraints [3, 4, 5, 7, 8, 9] |
Approved w/Constraints [3, 4, 5, 7, 8, 9] |
Approved w/Constraints [3, 4, 5, 7, 9, 10] |
DIVEST [3, 4, 5, 9, 10, 11] |
4.9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5, 9, 10, 11] |
4.10.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.11.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.12.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | Niagara 4 Supervisor must not be used for any data containing PHI/PII, sensitive information. After release of version 4.6 this constraint may be re-evaluated.
Niagara 4 Supervisor must only use operating systems that have authorized VA Configuration Baselines.
Niagara 4 Supervisor must only use database systems that have authorized VA Configuration Baselines.
Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. 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).
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. | | [2] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | [3] | Use of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing analysis with this technology need to work closely with system owners and agree on security scanning rules, such as the assets scanned, along the schedule and frequency of those scans. | | [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] | 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. | | [6] | 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). | | [7] | Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module is enabled to secure VA sensitive data in applications and devices that utilize Niagra 4. The configuration guide to enable Niagra to run in FIPS 140-2 is attached after the resources.
- Administrators must ensure that FIPS mode is enabled during Niagara 4`s initial install.
- Niagara 4`s applet and webstart must not be used for any data containing Protected HeaIth Information /Personally Identifiable Information.
- Niagra should be configured to meet all VA password requirements with regard to length and complexity. VA Handbook 6500 Control IA-5: Authenticator Management sets a standard of at least 8 non-blank characters. They must contain characters from three (3) of the following four (4) categories:` English upper case characters` English lower case characters` Base-10 digits` Non-alphanumeric special charactersSix of the characters must not occur more than once in the password. It is strongly advisable that users should not use VA credentials or weak passwords to non-VA IT systems and vice versa.
- Niagara 4 Supervisor must only use operating systems that have authorized VA Configuration Baselines.
- Niagara 4 Supervisor must only use database systems that have authorized VA Configuration Baselines.
- Due to potential information security risks, SaaS 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.
| | [8] | 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. | | [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. | | [11] | Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module is enabled to secure VA sensitive data in applications and devices that utilize Niagra 4. The configuration guide to enable Niagra to run in FIPS 140-2 is attached after the resources.
- Administrators must ensure that FIPS mode is enabled during Niagara 4`s initial install.
- Niagara 4`s applet and webstart must not be used for any data containing Protected HeaIth Information /Personally Identifiable Information.
- Niagra should be configured to meet all VA password requirements with regard to length and complexity. VA Handbook 6500 Control IA-5: Authenticator Management sets a standard of at least 8 non-blank characters. They must contain characters from three (3) of the following four (4) categories:
- English upper case characters
- English lower case characters
- Base-10 digits
- Non-alphanumeric special characters
Six of the characters must not occur more than once in the password. It is strongly advisable that users should not use VA credentials or weak passwords to non-VA IT systems and vice versa.
- Niagara 4 Supervisor must only use operating systems that have authorized VA Configuration Baselines.
- Niagara 4 Supervisor must only use database systems that have authorized VA Configuration Baselines.
- Due to potential information security risks, SaaS 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.
|
|
Note: |
At the time of writing, version 4.12.0 is the most current version, released 09/12/2022. |