Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Mindjet MindManager

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:	Mindjet MindManager is a team collaboration software. This software allows users to organize and visualize content for project planning and collaboration purposes. This software provides a unified dashboard where users can view visualized diagrams and project content. MindManager allows users to quickly capture and transform ideas into clear, customizable mind maps, flowcharts, and timelines to efficiently organize their teams or businesses. This entry comes in three different editions: MindManager for Windows, MindManager for Mac, and MindManager Enterprise Edition. This entry does not cover MindManager Enterprise. It only covers MindManager for Windows and MindManager for Mac. 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 been assessed by the Section 508 Office and found non-conformant. 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. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.1
Decision Date:	01/09/2023 at 19:31:35 UTC
Introduced By:	TRM Request
Vendor Name:	Mindjet

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
Mac V9	06/23/2011
Mac V10	09/20/2012
Mac V11	02/19/2018
Mac V12	11/11/2020
Mac V13	11/13/2020
Mac V22 (2022)	07/27/2022
Win V10 (2012)	09/22/2011
Win V11	09/20/2012
Win V15	09/09/2014
Win V16 (2016)	10/15/2015
Win V17 (2017)	10/01/2016
Win V18 (2018)	10/01/2017
Win V19 (2019)	09/26/2018
Win V20 (2020)	01/30/2020
Win V21 (2021)	03/11/2021
Win V22 (2022)	07/19/2022

Current Decision Matrix (12/27/2022)

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

CY2021

CY2022

CY2023

Future>

Release

Mac V9

Unapproved

Mac V10

Unapproved

Mac V11

Unapproved

Mac V12

Approved w/Constraints
[5, 9, 16, 18, 19, 20]

Divest
[9, 16, 18, 20, 21]

Divest
[9, 16, 18, 21, 22]

Unapproved

Mac V13

Unapproved

Approved w/Constraints
[9, 16, 18, 20, 21]

Approved w/Constraints
[9, 16, 18, 21, 22]

Approved w/Constraints
[9, 16, 18, 21, 23]

Divest
[23, 24, 25, 26, 27]

Divest
[23, 24, 26, 27, 28]

Mac V22 (2022)

Unapproved

Approved w/Constraints
[23, 24, 25, 26, 27]

Approved w/Constraints
[23, 24, 26, 27, 28]

Win V10 (2012)

Prohibited

Win V11

Unapproved

Win V15

Unapproved

Win V16 (2016)

Unapproved

Win V17 (2017)

Unapproved

Win V18 (2018)

Unapproved

Win V19 (2019)

Unapproved

Win V20 (2020)

Approved w/Constraints
[5, 9, 16, 18, 19, 20]

Divest
[9, 16, 18, 20, 21]

Divest
[9, 16, 18, 21, 22]

Unapproved

Win V21 (2021)

Unapproved

Approved w/Constraints
[9, 16, 18, 20, 21]

Approved w/Constraints
[9, 16, 18, 21, 22]

Approved w/Constraints
[9, 16, 18, 21, 23]

Divest
[23, 24, 25, 26, 27]

Divest
[23, 24, 26, 27, 28]

Win V22 (2022)

Unapproved

Approved w/Constraints
[23, 24, 25, 26, 27]

Approved w/Constraints
[23, 24, 26, 27, 28]

Decision Constraints


[1]	Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities. Certain versions of MindManager are prohibited and are not to be used under any circumstances, please refer to the forecast tab for specific information. Additionally, if PII/PHI/VA sensitive information is involved, FIPS 140-2 certified encryption must be used to encrypt data in transit and the technology must be implemented within the VA production network (not in a DMZ) or additional mitigating controls must be documented in an approved System Security Plan (SSP).

[2]	Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities. Important Note: Certain versions of MindManager are prohibited and are not to be used under any circumstances, please refer to the forecast tab for specific information. Additionally, if PII/PHI/VA sensitive information is involved, FIPS 140-2 certified encryption must be used to encrypt data in transit and the technology must be implemented within the VA production network (not in a DMZ) or additional mitigating controls must be documented in an approved System Security Plan (SSP).

[3]	As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

[4]	Certain versions of MindManager are prohibited and are not to be used under any circumstances, please refer to the forecast tab for specific information. New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a Systems Engineering Design Review (SEDR) (contact VA e-mail: VA IT ESE SEDR SEG) prior to implementation to ensure proper compliance to VA network design and usage requirements.

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

[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]	Certain versions of MindManager are prohibited and are not to be used under any circumstances, please refer to the Decision tab for specific information. New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a Systems Engineering Design Review (SEDR) prior to implementation to ensure proper compliance to VA network design and usage requirements.

[8]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

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

[10]	Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. 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).

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

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

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

[14]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Per the Initial Product Review, user must abide by the following constraints: If VA sensitive information is stored or transmitted, FIPS 140-2 validated cryptographic modules are required to secure the data. Blowfish encryption is not FIPS 140-2 validated. VA Handbook 6500: SC-13 System and Communications Protection requires that encryption technologies meet FIPS 140-2 cryptography standards for hardware, software, and firmware components. Passwords must be protected using FIPS 140-2 validated encryption. In the event MindManager is considered for use, system owners must ensure that the current version is used. Due to potential information security risks, Software as a Service/Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR), 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 determine 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. Functions to communicate with unapproved cloud storage and collaboration solutions must be disabled during installation of MindManager.

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

[16]	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: If VA sensitive information is stored or transmitted, FIPS 140-2 validated cryptographic modules are required to secure the data. Blowfish encryption is not FIPS 140-2 validated. VA Handbook 6500: SC-13 System and Communications Protection requires that encryption technologies meet FIPS 140-2 cryptography standards for hardware, software, and firmware components. Passwords must be protected using FIPS 140-2 validated encryption. In the event MindManager is considered for use, system owners must ensure that the current version is used. Due to potential information security risks, Software as a Service/Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR), 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 determine 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. Functions to communicate with unapproved cloud storage and collaboration solutions must be disabled during installation of MindManager. Users must ensure that Microsoft .NET Framework is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[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 (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

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

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

[20]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

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

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

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

[24]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Per the Initial Product Review (IPR), users must abide by the following constraints: (MindManager will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information. Functions to communicate with unapproved cloud storage and collaboration solutions must be disabled during installation of MindManager.

[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 VA Handbook 6500.

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

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

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

Note:

At the time of writing, version WIN V22 (2022) is the most current version, released 07/19/2022.
At the time of writing, version MAC V22 (2022) is the most current version, released 07/27/2022.
MindManager Mac 14 is now called MindManager Mac 22 to match version numbers across all MindManager products.

The following reference(s) are associated with this entry:
Type	Name	Description
Vendor Provided*	MindManager Support	This link provides the support page with all release versions for MindManager.
Vendor Provided*	MindManager Download Library	This link provides release notes and downloads for all release versions of MindManager.
Vendor Provided*	Product Information	This link provides basic information about this software.
*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
No components have been identified for this entry.


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

- The information contained on this page is accurate as of the Decision Date (01/09/2023 at 19:31:35 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 (12/27/2022)

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 (12/27/2022)

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