Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Confluence

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Confluence is a wiki solution that allows project members to collaborate on writing and sharing content. Content includes documents, images, diagrams, activity streams and web service integration. Content is published and can be read through a web browser and edited by users with appropriate write permissions. This allows updates to be visible to other members immediately. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.7
Decision Date:	07/01/2024 at 14:13:58 UTC
Introduced By:	TRM Request
Vendor Name:	Atlassian Software Systems

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
4.3	09/04/2012	09/04/2014	09/04/2014
5.4	11/28/2013	11/28/2015	11/28/2015
5.5	04/29/2014	04/29/2016	04/29/2016
5.6	09/03/2014	09/03/2016	09/03/2016
5.7	01/28/2015	01/27/2027	01/27/2027
5.8	06/02/2015	06/02/2017	06/02/2017
5.9	11/24/2015
5.10	08/06/2016
6.0	11/02/2016
6.1	03/20/2017
6.2	05/15/2017
6.3	07/12/2017
6.4	09/06/2017
6.5	11/01/2017
6.6	12/12/2017
6.10.1	07/17/2018
6.15.x	03/14/2019
7.x.x	09/10/2019
8.1.x	03/01/2023
8.5.x	08/22/2023
8.6.x	10/01/2023
8.7.x	12/06/2023
8.8.x	02/08/2024
8.9.x	06/11/2024

Current Decision Matrix (06/25/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2024

CY2025

CY2026

Future>

Release

4.3

Unapproved

5.4

Unapproved

5.5

Unapproved

5.6

Unapproved

5.9

Unapproved

6.0

Unapproved

6.1

Unapproved

6.2

Unapproved

6.3

Unapproved

6.4

Unapproved

6.5

Unapproved

6.6

Unapproved

6.10.1

Unapproved

6.15.x

Unapproved

7.x.x

Divest
[13, 17, 20, 21, 23, 24, 25, 26, 27]

Unapproved

8.1.x

Divest
[13, 17, 20, 21, 23, 24, 25, 26, 27]

Divest
[13, 17, 20, 21, 23, 24, 25, 26, 27, 28]

Unapproved

8.5.x

Approved w/Constraints
[13, 17, 20, 21, 23, 24, 25, 26, 27]

Approved w/Constraints
[13, 17, 20, 21, 23, 24, 25, 26, 27, 28]

8.6.x

Divest
[13, 17, 20, 21, 23, 24, 25, 26, 27]

Divest
[13, 17, 20, 21, 23, 24, 25, 26, 27, 28]

Unapproved

8.7.x

Divest
[13, 17, 20, 21, 23, 24, 25, 26, 27]

Divest
[13, 17, 20, 21, 23, 24, 25, 26, 27, 28]

Unapproved

8.8.x

Approved w/Constraints
[13, 17, 20, 21, 23, 24, 25, 26, 27]

Divest
[13, 17, 20, 21, 23, 24, 25, 26, 27, 28]

Unapproved

8.9.x

Unapproved

Approved w/Constraints
[13, 17, 20, 21, 23, 24, 25, 26, 27, 28]

Decision Constraints


[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.

[18]	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, MySQL, Apache Tomcat, 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) 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 September 10, 2021 For Internal VA Use Only Page 4 of 7 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.

[19]	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.

[20]	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.

[21]	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.

[22]	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).

[23]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that PostgreSql, Firefox, Google Chrome, Microsoft Edge, Microsoft Structured Query Language (SQL) Server, Apache Tomcat, 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) 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. 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. Administrators should monitor the NIST National Vulnerability Database website. Avoid using any versions below release 8.5.1 and update to 8.5.2 or later. 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.

[24]	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.

[25]	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.

[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]	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.

Note:

At the time of writing, version 8.9.3 is the most current version, released 06/11/2024.

Version 8.5.x is a Long Term Support (LTS) version.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Atlassian Companion	The Atlassian Companion application enables users to edit Confluence files in their preferred desktop application, then save the file back to Confluence automatically.


Collaboration and Electronic Workplace Collaboration Software	Content Management
Collaboration and Electronic Workplace Collaboration Software	Real-Time and Team Collaboration

- The information contained on this page is accurate as of the Decision Date (07/01/2024 at 14:13:58 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (06/25/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (06/25/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES