Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.11

Conners Continuous Performance Test (CPT) Third Edition

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:	Conners Continuous Performance Test (CPT) Third Edition is a task oriented computerized assessment of attention-related problems in individuals aged eight years and older. By indexing the respondent`s performance in areas of inattentiveness, impulsivity, sustained attention, and vigilance, this technology can be used in the diagnosis process of Attention-Deficit/Hyperactive Disorder (ADHD) and other neurological conditions related to attention. Conners CPT 3 provides objective information about an individual`s performance in attention tasks, complementing information obtained from rating scales such as the Conners 3. The Conners CPT 3 can be used in conjunction with the Conners Continuous Auditory Test of Attention (Conners CATA), which assesses auditory processing and attention-related problems in individuals aged eight years and older. The Conners CPT 3 and Conners CATA can be purchased as a combo kit or individually. This technology does not utilize a database as data is stored on the user`s local drive.
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 v23.4
Decision Date:	04/05/2023 at 00:57:25 UTC
Aliases:	Conners CPT 3; CPT-3; CPT3; Conners Continuous Performance Test
Introduced By:	TRM Request
Vendor Name:	Multi-Health Systems Inc.

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
5 (CPT 2)	12/30/2000
5.7 (CPT 3)	12/30/2014
5.9 (CPT 3)	02/12/2018
6.1 (CPT 3)
6.1.x (CPT3)

Current Decision Matrix (03/30/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 VAIT 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.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized 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	Authorized w/ Constraints (POA&M): 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	Authorized w/ Constraints (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 unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): 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 authorized 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 authorized 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.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2021

CY2022

CY2023

Future>

Release

5 (CPT 2)

Unapproved

5.7 (CPT 3)

Unapproved

5.9 (CPT 3)

DIVEST
[9, 10]

Unapproved

6.1 (CPT 3)

Approved w/Constraints
[9, 10]

Approved w/Constraints
[10, 11]

Approved w/Constraints
[11, 12]

DIVEST
[11, 12, 13, 14]

DIVEST
[11, 13, 14, 15]

6.1.x (CPT3)

Unapproved

Approved w/Constraints
[11, 12, 13, 14]

Approved w/Constraints
[11, 13, 14, 15]

Decision Constraints


[1]	Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines.

[2]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in accordance to VA 6500 and the Federal Information Security Management Act (FISMA). Per VA Handbook 6500, Federal Information Processing Standards (FIPS) 140-2 certified encryption must be used to protect and encrypt data in transit and at rest if Personally Identifiable Information/Protected Health Information/VA (PII/PHI/VA) sensitive information is involved or additional mitigating controls must be documented in an authorized System Security Plan (SSP). Additionally, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ) unless those specific uses and instances of this technology are authorized by the Enterprise Security Change Control Board (ESCCB), along with a Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA), which detail the security requirements for those users and systems that share information and resources outside of the VA production network.

[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 authorized, may continue to operate this technology. In the case of a project that has implemented, or been authorized 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 authorized or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

[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]	This product can be configured with Microsoft Access, which currently has TRM constraints for VA sensitive data and internet usage. If Microsoft Access is selected for use with this product, these factors must be considered. (Refer to Microsoft Access TRM entry for more details.)

[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]	Users must ensure that Microsoft .NET Framework is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

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

[11]	This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.

[12]	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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

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

[14]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

[15]	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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

Note:

At the time of writing, version 6.1.5 (CPT 3) is the most current version released.

Type	Name	Source	Description
Vendor Provided*	Conners Continuous Performance Test 3 (CPT-3)		The following FAQ’s are based on the questions about the Conners Continuous Performance Test 3 (CPT-3)/KCPT-2/CATA and have been compiled to provide our clients with answers to questions regarding security and privacy of these applications.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Name	Description
No components have been identified for this entry.


Collaboration and Electronic Workplace Productivity Software	Health Care
Health Care Health Services	Mental Health Services

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.
This technology may improve productivity for specific staff whose responsibilities include conducting neuropsychological assessments.
This is a well-documented technology.

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 involves the use Universal Serial Bus (USB) connections and proper security precautions must be taken when used.
The technology can potentially use the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
This technology is available as freeware. If commercial support is not purchased, the product will be without clearly defined support options which may result in suboptimal enterprise level support.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
There is no indication based on available vendor documentation that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
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.

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 (04/05/2023 at 00:57:25 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (03/30/2023)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (03/30/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework