|
<Past |
Future> |
| 2.x (Win) |
Approved w/Constraints
[14, 15, 16, 17, 18, 19] |
Approved w/Constraints
[14, 15, 16, 17, 18, 19] |
Approved w/Constraints
[14, 15, 16, 17, 18, 19] |
Approved w/Constraints
[14, 15, 17, 18, 19, 20] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[17, 18, 19, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 19, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 19, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 19, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 19, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 19, 20, 21, 22, 23] |
| 2.x (macOS) |
Approved w/Constraints
[14, 15, 16, 17, 18, 19] |
Approved w/Constraints
[14, 15, 16, 17, 18, 19] |
Approved w/Constraints
[14, 15, 16, 17, 18, 19] |
Approved w/Constraints
[14, 15, 17, 18, 19, 20] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[17, 18, 19, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 19, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 19, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 19, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 19, 20, 21, 22, 23] |
Approved w/Constraints
[17, 18, 19, 20, 21, 22, 23] |
| | | | [1] | Users must not use the Windows version of this technology as it must be downloaded through the Windows App store.
Per the Initial Product Review, users must abide by the following constraints:
A data loss prevention (DLP) strategy must be employed as the security controls offered by cloud providers vary widely.
Trello`s desktop must be administered only by the Desktop and Device Engineering team and the mobile version of the client must be managed by the Mobile Technology and Endpoint Security Engineering team.
Trello must only be installed on vendor supported or recommended web browsers.
The VA must only consider solutions with similar functionality if the current approved solutions do not meet all of VA`s needs or requirements.
Due to potential information security risks, Software as a Service (SaaS) 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), ChiefTechnology Officer (CTO), and stakeholders determines the SaaS/Platform as a Service (PaaS) category during the Discovery Phase. All SaaS and Non-Amazon Web Services (AWS)/Azure (VAEC) PaaS assets are routed to EPMOIA for Analysis and Approval to Operate (ATO) with technical oversight,acquisition, production, and sustainment provided by PSF.
VA must develop a policy that users must not use, disclose, transmit orotherwise process any PII/PHI as defined in Health Insurance Portability andAccountability Act (HIPAA) through Trello. | | | [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] | 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. | | | [4] | 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. | | | [5] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [6] | 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). | | | [7] | Users must ensure that Firefox, Google Chrome, Microsoft Internet Explorer (IE), and Safari are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Per the Initial Product Review, users must abide by the following constraints:
- A data loss prevention (DLP) strategy must be employed as the security controls offered by cloud providers vary widely.
- Trello`s desktop must be administered only by the Desktop and Device Engineering team and the mobile version of the client must be managed by the Mobile Technology and Endpoint Security Engineering team.
- Trello must only be installed on vendor supported or recommended web browsers.
- The VA must only consider solutions with similar functionality if the current approved solutions do not meet all of VA`s needs or requirements.
- Due to potential information security risks, Software as a Service (SaaS) 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), ChiefTechnology Officer (CTO), and stakeholders determines the SaaS/Platform as a Service (PaaS) category during the Discovery Phase. All SaaS and Non-Amazon Web Services (AWS)/Azure (VAEC) PaaS assets are routed to EPMOIA for Analysis and Approval to Operate (ATO) with technical oversight,acquisition, production, and sustainment provided by PSF.
- VA must develop a policy that users must not use, disclose, transmit orotherwise process any PII/PHI as defined in Health Insurance Portability andAccountability Act (HIPAA) through Trello.
| | | [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] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517
and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | | [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] | 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 should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517
and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | | [13] | 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). | | | [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 VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [15] | Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Per the Initial Product Review, users must abide by the following constraints:
- A data loss prevention (DLP) strategy should be employed as the security controls offered by cloud providers vary widely.
- Trello`s desktop must be administered only by the Desktop and Device Engineering team and the mobile version of the client must be managed by the Mobile Technology and Endpoint Security Engineering team.
- The VA should only consider solutions with similar functionality if the current approved solutions do not meet all of VA’s needs or requirements.
- 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.
- VA must develop a policy that users must not use, disclose, transmit or otherwise process any PII/PHI as defined in Health Insurance Portability and Accountability Act (HIPAA) through Trello.
| | | [16] | 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. | | | [17] | 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. | | | [18] | 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. | | | [19] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. 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 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517
and VA Directive 6513. The local ISSO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | | [20] | 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. | | | [21] | 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). | | | [22] | Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Users must ensure that Firefox, Google Chrome, and Microsoft Edge are implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users should not use this application through the Windows platform as it is downloaded through the Windows Application Store.
Per the Initial Product Review, users must abide by the following constraints:
- A data loss prevention (DLP) strategy should be employed as the security controls offered by cloud providers vary widely.
- Trello`s desktop must be administered only by the Desktop and Device Engineering team and the mobile version of the client must be managed by the Mobile Technology and Endpoint Security Engineering team.
- The VA should only consider solutions with similar functionality if the current approved solutions do not meet all of VA’s needs or requirements.
- 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.
- VA must develop a policy that users must not use, disclose, transmit or otherwise process any PII/PHI as defined in Health Insurance Portability and Accountability Act (HIPAA) through Trello.
| | | [23] | 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. |
|
| Note: |
At the time of writing, version 2.14.7 is the most current version, released 04/23/2024 for MacOS. Version 2.12.3 is the most current version, released 07/15/2022 for Windows. |
