Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 20.6

VLTrader
VLTrader Technology

General InformationGeneral Information help

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: VLTrader is software used for transferring files via secure protocols. This technology resolves ad hoc communication issues, including large files or attachments containing sensitive information. This technology provides visibility to support data concerns stemming from security issues and is designed to meet necessary compliance and regulatory standards, manage data exchanges, and merge disparate systems.

This technology uses local file storage for the file transfer payloads, configuration files, and file tracking information. Optionally, users can leverage network-attached storage, Hadoop Distributed File System (HDFS), and Amazon S3. Configuration and logging information is stored in Extensible Markup Language (XML)-formatted files. Users can optionally configure for tracking and log information to be stored in a database. Supported databases include Oracle, Microsoft Structured Query Language (SQL) Server, MySQL, PostgreSQL, and DB2.

This technology does not store the files in an encrypted state by default, but can be configured for repository encryption of the file transfer payloads. The repository encryption method and algorithm are configurable. Passwords are stored as a password hash.

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 on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC 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://vaww.portal.va.gov/sites/ECS/SitePages/Home.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 v19.8
Decision Date: 08/23/2019
Aliases: VersaLex Trader
Introduced By: TRM Request
Vendor Name: Cleo
- The information contained on this page is accurate as of the Decision Date (08/23/2019).