Hiperwall

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:	Hiperwall is a video wall content and source management solution package that enables users to connect different sources to a video wall, show and control conventional computer applications on the display and stream high-definition movies and video feeds to a unified display surface built from multiple commercial monitors. This technology is available in two editions: Hiperwall Premium and Hiperwall Core Edition. This assessment covers both versions.
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 v24.6
Decision Date:	06/11/2024 at 16:45:46 UTC
Introduced By:	TRM Request
Vendor Name:	Hiperwall

Vendor Release Information

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

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
4.x	02/09/2015
5.0	11/14/2017
5.1	06/05/2018
6.0	02/15/2019
6.0.2	01/10/2020
7.2.x
8.5.x	05/23/2023

Current Decision Matrix (06/05/2024)

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 VA IT 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. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved 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	Unapproved: 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	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 unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint: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 approved 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 approved 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.

<Past

CY2029

CY2030

CY2031

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

4.x

Unapproved

5.0

Unapproved

5.1

Unapproved

6.0

Unapproved

6.0.2

Unapproved

7.2.x

Unapproved

8.5.x

Approved w/Constraints
[9, 10, 11, 12, 13]

Decision Constraints


[1]	This technology includes functionality requiring Quicktime. Windows users may be limited as Quicktime is prohibited for use in the TRM on Windows platforms. New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a Systems Engineering Design Review (SEDR) (contact VA e-mail: VA IT ESE SEDR SEG) prior to implementation to ensure proper compliance to VA network design and usage requirements.

[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]	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]	This technology includes functionality requiring Quicktime. Windows users must not leverage Quicktime as it is prohibited for use in the TRM on Windows platforms. 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]	This technology includes functionality that requires QuickTime. Windows users must not leverage QuickTime as it is prohibited for use in the TRM on Windows platforms. 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.This technology includes functionality requiring Quicktime. Windows users must not leverage Quicktime as it is prohibited for use in the TRM on Windows platforms.

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

[7]	Security Engineering (SE) conducted a pre-assessment and security requirements verification of Hiperwall. It is advised that if this product is used within the VA that the following constraints be applied: The underlying infrastructure must provide the FIPS 140-2 encryption for data at rest or in transit. Hiperwall must only use TRM approved codec packs within the VA. This technology cannot be used until a Secure Configuration Baseline is developed. In order to reduce costs, risk and overhead in many areas including: training, patching, configuration standards, and documentation, VA has standardized the types and configurations of the platforms/technologies it uses and maintains baselines for in its internal operating environment.

[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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[9]	Per the Initial Product Review, users must abide by the following constraints: The underlying infrastructure must provide the FIPS 140-2 certified encryption for data at rest or in transit where applicable. This technology should not be used without a Secure Configuration Baseline or Implementation Standard. In order to reduce costs, risk and overhead in many areas including: training, patching, configuration standards, and documentation, VA has standardized the types and configurations of the platforms/technologies it uses and maintains baselines for in its internal operating environment. If it is determined that Hiperwall is an enterprise product the Baseline Configuration Management team will need to create an Enterprise Secure Configuration Baseline or Implementation Standard. If the product is determined to be a one-off implementation, Hiperwall will need the same, but it will be the system owner’s responsibility to develop a system level baseline. Without a published DISA STIG or NIST validated checklist, creating a baseline requires substantial effort and significant time and cost. The project team will require written vendor commitment for assistance and continued vendor support and a VA Subject Matter Expert (SME) point of contact with a signed Baseline ownership Memorandum of Understanding (MOU). To begin exploring baseline/standard creation, the project team requesting to use this technology must submit a Solution Delivery, Baseline and Configuration Management (BCM) SNOW request via the following link: https://yourit.va.gov/va?id=sc_cat_item&sys_id=4894aef0dbedc0949b1534cc7c961902

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

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

[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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[13]	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 8.5.0 is the latest version of this technology, released 05/23/2023.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Control Node	Control Node is the management point of the entire system.
Display Node	Display Node works through the monitors or display devices that show content to the viewer.
Secondary Control Node	This provides the ability to control content selection from multiple locations or work stations.
Sender Node	Sender Node delivers feeds to the Display Node.
Streamer Node	This delivers feeds to the Display Node.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Collaboration and Electronic Workplace Productivity Software	Multimedia Software

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Windows Client - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

QuickTime

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.
This is a well-documented technology.
This technology supports several industry standard file formats.

Adoption Risks

The potential of vendor lock exists when utilizing proprietary vendor technology.
Hiperwall is not Federal Information Processing Standards (FIPS) 140-2 certified, it relies on the host device’s FIPS encryption.
No Secure Configuration Baseline or Enterprise Implementation Standard exists for Hiperwall.
The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
This technology may transmit data over the VA Wide Area Network (WAN).
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.
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.

Architectural Benefits

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

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (06/05/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (06/05/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES