Reflector

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:	Reflector is software that allows iPhone, iPad, Chromebooks, Android, and Windows tablet screens to be mirrored onto a Mac or Personal Computer (PC) over a wireless network connection. It turns macOS and Windows devices into AirPlay, Google Cast, or Miracast receivers. 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 approved 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 been assessed by the Section 508 Office and found non-conformant. 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. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.3
Decision Date:	03/13/2023 at 16:47:48 UTC
Aliases:	Reflection
Introduced By:	TRM Request
Vendor Name:	Squirrels LLC

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
1.2.3
1.3	10/30/2013
1.3.1	11/01/2013
1.3.4	03/24/2014
1.4	08/04/2014
1.5	09/25/2014
2.0	05/28/2015
2.1	08/19/2015
2.2	09/25/2015
2.3	11/09/2015
2.4.x (Mac)	01/06/2016
2.5.x (Mac)	04/13/2016
2.6.x (Mac)	11/17/2016
3.x (Mac)	11/21/2017
2.4.x (Windows)	01/06/2016
2.5.x (Windows)	04/14/2016
2.6.x (Windows)	11/17/2016
3.x (Windows)	11/21/2017
4.x (Windows)	03/22/2021
4.x (Mac)	03/22/2021

Current Decision Matrix (03/09/2023)

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

CY2017

CY2018

CY2019

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

1.3.1

Unapproved

1.3.4

Unapproved

1.4

Divest
[4, 5, 6]

Unapproved

1.5

Divest
[4, 5, 6]

Unapproved

2.3

Divest
[4, 5, 6]

Unapproved

2.4.x (Mac)

Approved w/Constraints
[4, 5, 6]

Approved w/Constraints
[4, 5, 7]

Divest
[5, 7, 8]

Divest
[5, 7, 9, 10]

Unapproved

2.5.x (Mac)

Approved w/Constraints
[4, 5, 6]

Approved w/Constraints
[4, 5, 7]

Divest
[5, 7, 8]

Divest
[5, 7, 9, 10]

Unapproved

2.6.x (Mac)

Approved w/Constraints
[4, 5, 6]

Approved w/Constraints
[4, 5, 7]

Divest
[5, 7, 8]

Divest
[5, 7, 9, 10]

Unapproved

3.x (Mac)

Unapproved

Approved w/Constraints
[5, 7, 8]

Approved w/Constraints
[5, 7, 9, 10]

Approved w/Constraints
[5, 7, 10, 11]

2.4.x (Windows)

Approved w/Constraints
[4, 5, 6]

Approved w/Constraints
[4, 5, 7]

Divest
[5, 7, 8]

Divest
[5, 7, 9, 10]

Unapproved

2.5.x (Windows)

Approved w/Constraints
[4, 5, 6]

Approved w/Constraints
[4, 5, 7]

Divest
[5, 7, 8]

Divest
[5, 7, 9, 10]

Unapproved

2.6.x (Windows)

Approved w/Constraints
[4, 5, 6]

Approved w/Constraints
[4, 5, 7]

Divest
[5, 7, 8]

Divest
[5, 7, 9, 10]

Unapproved

3.x (Windows)

Unapproved

Approved w/Constraints
[5, 7, 8]

Approved w/Constraints
[5, 7, 9, 10]

Approved w/Constraints
[5, 7, 10, 11]

4.x (Windows)

Unapproved

4.x (Mac)

Unapproved

Decision Constraints


[1]	IOS source devices must only be those issued and managed by the organization and in compliance with existing mobile security policies and procedures. The application must be properly passworded to ensure only specific iOS devices can connect to target systems. Product, source and target devices must remain patched and operated in accordance with Federal and Department security policies and guidelines. Product may not be used in clinical or other settings that may involve PHI or PII data due to the lack of FIPS 140-2 encryption capabilities.

[2]	IOS source devices must only be those issued and managed by the organization and in compliance with existing mobile security policies and procedures. The application must be properly password protected to ensure only specific iOS devices can connect to target systems. Product, source and target devices must remain patched and operated in accordance with Federal and Department security policies and guidelines. Product may not be used in clinical or other settings that may involve PHI or PII data due to the lack of FIPS 140-2 encryption capabilities.

[3]	As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

[4]	iOS source devices must only be those issued and managed by the VA and in compliance with existing mobile security policies and procedures. The application must be properly password protected to ensure only specific iOS devices can connect to target systems. Product, source and target devices must remain patched and operated in accordance with Federal and Department security policies and guidelines. Product may not be used in clinical or other settings that may involve Personally Identifiable Information (PII) or Protected Health information (PHI) data due to the lack of Federal Information Processing Standard (FIPS) 140-2 encryption capabilities. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[5]	Users should check with their supervisor, Information Security Office (ISO) 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 approved and the user should take the proper steps to decline those installations.

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

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

[8]	iOS source devices must only be those issued and managed by the VA and in compliance with existing mobile security policies and procedures. The application must be properly password protected to ensure only specific iOS devices can connect to target systems. Product, source and target devices must remain patched and operated in accordance with Federal and Department security policies and guidelines. This technology may not be used in clinical or other settings that may involve Personally Identifiable Information (PII) or Protected Health information (PHI) data due to the lack of Federal Information Processing Standard (FIPS) 140-2 encryption capabilities. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[9]	iOS source devices must only be those issued and managed by the VA and in compliance with existing mobile security policies and procedures. The application must be properly password protected to ensure only specific iOS devices can connect to target systems. Product, source and target devices must remain patched and operated in accordance with Federal and Department security policies and guidelines. This technology must not be used in clinical or other settings that may involve Personally Identifiable Information (PII) or Protected Health information (PHI) data due to the lack of Federal Information Processing Standard (FIPS) 140-2 encryption capabilities. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[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]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. iOS source devices must only be those issued and managed by the VA and in compliance with existing mobile security policies and procedures. The application must be properly password protected to ensure only specific iOS devices can connect to target systems. Product, source, and target devices must remain patched and operated in accordance with Federal and Department security policies and guidelines. This technology must not be used in clinical or other settings that may involve Personally Identifiable Information (PII) or Protected Health information (PHI) data due to the lack of Federal Information Processing Standard (FIPS) 140-2 encryption capabilities.

Note:

At the time of writing, version 4.1.0 is the most current version for both macOS and Windows.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Reflector 4 Release Notes		Reflector 4.0 Initial Release Notes and Documentation.
*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
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology User Interface	Mobile Framework
Platforms and Storage Operating Systems	OS Tools

Operating Systems Supported by the Technology

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

Technologies/Standards Relationships

Runtime Dependencies:

No runtime dependencies have been identified.

Comparable Technologies:

Companion Technologies/Supported Standards:

No companion technologies/standards have been identified.

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.
There are minimal other TRM-approved technologies that provide the same functionality.
This is a well-documented technology.

Adoption Risks

There is no indication based on available vendor documentation that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
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
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
Due to the rapid release schedule of this product, 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 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 (03/09/2023)

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 (03/09/2023)

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