Integrated Visual and Auditory Plus Continuous Performance Test Second Edition Iva 2

VA Technical Reference Model v 22.8

Integrated Visual and Auditory (IVA)-2 Continuous Performance Test (CPT)

1. General
2. Decision
3. Reference
4. Component
5. Category
6. Analysis

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:	The Integrated Visual and Auditory (IVA)-2 Continuous Performance Test (CPT) is a psychological test that helps clinicians evaluate both visual and auditory attention and response control functioning. This technology includes free online, self-scoring Attention Deficit Hyperactivity Disorder (ADHD) parent, teacher, and self-rating scales and a report writer that helps guide clinicians in making a diagnosis. This technology utilizes a Microsoft Structured Query Language (SQL) Server database to store test results and other data.
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.10
Decision Date:	10/01/2021
Introduced By:	TRM Request
Vendor Name:	BrainTrain, Inc.

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
2016.2	01/18/2016
2017.2	03/15/2017
2018.x	03/12/2018
2019.x	01/31/2019
2020.x

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	CY2021				CY2022				CY2023				Future>
Release	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4
2016.2	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved
2017.2	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved
2018.x	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved
2019.x	Approved w/Constraints [1, 7, 8]	Approved w/Constraints [1, 7, 8]	Approved w/Constraints [1, 7, 8]	Divest [6, 7, 8, 9, 10]	Divest [6, 7, 8, 9, 10]	Divest [6, 7, 8, 9, 10]	Divest [6, 7, 8, 9, 10]	Divest [6, 7, 8, 9, 10]	Unapproved	Unapproved	Unapproved	Unapproved
2020.x	Unapproved	Unapproved	Unapproved	Approved w/Constraints [6, 7, 8, 9, 10]	Approved w/Constraints [6, 7, 8, 9, 10]	Approved w/Constraints [6, 7, 8, 9, 10]	Approved w/Constraints [6, 7, 8, 9, 10]	Approved w/Constraints [6, 7, 8, 9, 10]	Approved w/Constraints [6, 7, 8, 9, 10]	Approved w/Constraints [6, 7, 8, 9, 10]	Approved w/Constraints [6, 7, 8, 9, 10]	Approved w/Constraints [6, 7, 8, 9, 10]
	Decision Constraints [1] If free trialware is utilized, the software must be purchased or removed at the end of the trial period. [2] Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). [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] 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. [5] Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). [6] 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. [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] Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). [9] If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Internet Explorer (IE) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the 'Category' tab under 'Runtime Dependencies') [10] 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.
Note:	At the time of this writing, 2020.1 is the most recently released version.

The following reference(s) are associated with this entry:

Type	Name	Source	Description
There are no references identified for this entry.

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.

• Windows Client - Approved w/Constraints

Adoption Benefits

• This is a mature technology.

• 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.

• According to the vendor, this technology is 508-compliant.

• This technology can assist physicians in working with patients to help diagnose health problems related to auditory and visual attention.

• This is a well-documented technology.

Adoption Risks

• 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.

• There are multiple TRM-approved technologies with similar or duplicate functionality.

• This technology has the potential to store, collect, or transmit Personally Identifiable Information (PII)/Protected Health Information (PHI).

• This software has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.

Architectural Benefits

• This technology can use a VA-preferred database.

Architectural Risks

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

- The information contained on this page is accurate as of the Decision Date (10/01/2021).

farrellingdon.blogspot.com

Source: https://www.oit.va.gov/Services/TRM/ToolPage.aspx?tid=9513

Share this post