| 25.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
| | | | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in on-premises in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations.
This technology can potentially utilize publicly available artificial intelligence (AI) services.
Per the Initial Product Review, users must abide by the following constraints:
- WatsonX.ai will require a 3rd party FIPS 140-2 (or its successor) certified solution
for any data containing PHI/PII or VA sensitive information.
- Due to potential information security risks, SaaS/PaaS solutions must complete
the Business Integration and Outcomes Service (BIOS) process where a
collaborative effort between Demand Management (DM), Enterprise Program
Management Office Information Assurance (EPMO IA), Digital Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology
Officer (CTO), and stakeholders determines the SaaS/PaaS category during the
Discovery Phase. All SaaS and Non-AWS or Azure (VAEC) PaaS assets are routed
to EPMO IA for Analysis and Approval to Operate (ATO) with technical
oversight, acquisition, production, and sustainment provided by DTC.
- 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 approved 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.
- System owners should use the latest version of this product and monitor both
the CVE Details and NIST National Vulnerability Database websites for any new
security vulnerabilities.
- This product should be used with a VA approved container platform that has a
developed and approved baseline configuration with specific hardening
guidance regarding the secure implementation of WatsonX.ai. Please reference
the TRM for the approved solution and the Baseline Configuration
Management website for more information.
- Open architecture software often relies on open-source software and can
inherit its vulnerabilities. Administrators should manage third-party risks by
continuously monitoring for vulnerabilities in external components.
- OMB Memorandum M-22-18,” Enhancing the Security of the Software Supply
Chain through Secure Software Development Practices,” and OMB
Memorandum M-23-16, “Update to Memorandum M-22-18,” limit agencies’
ability to use software that is not developed using secure practices. The
attestation form will allow software producers to confirm that they follow those
practices.
| | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | | [3] | 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. | | | [4] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | | [5] | 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). | | | [6] | 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. |
|