MyEclipse

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:	MyEclipse is a proprietary release of Eclipse bundled with the most commonly used commercial and open source plug-ins available for Java Standard Edition (SE), Java Enterprise Edition (EE), Extensible Markup Language (XML) and Unified Modeling Language (UML). It also integrates World Wide Web (Web 2.0)/ Asynchronous JavaScript (AJAX), Hibernate/ Standards, Productivity and Innovation for Growth (Spring), and Java NetBeans. This product has both a Stable stream and a Continuous Integration (CI) stream. Each stream shares an identical fundamental set of features and functions; the CI stream gets updated more frequently than the Stable stream. MyEclipse contains two primary editions: Standard and Professional. This entry covers both editions.
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.11
Decision Date:	11/02/2023 at 18:47:58 UTC
Introduced By:	Extended Tool List (ETL)
Vendor Name:	Genuitec

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
5.1.1	03/01/2007
5.5	05/01/2007
6.0	08/01/2007
6.0.1	10/01/2007
6.1	03/01/2008
6.5	06/01/2008
6.6	10/01/2008
7	03/01/2009
7.1.1	04/01/2009
7.5	06/01/2009
8.0	11/30/2009
8.5	03/29/2010
8.6	08/02/2010
9.1	07/05/2011
10.0	11/03/2011
10.6	07/30/2012
10.7	11/27/2012
2013	04/15/2013
2014	12/03/2013
2015	01/15/2015
2016 Stable	07/13/2016
2016 CI	09/27/2016
2017 CI x	01/03/2017
2017 Stable
2018 Cl x
2019.x
2021.5.x
2022.1.x	03/24/2022
2023.1.x

Current Decision Matrix (10/31/2023)

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

CY2023

CY2024

CY2025

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

10.6

Unapproved

10.7

Unapproved

2013

Unapproved

2014

Unapproved

2015

Unapproved

2016 Stable

Unapproved

2016 CI

Unapproved

2017 CI x

Unapproved

2017 Stable

Unapproved

2018 Cl x

Unapproved

2019.x

Divest
[3, 10, 12, 13]

Unapproved

2021.5.x

Approved w/Constraints
[3, 10, 12, 13]

Divest
[3, 10, 13, 14, 15]

Unapproved

2022.1.x

Approved w/Constraints
[3, 10, 12, 13]

Divest
[3, 10, 13, 14, 15]

Unapproved

2023.1.x

Unapproved

Approved w/Constraints
[3, 10, 13, 14, 15]

Decision Constraints


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

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

[3]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

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

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

[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]	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: Ensure that MyEclipse and the CVS Server have been configured to supply FIPS 140-2 data encryption. Data encryption shall be enforced using a FIPS-approved algorithm provided by the underlying FIPS-compliant OS. The applications that are developed using MyEclipse must be FIPS compliant to prevent unauthorized disclosure of information and protect sensitive data at rest and during transmission, including PII acknowledged in the end user license as collected, transformed, and used by the licensor, Genuitec. In addition to isolating the development environment in a separate enclave, appropriate authentication and access control must be enforced to ensure only authorized staff have access to it. The CVS server must be configured to utilize Secure Shell version 2 (SSH2) protocol.

[8]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This technology must use the latest version of Java Runtime Environment (JRE) - Oracle. This technology must use the latest version of Java Development Kit (JDK) - Oracle. Ensure that MyEclipse and the CVS Server have been configured to supply FIPS 140-2 data encryption. Data encryption shall be enforced using a FIPS-approved algorithm provided by the underlying FIPS-compliant OS. The applications that are developed using MyEclipse must be FIPS compliant to prevent unauthorized disclosure of information and protect sensitive data at rest and during transmission, including PII acknowledged in the end user license as collected, transformed, and used by the licensor, Genuitec. In addition to isolating the development environment in a separate enclave, appropriate authentication and access control must be enforced to ensure only authorized staff have access to it. The CVS server must be configured to utilize SSH2 protocol.

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

[10]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This technology must use the latest version of Java Runtime Environment (JRE) - Oracle. This technology must use the latest version of Java Development Kit (JDK) - Oracle. This technology cannot use Docker which is unapproved at the time of this writing. Per the Initial Product Review, users must abide by the following constraints: This product should be used with a VA approved container platform that has a developed and approved baseline configuration with specific hardening guidance regarding the secure implementation of Genuitec MyEclipse. Please reference the TRM for the approved solution and the Baseline Configuration Management website for more information. Ensure that MyEclipse and the CVS Server have been configured to supply FIPS 140-2 data encryption. Data encryption shall be enforced using a FIPS-approved algorithm provided by the underlying FIPS-compliant OS. The applications that are developed using MyEclipse must be FIPS compliant to prevent unauthorized disclosure of information and protect sensitive data at rest and during transmission, including PII acknowledged in the end user license as collected, transformed, and used by the licensor, Genuitec. In addition to isolating the development environment in a separate enclave, appropriate authentication and access control must be enforced to ensure only authorized staff have access to it. The CVS server must be configured to utilize SSH2 protocol.

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

[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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

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

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

[15]	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 2023.1.2 is the most current version and released 07/07/2023.

References

The following reference(s) are associated with this entry:
Type	Name	Description
Vendor Provided*	MyEclipse 2021.5.24—Refreshed and Refined!	This blog post provides information on the release date of this software as well as changes to it.
Vendor Provided*	Download MyEclipse	This webpage provides the download link for this software as well as system requirements.
Vendor Provided*	MyEclipse 2022.1 – Jakarta EE 9 and Vue in Eclipse + More!	This blog post provides information on the release date of version 2022.1 for this software as well as changes to it.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

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
MyEclipse Reports	MyEclipse Reports is an implementation of the Eclipse Business Intelligence and Reporting Tools (BIRT) framework, specialized to the MyEclipse web project conventions and directory layout, development workflow and testing features. MyEclipse Reports includes report development utilities and a runtime report engine. MyEclipse Reports provides wizards for creating new Report Web projects and adding the Report Web Runtime facet to existing MyEclipse web projects.
Secure Delivery Center	This module allows the organization to create, manage, distribute, lock-down and secure all Eclipse applications.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Development Tools	Integrated Development Environment (IDE)

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

MyEclipse eliminates the need to use specialized programming languages, software development kits, and hardware in the development of mobile device Web applications.
This technology provides a visual editor which simplifies user interface design for Hypertext Markup Language (HTML) and JavaScript Web pages. This capability supports improved developer productivity.
MyEclipse has the ability to generate Representational State Transfer (REST) services from existing Java Persistence Application Program Interface (JPA API) entities.
This technology has a comprehensive set of documentation.
At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.
This technology supports several industry standard file formats.

Adoption Risks

The latest release of Genuitec MyEclipse (2020.9.16) includes built-in container specific components including Docker, OpenShift, and Quarkus (a Kubernetes Native Java framework).
This technology can potentially use Docker, an unapproved technology.
There is no indication based on available vendor documentation that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
There are other approved solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
This software has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
This technology relies on Java Development Kit (JDK) - Oracle, which has a rapid release and update schedule.
This technology relies on Java Runtime Environment (JRE) - Oracle, which has a rapid release and update schedule.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
The application contains a secure storage feature which saves data in an encrypted form, using algorithms supplied by the Java virtual machine and/or the operating system. MyEclipse does not employ any encryption key longer than 64 bits. This does not meet the Department of Veterans Affairs (VA) requirement for encryption. Federal Information Processing Standards (FIPS) 140-2 encryption algorithms are required to protect VA sensitive data in transit.
Since IDEs are used to create software or applications, development teams may collaborate on projects and require a central repository for their work. MyEclipse allows the development team to connect to a CVS server that gives them the ability to share code, version control and resource management. Eclipse includes an SSH client for accessing a remote CVS server. The client supports both the SSH1 and SSH2 protocol versions. SSH1 has inherent design flaws which make it vulnerable. It is generally considered obsolete and should not be used.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved operating systems.
This product is middleware independent, and supports a large number of approved application servers and database systems.

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 (10/31/2023)

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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (10/31/2023)

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

EMAIL UPDATES