<Past |
Future> |
8 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
8.0.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
9 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
9.0.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
10 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
10 Update 11 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
11 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
2016.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
2018.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
2021.x |
Approved w/Constraints [16, 18, 20, 21, 22, 23] |
Approved w/Constraints [16, 18, 20, 21, 22, 23] |
Approved w/Constraints [16, 18, 20, 21, 22, 23] |
DIVEST [18, 20, 22, 23, 24, 25, 26, 27] |
DIVEST [18, 22, 23, 24, 25, 26, 28, 29] |
DIVEST [18, 22, 23, 24, 25, 26, 28, 29] |
DIVEST [18, 22, 23, 24, 25, 26, 28, 29] |
Authorized w/ Constraints (DIVEST) [18, 22, 23, 24, 25, 26, 28, 29] |
Authorized w/ Constraints (DIVEST) [18, 22, 23, 24, 25, 26, 28, 29] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
2023.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [18, 20, 22, 23, 24, 25, 26, 27] |
Approved w/Constraints [18, 22, 23, 24, 25, 26, 28, 29] |
Approved w/Constraints [18, 22, 23, 24, 25, 26, 28, 29] |
Approved w/Constraints [18, 22, 23, 24, 25, 26, 28, 29] |
Authorized w/ Constraints [18, 22, 23, 24, 25, 26, 28, 29] |
Authorized w/ Constraints [18, 22, 23, 24, 25, 26, 28, 29] |
Authorized w/ Constraints (DIVEST) [18, 22, 23, 25, 26, 28, 29, 30] |
Authorized w/ Constraints (DIVEST) [18, 22, 23, 25, 26, 28, 29, 30] |
Authorized w/ Constraints (DIVEST) [18, 22, 23, 25, 26, 28, 29, 30] |
2025.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [18, 22, 23, 25, 26, 28, 29, 30] |
Authorized w/ Constraints [18, 22, 23, 25, 26, 28, 29, 30] |
Authorized w/ Constraints [18, 22, 23, 25, 26, 28, 29, 30] |
Note: |
At the time of writing, version 2025.0 is the most current version, released 02/26/2025. |
| | [16] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Users must ensure that Apache Hypertext Transfer Protocol (HTTP) Server, Microsoft .NET Framework and Microsoft Internet Information Services (IIS) 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:
- The FIPS 140-certified RSA BSAFE Crypto-J libraries are available only in the Enterprise Edition, and VA should only use such version. WebSphere Application Server integrates cryptographic modules including Java Secure Socket Extension (JSSE) and Java Cryptography Extension (JCE), which have undergone FIPS 140-2 certification. System owners should enable this option when running ColdFusion on WebSphere application server. Red Hat Enterprise Linux (RHEL) is FIPS 140-2 certified. It provides the FIPS-validated cryptographic modules when JBoss runs on top of it.
- Ensure the most recent updates, patches and hotfixes to the ColdFusion software are tested and installed as soon as they become available. As of this writing, the latest update for ColdFusion Enterprise Edition 2018 is Update 3. System owners and developers should refer to the ColdFusion Lockdown Guide, ColdFusion Developer Security Guide and Adobe ColdFusion Security Technical Implementation Guide (STIG) to gain useful knowledge in securing ColdFusion. In addition, an implementation of a VA-authorized web application firewall (WAF) can add another layer of security to the web server enclave.
| | [18] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. | | [20] | 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 with the VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [21] | 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 VA Handbook 6500. | | [22] | 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. | | [23] | 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. | | [24] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Users must ensure that PostgreSQL, Microsoft Structured Query Language (SQL) Server, Oracle Database, Apache Hypertext Transfer Protocol (HTTP) Server, Apache Tomcat, Microsoft .NET Framework, and Microsoft Internet Information Services (IIS) 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:
- The FIPS 140-certified RSA BSAFE Crypto-J libraries are available only in the Enterprise Edition, and VA should only use such version. WebSphere Application Server integrates cryptographic modules including Java Secure Socket Extension (JSSE) and Java Cryptography Extension (JCE), which have undergone FIPS 140-2 certification. System owners should enable this option when running ColdFusion on WebSphere application server. Red Hat Enterprise Linux (RHEL) is FIPS 140-2 certified. It provides the FIPS validated cryptographic modules when JBoss runs on top of it.
- Ensure the most recent updates, patches and hotfixes to the ColdFusion software are tested and installed as soon as they become available. As of this writing, the latest update for ColdFusion Enterprise Edition 2023 Update 2 (release date, 14 July 2023). System owners and developers should refer to the ColdFusion Lockdown Guide, ColdFusion Developer Security Guide and Adobe ColdFusion Security Technical Implementation Guide (STIG) to gain useful knowledge in securing ColdFusion. In addition, an implementation of a VA-authorized web application firewall (WAF) can add another layer of security to the web server enclave.
| | [25] | 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. | | [26] | 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. | | [27] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) 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 compliant encryption 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 compliant full disk encryption (FOE) must be implemented on the hard drive 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). | | [28] | 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. | | [29] | 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). | | [30] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Users must ensure that PostgreSQL, Microsoft Structured Query Language (SQL) Server, Oracle Database, Apache Hypertext Transfer Protocol (HTTP) Server, and Microsoft Internet Information Services (IIS) 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:
- The FIPS 140-certified RSA BSAFE Crypto-J libraries are available only in the
Enterprise Edition, and VA should only use such version. WebSphere
Application Server integrates cryptographic modules including Java Secure
Socket Extension (JSSE) and Java Cryptography Extension (JCE), which have
undergone FIPS 140-2 certification. System owners should enable this option
when running ColdFusion on WebSphere application server. Red Hat
Enterprise Linux (RHEL) is FIPS 140-2 certified. It provides the FIPS-validated
cryptographic modules when JBoss runs on top of it.
- Ensure the most recent updates, patches and hotfixes to the ColdFusion
software are tested and installed as soon as they become available. System
owners and developers should refer to the ColdFusion Lockdown Guide,
ColdFusion Developer Security Guide and Adobe ColdFusion Security
Technical Implementation Guide (STIG) to gain useful knowledge in securing
ColdFusion. In addition, an implementation of a VA-approved web application
firewall (WAF) can add another layer of security to the web server enclave.
System Administrators must also monitor active CVE entries.
|
|