| 22.x |
Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27] |
Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27] |
Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27] |
Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27] |
Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27] |
Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27] |
Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27] |
Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27] |
Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27] |
Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27] |
Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27] |
Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27] |
| | | | [1] | Veterans Affairs (VA) users must ensure VA sensitive data is protected properly in accordance with VA Handbook 6500 and the Federal Information Security Management Act (FISMA). Per VA Handbook 6500, Federal Information Processing Standards (FIPS) 140-2 certified encryption must be used to protect and encrypt data in transit and at rest if Personally Identifiable Information/Protected Health Information/VA (PII/PHI/VA) sensitive information is involved. If FIPS 140-2 certified encryption is not used, additional mitigating controls must be documented in an approved System Security Plan (SSP). In addition, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)), unless the specific uses and instances of the technology are approved by the Enterprise Security Change Control Board (ESCCB). All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. In cases where the technology is used for external connections, a full ESCCB review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513.
Cloud versions of this product are not permitted without a waiver from the Architecture and Engineering Review Board (AERB) and expressed authorization. Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. | | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [3] | Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. | | | [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. | | | [5] | This technology is downloaded with and can interact with H2 Database, which is an unapproved technology. Users must disable and remove H2 Database and use an approved database technology like Microsoft Structured Query Language (SQL) Server.
VA requires Federal Information Processing Standards (FIPS) 140-2 compliant cryptographic modules for encryption of data at rest and in transit. Ensure underlying infrastructure and application access are configured to provide FIPS 140-2 encryption for web access supporting Aspect Prophecy.
The H2 database is used by Prophecy internally, with no user access.
Adherence to VA guidelines on approved web browsers when using this product is required. If there is a business need for alternative browsers, such as Mozilla Firefox, or nonstandard versions of Internet Explorer or Google Chrome a STAT waiver must be granted to the project team or organization that wishes to use the alternative browser.
It is advised that a custom usage policy be created at the Aspect Prophecy entry point and users required to accept it before they are allowed to access the site. It should be stated explicitly that discussing and posting of VA sensitive information is prohibited.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [6] | 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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [7] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [8] | This technology is downloaded with and can interact with H2 Database, which is an unapproved technology. Users must disable and remove H2 Database and use an approved database technology like Microsoft Structured Query Language (SQL) Server.
VA requires Federal Information Processing Standards (FIPS) 140-2 compliant cryptographic modules for encryption of data at rest and in transit. Ensure underlying infrastructure and application access are configured to provide FIPS 140-2 encryption for web access supporting Aspect Prophecy.
The H2 database is used by Prophecy internally, with no user access.
Adherence to VA guidelines on approved web browsers when using this product is required. If there is a business need for alternative browsers, such as Mozilla Firefox, or nonstandard versions of Internet Explorer or Google Chrome a STAT waiver must be granted to the project team or organization that wishes to use the alternative browser.
It is advised that a custom usage policy be created at the Aspect Prophecy entry point and users required to accept it before they are allowed to access the site. It should be stated explicitly that discussing and posting of VA sensitive information is prohibited.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [9] | 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 Security Officer (ISO) 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). | | | [10] | This technology is downloaded with and can interact with H2 Database, which is an unapproved technology. Users must disable and remove H2 Database and use an approved database technology like Microsoft Structured Query Language (SQL) Server.
VA requires Federal Information Processing Standards (FIPS) 140-2 compliant cryptographic modules for encryption of data at rest and in transit. Ensure underlying infrastructure and application access are configured to provide FIPS 140-2 encryption for web access supporting Aspect Prophecy.
The H2 database is used by Prophecy internally, with no user access.
Adherence to VA guidelines on approved web browsers when using this product is required. If there is a business need for alternative browsers, such as Mozilla Firefox, or nonstandard versions of Internet Explorer or Google Chrome a STAT waiver must be granted to the project team or organization that wishes to use the alternative browser.
It is advised that a custom usage policy be created at the Aspect Prophecy entry point and users required to accept it before they are allowed to access the site. It should be stated explicitly that discussing and posting of VA sensitive information is prohibited.
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 is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology must use the latest version of Java Development Kit (JDK) - Oracle. | | | [11] | 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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [12] | This technology is downloaded with and can interact with H2 Database, which is an unapproved technology. Users must disable and remove H2 Database and use an approved database technology like Microsoft Structured Query Language (SQL) Server.
VA requires Federal Information Processing Standards (FIPS) 140-2 compliant cryptographic modules for encryption of data at rest and in transit. Ensure underlying infrastructure and application access are configured to provide FIPS 140-2 encryption for web access supporting Aspect Prophecy.
The H2 database is used by Prophecy internally, with no user access.
Adherence to VA guidelines on approved web browsers when using this product is required. If there is a business need for alternative browsers, such as Mozilla Firefox, or nonstandard versions of Internet Explorer or Google Chrome a STAT waiver must be granted to the project team or organization that wishes to use the alternative browser.
It is advised that a custom usage policy be created at the Aspect Prophecy entry point and users required to accept it before they are allowed to access the site. It should be stated explicitly that discussing and posting of VA sensitive information is prohibited.
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-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology must use the latest version of Java Development Kit (JDK) - Oracle. | | | [13] | 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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [14] | 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 Security Officer (ISO) 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). | | | [15] | 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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [16] | 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. | | | [17] | 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 Project Special Forces (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [18] | 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). | | | [19] | This technology is downloaded with and can interact with H2 Database, which is an unapproved technology. Users must disable and remove H2 Database and use an approved database technology like Microsoft Structured Query Language (SQL) Server.
VA requires Federal Information Processing Standards (FIPS) 140-2 compliant cryptographic modules for encryption of data at rest and in transit. Ensure underlying infrastructure and application access are configured to provide FIPS 140-2 encryption for web access supporting Aspect Prophecy.
The H2 database is used by Prophecy internally, with no user access.
Adherence to VA guidelines on approved web browsers when using this product is required. If there is a business need for alternative browsers, such as Mozilla Firefox, or nonstandard versions of Internet Explorer or Google Chrome a STAT waiver must be granted to the project team or organization that wishes to use the alternative browser.
It is advised that a custom usage policy be created at the Aspect Prophecy entry point and users required to accept it before they are allowed to access the site. It should be stated explicitly that discussing and posting of VA sensitive information is prohibited.
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-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. | | | [20] | 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-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize the H2 Database Engine, as it is unapproved for use on the TRM.
This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- VA requires Federal Information Processing Standards (FIPS) 140-2 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 Aspect 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 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 approved 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.
| | | [21] | Users should check with their supervisor, Information Security Office (ISO) 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 approved and the user should take the proper steps to decline those installations. | | | [22] | 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. | | | [23] | 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 approved and the user should take the proper steps to decline those installations. | | | [24] | 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). | | | [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). |
|
