PyCharm

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:	PyCharm is an integrated development environment (IDE) used in computer programming, explicitly for the Python language. This technology has a built-in terminal that provides code analysis, a graphical debugger, an integrated unit tester and integration with version control systems. Additionally, PyCharm has an interactive Python console and supports Anaconda. This technology accesses data from a variety of sources, such as Db2, Maria Database (MariaDB), Microsoft Structured Query Language (SQL) Server, Mongo Database (MongoDB), Oracle Database, PostgreSQL, Redis, SQLite, Apache Cassandra, and My Structured Query Language (MySQL) databases to store data. There are two editions available for this product: Community and Professional. Each edition has the same core functionality, however, the Professional edition includes additional analysis capabilities and has database consoles for managing data structures in databases. The Community Edition is free and open source and the Professional edition is available under a commercial license. 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 v24.4
Decision Date:	04/18/2024 at 18:19:35 UTC
Introduced By:	TRM Request
Vendor Name:	JetBrains

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
2016.3	11/23/2016
2017.1	03/16/2017
2017.3.x	11/29/2017
2018.x	03/28/2018
2019.x	03/26/2019
2020.x	06/02/2020
2021.x	04/06/2021
2022.x	07/20/2022
2023.x	03/29/2023
2024.x	04/03/2024

Current Decision Matrix (04/15/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

CY2022

CY2023

CY2024

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

2016.3

Unapproved

2017.1

Unapproved

2017.3.x

Unapproved

2018.x

Unapproved

2019.x

Unapproved

2020.x

Divest
[2, 5, 6, 7, 8, 9]

Divest
[6, 7, 8, 9, 10, 11]

Unapproved

2021.x

Approved w/Constraints
[2, 5, 6, 7, 8, 9]

Divest
[2, 5, 6, 7, 8, 9]

Divest
[6, 7, 8, 9, 10, 11]

Unapproved

2022.x

Unapproved

Approved w/Constraints
[2, 5, 6, 7, 8, 9]

Approved w/Constraints
[6, 7, 8, 9, 10, 11]

Divest
[7, 8, 9, 10, 11, 12]

Divest
[7, 8, 9, 10, 11, 13, 14]

2023.x

Unapproved

Approved w/Constraints
[7, 8, 9, 10, 11, 12]

Divest
[7, 8, 9, 10, 11, 13, 14]

2024.x

Unapproved

Approved w/Constraints
[7, 8, 9, 10, 11, 13, 14]

Decision Constraints


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

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

[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]	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 Development Kit (JDK) - Oracle.

[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]	This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Firefox, Google Chrome, Microsoft SQL Server, Postgresql, My Structured Query Language (MySQL) Database - Commercial Editions, and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must not utilize Docker Compose (Community) as it is, at the time of writing, unapproved in the TRM. Users must not utilize Apache Cassandra as it is, at the time of writing, unapproved in the TRM. Users must not utilize Maria Database (MariaDB) Server as it is, at the time of writing, unapproved in the TRM.

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

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

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

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

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

[12]	This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Firefox, Google Chrome, Microsoft SQL Server, PostgreSQL, My Structured Query Language (MySQL) Database - Commercial Editions, and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must not utilize Docker Compose (Community) as it is, at the time of writing, unapproved in the TRM. Users must not utilize Apache Cassandra as it is, at the time of writing, unapproved in the TRM. Users must not utilize Maria Database (MariaDB) Server as it is, at the time of writing, unapproved in the TRM.

[13]	This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Firefox, Google Chrome, Microsoft Structured Query Language (SQL) Server, PostgreSQL, My Structured Query Language (MySQL) Database - Commercial Editions, MongoDB, and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must not utilize Apache Cassandra, Redis, Maria Database (MariaDB) Server, and My Structured Query Language (MySQL) Database - Community Editions, as they are, at the time of writing, unapproved in the TRM.

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

Note:

At the time of writing, version 2024.1 is the most current version, released 04/03/2024.

References

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.

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
No components have been identified for this entry.

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)

Open Source

This entry is available as an open source technology.

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Windows Client - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Apache Cassandra - (required for some configurations)
Db2 - (required for some configurations)
Java Runtime Environment (JRE) - Oracle
JDK - Oracle Java Standard Edition (SE) Development Kit
Maria Database (MariaDB) Server - (required for some configurations)
Microsoft Structured Query Language (SQL) Server - (required for some configurations)
Mirantis Container Runtime (MCR) - (required for some configurations)
MongoDB Enterprise Advanced - (required for some configurations)
My Structured Query Language (MySQL) Database - Commercial Editions - (required for some configurations)
My Structured Query Language (MySQL) Database - Community Editions - (required for some configurations)
Oracle Database - (required for some configurations)
PostgreSQL - (required for some configurations)
Redis - (required for some configurations)
SQLite - (required for some configurations)

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology supports several industry standard file formats.
This technology may improve productivity for specific staff whose responsibilities include code analysis, debugging, and unit testing.
The vendor of this technology is an industry leader in the subject matter.
The Community Edition of this technology is available at no cost through open source licensing and supports VA`s open source initiative.
This is a well-documented technology.

Adoption Risks

This technology relies on Java Development Kit (JDK) - 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.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search for more details.
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
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.
This technology can potentially use Apache Cassandra, Redis, Maria Database (MariaDB) Server, and My Structured Query Language (MySQL) Database - Community Editions, unapproved technologies.
There is no indication based on either the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
This technology relies on Java Runtime Environment (JRE) - Oracle, which has a rapid release and update schedule.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved operating 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 (04/15/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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 (04/15/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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