Reflection for Secure Information Technology (IT) Gateway

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:	Reflection for Secure Information Technology (IT) Gateway performs file management. It offers two key features: Jobs and Transfer Sites. Both use secure authentication and encryption for all connections and provide administrators with multiple options for creating custom configurations appropriate to different users and business practices.
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.7
Decision Date:	07/18/2022 at 18:22:54 UTC
Aliases:	RSIT Gateway
Introduced By:	TRM Request
Vendor Name:	Micro Focus

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.1.x	07/13/2016

Current Decision Matrix (07/13/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 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

CY2020

CY2021

CY2022

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

1.1.x

Approved w/Constraints
[1, 2, 4, 5, 6]

Approved w/Constraints
[1, 2, 4, 5, 7]

Approved w/Constraints
[4, 5, 7, 8, 9]

Unapproved

Decision Constraints


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

[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]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This technology must run on an approved version of the Oracle Java Runtime Environment (JRE).

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

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

[6]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This technology must run on an approved version of the Oracle Java Standard Edition (SE) Development Kit. Users must ensure that they are implementing this technology with the baselined version of Microsoft Internet Explorer and Google Chrome.

[7]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This technology must run on an approved version of the Oracle Java Standard Edition (SE) Development Kit. Users must ensure that they are implementing this technology with VA-approved baselines of Microsoft Internet Explorer, Firefox, and Google Chrome. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle.

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

Note:

At the time of writing, version 1.1.SP2 is the most current version, released 07/23/2019.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Reflection for Secure IT Gateway - Documentation		This link points to Reflection for Secure IT Gateway documents, including Release Notes, Administrator's Guide, and Evaluation Guides.
*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
Gateway Administrator	The Gateway Administrator service is required for all Reflection for Secure IT Gateway installations. It should be installed on a system in your internal network.
Reflection Hub	The Reflection Hub is required for automated Jobs. This service should be installed on a system running in your internal network.
Reflection Public Key Infrastructure (PKI) Services Manager	Reflection PKI Services Manager is an optional component that provides Public Key Infrastructure (PKI) support for a number of Attachmate products.
Reflection Secure Shell Proxy	The Reflection Transfer Server and Reflection Secure Shell Proxy are required for Transfer Sites. These two services must be installed together using the Setup Gateway Proxy feature. These services are typically installed on a system in the DMZ.
Reflection Transfer Server	The Reflection Transfer Server and Reflection Secure Shell Proxy are required for Transfer Sites. These two services must be installed together using the Setup Gateway Proxy feature. These services are typically installed on a system in the DMZ.
Secure File Transfer Protocol (SFTP) Servers	The number and arrangement of Secure File Transfer Protocol (SFTP) servers depends on the business needs. These can be any UNIX or Windows servers running SFTP-enabled SSH.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Network and Telecommunications Transport	Wide Area Network (WAN)

Operating Systems Supported by the Technology

Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Reflection for Secure IT Gateway may be configured for Federal Information Processing Services (FIPS) 140-2 Level 1 validation (certificate #2468).
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 technology has a comprehensive set of documentation.
This technology may improve productivity for specific staff whose responsibilities include file management.

Adoption Risks

This technology requires Zulu, an unapproved technology.
This technology may utilize external data connections.
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 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.
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.
Microsoft Internet Explorer, a dependency of this technology, is in End of Life status and must no longer be used.
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.
This technology can integrate with and alter database technologies.
The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.

Architectural Benefits

This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.
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 is not portable as it runs only on Windows platforms.
This technology does not use a VA-preferred database to store data.

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 (07/13/2022)

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

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (07/13/2022)

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

Architectural Risks

EMAIL UPDATES