|
<Past |
Future> |
| 3.x |
Approved w/Constraints [4, 10, 14, 15, 16] |
DIVEST [4, 14, 15, 16, 17, 18] |
DIVEST [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 18, 19] |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required[a] |
| 22.x |
Unapproved |
DIVEST [4, 14, 15, 16, 17, 18] |
DIVEST [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 18, 19] |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required[a] |
| 23.x |
Unapproved |
DIVEST [4, 14, 15, 16, 17, 18] |
DIVEST [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 18, 19] |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required[a] |
| 24.x |
Unapproved |
Approved w/Constraints [4, 14, 15, 16, 17, 18] |
Approved w/Constraints [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints [4, 14, 15, 16, 17, 18] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 18, 19] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 18, 19] |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required[a] |
| 25.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 18, 19] |
Authorized w/ Constraints (DIVEST) [4, 14, 15, 16, 18, 19] |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required[a] |
| Note: |
At the time of writing, version 25.9 is the most current version, released 09/15/2025. |
| | | | [4] | 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. | | | [10] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Firefox, Google Chrome, and Microsoft Internet Explorer (IE) are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must Divest the use of Internet Explorer with this technology. Other authorized internet browsers are available. See Category Tab for details. | | | [14] | Users should check with their supervisor, Information System Security Officer (ISSO) 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 authorized and the user should take the proper steps to decline those installations. | | | [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. | | | [16] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [17] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Google Chrome is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Cogito Companion will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Protected Health Information (PHI)/PII or VA sensitive information.
- Due to potential information security risks, cloud-based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised.
- The use of AI is increasing, and guidance is still developing. Users must check the most recent VA guidance before using AI technologies and solutions. Consideration should be given to the source of any initial data for the AI tool, if any VA data will be collected and ingested into the data set, where that data will be stored, and what rights the VA has to that data. No web-based, publicly available generative AI service has been authorized for use with VA-sensitive data. Examples of these include OpenAI’s ChatGPT and GPT4, Google’s Bard, Anthropic’ s Claude, and Microsoft’s new Bing. VA follows existing federal requirements and processes to ensure VA data is protected. When users enter information into an unapproved web-based tool, VA loses control of the data.
| | | [18] | 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. | | | [19] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Google Chrome, Microsoft Edge, and Firefox are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Cogito Companion will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Protected Health Information (PHI)/PII or VA sensitive information.
- Due to potential information security risks, cloud-based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised.
- The use of AI is increasing, and guidance is still developing. Users must check the most recent VA guidance before using AI technologies and solutions. Consideration should be given to the source of any initial data for the AI tool, if any VA data will be collected and ingested into the data set, where that data will be stored, and what rights the VA has to that data. No web-based, publicly available generative AI service has been authorized for use with VA-sensitive data. Examples of these include OpenAI’s ChatGPT and GPT4, Google’s Bard, Anthropic’ s Claude, and Microsoft’s new Bing. VA follows existing federal requirements and processes to ensure VA data is protected. When users enter information into an unapproved web-based tool, VA loses control of the data.
|
|