| 7.x.x |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 13, 14] |
Approved w/Constraints
[3, 6, 9, 10, 11, 13, 14] |
Approved w/Constraints
[3, 6, 9, 10, 11, 13, 14] |
Approved w/Constraints
[3, 6, 10, 11, 13, 15, 16, 17] |
Approved w/Constraints
[3, 6, 10, 11, 13, 15, 16, 17] |
Approved w/Constraints
[3, 6, 10, 11, 13, 15, 16, 17] |
| | | | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
The following constraints were listed in the product`s Initial Product Review (IPR) performed by the Solution Delivery Security Engineering team and must be followed:
Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. 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).
As a content-management system that allows user-generated content to be posted on the web, precautions must be taken within the application to prevent cross-site scripting attacks.
Confluence does not directly support Transport Layer Security (TLS). Administrators should set up TLS at the level of the Java web application server, or the Hypertext Transfer Protocol (HTTP) proxy in front of the Confluence application.
Administrators must avoid installing any third party applications within the Confluence server environment.
Confluence provides a list of known security vulnerabilities. Administrators must avoid using anything below the latest release, 6.10.1.
Compensating controls must be implemented to ensure the data at rest and in transit is utilizing Federal Information Processing Standard (FIPS) 140-2 validated encryption if applicable.
Servers hosting the Confluence environment are required, per VA security policy, to install VA approved antivirus software and conduct periodic scans of the information system. The information system should be configured to exclude any directories and files only if they are severely impacting performance.
VA Handbook 6500 SI-3 Malicious Code Protection requires periodic scans of the information system and real-time scans of files from external sources at endpoint and/or network entry/exit points as the files are downloaded, opened, or executed in accordance with VA security policy and takes identified action in response to malicious code detection.
VA Secure Configuration Baselines for approved VA server operating systems require the installation of McAfee Anti-Virus Software, McAfee ePolicy Orchestrator (ePO) agent, and McAfee Host Intrusion Prevention (HIPS). | | | [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 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 ISO can provide assistance in reviewing the NIST vulnerabilities. | | | [4] | 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). | | | [5] | 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). | | | [6] | 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. | | | [7] | 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, Microsoft Internet Explorer (IE), 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 Runtime Environment (JRE) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) processwhere 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.
- Other solutions should be considered as Confluence is in a Divest status on the One VA-TRM Q4 2021. Any use of Confluence should be considered short term and other solutions should be considered.
- As a content-management system that allows user-generated content to be posted on the web, precautions must be taken within the application to prevent cross-site scripting attacks.
- Confluence does not directly support TLS. Administrators should set up TLS at the level of the Java web application server, or the HTTP proxy in front of the Confluence application.
- Administrators should avoid installing any 3rd party applications within the Confluence server environment.
- Confluence provides a list of known security vulnerabilities. Administrators should avoid using anything below the latest release, 7.3.1.
- Compensating controls should be implemented to ensure the data at rest and in transit is utilizing FIPS 140-2 validated encryption if applicable.
- Servers hosting the Confluence environment are required, per VA security policy, to install VA approved antivirus software and conduct periodic scans of the information system. The information system should be configured to exclude any directories and files only if they are severely impacting performance.
| | | [8] | 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). | | | [9] | 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, Microsoft Internet Explorer (IE), 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 Environment.
Per the Initial Product Review, users must abide by the following constraints:
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) processwhere 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.
- Other solutions should be considered as Confluence is in a Divest status on the One VA-TRM Q4 2021. Any use of Confluence should be considered short term and other solutions should be considered.
- As a content-management system that allows user-generated content to be posted on the web, precautions must be taken within the application to prevent cross-site scripting attacks.
- Confluence does not directly support TLS. Administrators should set up TLS at the level of the Java web application server, or the HTTP proxy in front of the Confluence application.
- Administrators should avoid installing any 3rd party applications within the Confluence server environment.
- Confluence provides a list of known security vulnerabilities. Administrators should avoid using anything below the latest release, 7.3.1.
- Compensating controls should be implemented to ensure the data at rest and in transit is utilizing FIPS 140-2 validated encryption if applicable.
- Servers hosting the Confluence environment are required, per VA security policy, to install VA approved antivirus software and conduct periodic scans of the information system. The information system should be configured to exclude any directories and files only if they are severely impacting performance.
| | | [10] | 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. | | | [11] | 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). | | | [12] | 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). | | | [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. | | | [14] | 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). | | | [15] | 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, Google Chrome, Firefox, 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 Runtime Environment (JRE) - Oracle.
This technology must use the latest TRM-approved version of Java Environment.
Per the [Initial Product Review/Security Assessment Review], users must abide by the following constraints:
- 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.
- As a content-management system that allows user-generated content to be posted on the web, precautions must be taken within the application to prevent cross-site scripting attacks.
- Confluence does not directly support TLS. Administrators should set up TLS at the level of the Java web application server, or the HTTP proxy in front of the Confluence application.
- Administrators should avoid installing any 3rd party applications within the Confluence server environment.
- Confluence provides a list of known security vulnerabilities. Administrators should avoid using anything below release 7.3.1.
- Compensating controls should be implemented to ensure the data at rest and in transit is utilizing FIPS 140-2 certified encryption if applicable.
- Servers hosting the Confluence environment are required, per VA security policy, to install VA approved antivirus software and conduct periodic scans of the information system. The information system should be configured to exclude any directories and files only if they are severely impacting performance.
| | | [16] | 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). | | | [17] | If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL 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 MySQL Database – Commercial Edition TRM entry for more details. |
|
