Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.11

Niagara 4

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Niagara 4 uses tag hierarchies to automatically integrate data in a navigation tree. Using a standardized dictionary of tagged elements, users choose which points to monitor directly. Users can leverage the standardized dictionary to create consistency in their building automation systems. The point-and-click or drag-and-drop interface allows users to create customized charts, allowing them to find and display critical information. This technology also supports data cleaning capabilities and role-based access control. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and authorized by the Mobile Technology and Endpoint Security Engineering Team: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx
Technology/Standard Usage Requirements:	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.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v22.11
Decision Date:	11/04/2022 at 00:18:51 UTC
Aliases:	Niagara 4 Supervisor
Introduced By:	TRM Request
Vendor Name:	Tridium

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
3.x
4.0	08/31/2015
4.4	01/31/2018
4.7.x	10/30/2018
4.8.x	09/19/2019
4.9.x	07/27/2020
4.10.x	03/30/2021
4.11.x	12/15/2021
4.12.x	09/12/2022

Current Decision Matrix (10/14/2022)

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

CY2020

CY2021

CY2022

Future>

Release

3.x

Unapproved

4.0

Unapproved

4.4

Unapproved

4.7.x

DIVEST
[3, 4, 5, 7, 8, 9]

DIVEST
[3, 4, 5, 7, 9, 10]

DIVEST
[3, 4, 5, 9, 10, 11]

DIVEST
[3, 5, 10, 11, 12, 13]

DIVEST
[3, 5, 10, 11, 12, 14]

Unapproved

4.8.x

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]

DIVEST
[3, 5, 10, 11, 12, 13]

DIVEST
[3, 5, 10, 11, 12, 14]

Unapproved

4.9.x

Unapproved

Approved w/Constraints
[3, 4, 5, 9, 10, 11]

Approved w/Constraints
[3, 5, 10, 11, 12, 13]

Approved w/Constraints
[3, 5, 10, 11, 12, 14]

DIVEST
[3, 5, 10, 12, 15, 16, 17, 18, 19]

DIVEST
[3, 5, 10, 12, 16, 17, 18, 20]

4.10.x

Unapproved

DIVEST
[3, 5, 10, 12, 15, 16, 17, 18, 19]

DIVEST
[3, 5, 10, 12, 16, 17, 18, 20]

4.11.x

Unapproved

Approved w/Constraints
[3, 5, 10, 12, 15, 16, 17, 18, 19]

DIVEST
[3, 5, 10, 12, 16, 17, 18, 20]

4.12.x

Unapproved

Approved w/Constraints
[3, 5, 10, 12, 16, 17, 18, 20]

Decision Constraints


[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.

[12]	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.

[13]	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).

[14]	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 (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[15]	Users must ensure that Google Chrome, Firefox, Microsoft Structured Query Language (SQL) Server, and Oracle Database 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 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 section. 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, Platform as a Service (PaaS)/Software as a Service (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), Digital Transformation Center (DTC), 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 DTC. It is advised to install the latest version of this software and monitor the CVE Details website for any new vulnerabilities.

[16]	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).

[17]	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 VA OIT Product Engineering team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[18]	If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details.

[19]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

[20]	Users must ensure that Microsoft Structured Query Language (SQL) Server, VMWare vSphere, and Oracle Database are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle. 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 section. 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, Platform as a Service (PaaS)/Software as a Service (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), Digital Transformation Center (DTC), 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 DTC. It is advised to install the latest version of this software and monitor the CVE Details website for any new vulnerabilities.

Note:

At the time of writing, version 4.12.0 is the most current version, released 09/12/2022.

Name	Description
No components have been identified for this entry.


Information Management Technologies Data Management	Database-Related Management Tools

General Analysis

Adoption Benefits

This is a mature technology.
This is a well-documented technology.
This technology utilizes built-in Authentication and Authorization (A&A) capabilities.

Adoption Risks

The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search for more details.
This technology may transmit data over the VA Wide Area Network (WAN).
An external database is not required however, is recommended if large amounts of data are to be offloaded from the hard drive of the supervisor. External database types which are supported: MySQL 5.7, Oracle 11g, SQL Server 2012, SQL Server 2016.
Although Niagara 4 itself is not Federal Information Process Standards (FIPS) 140-2 certified, it uses the open source Bouncy Castle FIPS Java API (BCFJA) which is certified (certificate #3152).
Niagara 4`s FIPS mode is not automatically enabled.
Niagara 4`s applet and webstart do not have a FIPS mode.
Niagara 4`s password settings are not compliant with VA standards.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
This technology is a scanning utility. Users must ensure scans comply with system owner guidance.
Niagara 4 Supervisor may be installed on the following operating systems: Windows 10 64-bit, Windows 8.1 Enterprise, Windows Server 2012 R2 Standard, and Red Hat Enterprise Linux-7.
This technology can integrate with and alter database technologies.
This product can be configured with a MySQL Commercial Edition Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms.
There is a published vulnerability CVE- 2020-14483 that affect versions4.6.96.28, 4.7.109.20, 4.7.110.32 and 4.8.0.110 of this software which could result in a timeout during a TLS handshake can result in the connection failing to terminate.
This technology relies on Java Runtime Environment (JRE) - Oracle, which has a rapid release and update schedule.

Architectural Benefits

This technology is portable as it runs on multiple TRM-authorized operating systems.
This technology can use a VA-preferred database.
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.
There is a Cloud version of the Niagara 4 Supervisor.

- The information contained on this page is accurate as of the Decision Date (11/04/2022 at 00:18:51 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (10/14/2022)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (10/14/2022)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework