| 2025.x |
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] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
| | | | [1] | 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.
Per the Security Assessment Review, users must abide by the following constraints:
- A vulnerability exists because Positron 2025.x allows for the download of extensions from the Open VSX marketplace. To mitigate, extensions must be disabled, and only private, vetted extensions shall be used. It is recommended that Positron Pro be considered instead as it allows for extension whitelisting restricting users to only agency-approved extensions.
- A vulnerability exists because Positron provides AI capabilities through the Positron Assistant. To mitigate, Positron Assistant may only be used with VA approved Generative AI Pilots. No web-based, publicly available generative AI service has been approved for use with VA-sensitive data.
- A vulnerability exists because Positron 2025.x includes/utilizes commercial cloud computing services. To mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated.
- A vulnerability exists because Positron supports automatic updates by default. System Administrators shall set Update:mode within the program
settings to “none” to disable automatic updates.
| | | [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. |
|