2.6 |
Unapproved |
Unapproved |
Unapproved |
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] | Users must ensure that Firefox, Google Chrome, and Microsoft Edge are implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Security Assessment Review, users must abide by the following constraints:
- An MOU-ISA was completed with the OIS ECSD team, and they stated an ATO is not required for the vendors cloud solution as no
VA owned data is being physically stored. The connection is documented in the Enterprise Call Session Control (ECSC) Assessing
ATO.
- OSS may be used if there is adequate maintenance and support. As a condition of certification, Sponsor/Software admin personnel shall
maintain and monitor the distribution of all OSS. The software shall be physically stored in Sponsor/Software admin software library for
quality control.
- System owners should use the latest version of the product and monitor both the CVE Details and NIST NVD websites for any new
security vulnerabilities.
- 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.
| | [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] | 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. | | [4] | 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). | | [5] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [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. |
|