OTCnet

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:	Over-the-Counter Channel (OTCnet) is a Web-based application that integrates Check Capture and Deposit Reporting functionalities into one system. Created from two legacy systems, Paper Check Conversion Over The Counter System (PCC OTC) and Treasury General Account Deposit Reporting Network (TGAnet), OTCnet`s design accommodates check capture and deposit reporting using electronic collection mechanisms instead of paper based processing. Please note: Over-the-Counter Channel (OTCnet) contains an OTCnet Local Bridge (OLB) and OTCnet Firmware. The firmware deployed by this software does not require TRM approval on its own, only OLB. OTCnet OLB is handled by its own separate TRM entry. Additionally, OTCnet has an Online and Offline Mode. This review covers the Online Mode only, all software is provided through the browser so eligible checks are converted end to end over the internet.
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 v21.6
Decision Date:	06/25/2021
Aliases:	OTCnet Offline Production
Introduced By:	TRM Request
Vendor Name:	Bureau of the Fiscal Service

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.3	10/01/2012
1.3.1	12/01/2012
1.3.2	03/01/2013
1.4	09/13/2013
1.5	06/01/2014
2.1	09/01/2015
2.2	06/01/2016
2.3	11/01/2016
2.4	12/01/2016
2.5	07/28/2017
2.7	03/01/2018
2.10	03/25/2019
3.2	05/01/2020
3.3	09/01/2020
3.4	01/21/2021
3.5	04/30/2021

Current Decision Matrix (06/22/2021)

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 STAT review is conducted and signed by Associate Deputy Assistant Secretary (ADAS), Enterprise Program Management Office (EPMO) or designee and based upon a recommendation from the Strategic Technology Alignment Team (STAT) Working Group (WG), 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.3

Unapproved

1.3.1

Unapproved

1.3.2

Unapproved

1.4

Unapproved

1.5

Unapproved

2.1

Unapproved

2.2

Unapproved

2.3

Unapproved

2.4

Unapproved

2.5

Unapproved

2.7

Divest
[1, 3, 8]

Unapproved

2.10

Approved w/Constraints
[1, 3, 8]

Divest
[1, 3, 9]

Divest
[3, 10]

Unapproved

3.2

Unapproved

Approved w/Constraints
[1, 3, 9]

Divest
[3, 10]

Divest
[10, 11]

Unapproved

3.3

Unapproved

Approved w/Constraints
[3, 10]

Approved w/Constraints
[10, 11]

Divest
[10, 11]

Unapproved

3.4

Unapproved

Divest
[10, 11]

Unapproved

3.5

Unapproved

Approved w/Constraints
[10, 11]

Decision Constraints


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

[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]	OTC uses the Java Runtime Environment (JRE). It is recommended that the latest release of Java 8, 32-bit be maintained at all times to ensure the highest level of security. It is a requirement that VA sensitive data be properly protected in accordance with VA Handbook 6500, Federal Information Security Management Act (FISMA), and Federal Information Processing Standards (FIPS) 140-2. In accordance with National Institute of Standards and Technology (NIST) SP 800-53 and SP 800-70, Information Security is an important business process that should be considered in all phases of the acquisition process to ensure data and information technology (IT) systems are adequately protected against risk of loss, misuse, and unauthorized access. In accordance with FISMA, government information or government IT systems require compliance with the agency IT Security Policy. All information technology acquisitions must meet the requirements outlined in the Federal Acquisition Regulation (FAR) Part 39.101 (d) policy ensuring the use of common security configuration checklists in the management of risk.

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

[6]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place.

[7]	OTC uses the Java Runtime Environment (JRE). It is recommended that the latest release of Java 8, 32-bit be maintained at all times to ensure the highest level of security. It is a requirement that VA sensitive data be properly protected in accordance with VA Handbook 6500, Federal Information Security Management Act (FISMA), and Federal Information Processing Standards (FIPS) 140-2. In accordance with National Institute of Standards and Technology (NIST) SP 800-53 and SP 800-70, Information Security is an important business process that should be considered in all phases of the acquisition process to ensure data and information technology (IT) systems are adequately protected against risk of loss, misuse, and unauthorized access. In accordance with FISMA, government information or government IT systems require compliance with the agency IT Security Policy. All information technology acquisitions must meet the requirements outlined in the Federal Acquisition Regulation (FAR) Part 39.101 (d) policy ensuring the use of common security configuration checklists in the management of risk.

[8]	Per the Initial Product Review, users must abide by the following constraints: OTC uses the Java Runtime Environment (JRE). It is recommended that the latest release of Java 8, 32-bit be maintained at all times to ensure the highest level of security.

[9]	Users must ensure that Acrobat Reader and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Initial Product Review, users must abide by the following constraints: OTC uses the Java Runtime Environment (JRE). It is recommended that the latest release of Java 8, 32-bit be maintained at all times to ensure the highest level of security. This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.

[10]	Users must ensure that Acrobat Reader and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Initial Product Review, users must abide by the following constraints: OTC uses the Java Runtime Environment (JRE). It is recommended that the latest release of Java 8, 32-bit be maintained at all times to ensure the highest level of security. This technology must use the latest TRM-approved version of a Java Runtime Environment (JRE).

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

Note:

At the time of writing, version 3.5 is the most current version and released 04/30/2021.

References

The following reference(s) are associated with this entry:
Type	Name	Description
Vendor Provided*	OTCnet System Requirements & Reference Guide v3.3	This document provides system and configuration requirements for the use of OTCnet Online for deposit reporting and check capture. This document also provides system and configuration requirements for OTCnet Offline, which is available for users performing check processing/check scanning in areas with low bandwidth and/or unreliable internet connectivity.
Vendor Provided*	OTCnet 3.4 Release Notes	This links to the releases notes for OTCnet version 3.4 and has updated guidelines and application enhancements.
*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
Over-the-Counter Channel Local Bridge (OTCnet OLB)	The OLB is a component which must be installed on all workstations performing check capture, check processing, and terminal configuration operations. Please note, OLB is handled by its own entry and needs its own approval. See entry for more information.

VA Categories View the VA Categorization Framework

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

Operating Systems Supported by the Technology

Windows Client - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

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 Network Security Operations Center (NSOC) bulletins had been issued for the latest versions of this technology.
This is a mature technology.
This is a well-documented technology.
This technology is compliant with Federal Information Security Management Act (FISMA), 508 regulations, Homeland Security Presidential Directive -12 (HSPD-12) and Personal Identity Verification (PIV) standards.
This technology supports Central Accounting and Reporting System (CARS) requirements set by Government Wide Accounting (GWA) that all transactions capture standard classification information at the onset of a transaction.

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.
This technology relies on Java Runtime Environment (JRE) - Oracle, which has a rapid release and update schedule.
This technology has certain functionalities that rely on the permanently unapproved technology Java Access Bridge (JAB).
OTCNet uses the Java Runtime Environment (JRE). Older versions of Java are no longer publicly supported by Oracle and are no longer receiving new security updates.

Architectural Benefits

This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.

Architectural Risks

This technology is not portable as it runs only on Windows platforms.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 21.6

General Information

Vendor Release Information

Current Decision Matrix (06/22/2021)

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 21.6

General Information

Vendor Release Information

Current Decision Matrix (06/22/2021)

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