|
<Past |
Future> |
| 14 |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 14.5 |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 16.x.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 18.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 19.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 20.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 22.x |
Authorized w/ Constraints [4, 13, 24, 25, 26, 27, 28, 29] |
Authorized w/ Constraints [4, 13, 24, 25, 26, 27, 28, 29] |
Authorized w/ Constraints [4, 13, 24, 25, 26, 27, 28, 29] |
Authorized w/ Constraints (DIVEST) [4, 13, 24, 25, 26, 27, 29, 30] |
Unauthorized, Conditions Required[b] [4, 13, 24, 25, 26, 27, 29, 30] |
Unauthorized, Conditions Required[b] [4, 13, 24, 25, 26, 27, 29, 30] |
Unauthorized, Conditions Required[b] [4, 13, 24, 25, 26, 27, 29, 30] |
Unauthorized, Conditions Required[b] [4, 13, 24, 25, 26, 27, 29, 30] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 24.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [4, 13, 24, 25, 26, 27, 29, 30] |
Authorized w/ Constraints [4, 13, 24, 25, 26, 27, 29, 30] |
Authorized w/ Constraints [4, 13, 24, 25, 26, 27, 29, 30] |
Authorized w/ Constraints [4, 13, 24, 25, 26, 27, 29, 30] |
Authorized w/ Constraints [4, 13, 24, 25, 26, 27, 29, 30] |
Authorized w/ Constraints [4, 13, 24, 25, 26, 27, 29, 30] |
Authorized w/ Constraints [4, 13, 24, 25, 26, 27, 29, 30] |
Authorized w/ Constraints [4, 13, 24, 25, 26, 27, 29, 30] |
Authorized w/ Constraints [4, 13, 24, 25, 26, 27, 29, 30] |
| Note: |
At the time of writing, version 24.1 is the most current version, released 08/25/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. | | | [13] | This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details. | | | [24] | 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. | | | [25] | 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. | | | [26] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 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 or its successor 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 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device 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 System Security Officer (ISSO) 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). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. | | | [27] | 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). | | | [28] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft Structured Query Language (SQL) Server, PostgreSQL, and Oracle Database are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize H2 Database Engine, as it, at the time of writing, requires a POA&M.
This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- The H2 database is used by Prophecy internally, with no user access.
- It is advised that a custom usage policy be created at the Aspect Prophecy entry point and users required to accept it before they can access the site. It should be stated explicitly that discussing and posting of VA sensitive information is prohibited.
- System owners should review the One-VA TRM entries for the authorized versions of databases and Oracle Java SDK.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), 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/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 PSF.
| | | [29] | 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. | | | [30] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft Structured Query Language (SQL) Server, PostgreSQL, and Oracle Database are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize H2 Database Engine, as it, at the time of writing, requires a POA&M.
This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle.
Users must Divest the use of Nuance Vocalizer with this technology.
Per the Initial Product Review, users must abide by the following constraints:
- VA requires Federal Information Processing Standards (FIPS) 140-2 (or its
successor) certified cryptographic modules for encryption of data at rest and
in transit. Ensure underlying infrastructure and application access are
configured to provide FIPS 140-2 certified encryption for web access
supporting Alvaria Prophecy.
- The H2 database is used by Prophecy internally, with no user access.
- It is advised that a custom usage policy be created at the Alvaria Prophecy
entry point and users are required to accept it before they can access the site.
It should be stated explicitly that discussing and posting of VA sensitive
information is prohibited.
- System owners should review the One-VA TRM entries for the authorized
versions of databases and Oracle Java SDK.
- 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.
- 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.
VA Supply Chain Risk Management (SR) Policy and VA Handbook 6500.6,
Contract Security, Appendix C The contractor (including producers and
resellers) shall comply with Office of Management and Budget (OMB) M-22-
18 and M-23-16 when using third-party software on VA information systems
or otherwise affecting the VA information. This includes new software
purchases and software renewals for software developed or modified by
major version change after the issuance date of M-22-18 (September 14,
2022).
|
|