|
<Past |
Future> |
| 2023.x |
Approved w/Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Divest
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Divest
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Divest
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Divest
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Divest
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Divest
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| 2024.x |
Unapproved |
Approved w/Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
Approved w/Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] |
| | | | [1] | Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize the Docker Compose (Community), as it is unapproved for use on the TRM.
Per the Security Assessment Review, users must abide by the following constraints:
- To mitigate, an administrator shall monitor the .exe and .dll files used by the application with a file integrity checker to ensure no unauthorized changes occur.
- To mitigate, system owners must ensure they are using the most recent, TRM approved, version of JetBrains Rider.
- JetBrains Rider will require a 3rd party FIPS 140-2 or its successor certified solution for any data containing PHI/PII or VA sensitive information.
- 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.
JetBrains Rider shall 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 JetBrains Rider. Please reference the TRM for an approved solution and the Baseline Configuration Management website for more information.
- A vulnerability exists because JetBrains Rider v2023.3.2 installs multiple Open-source software applications, many of which are
listed as Divest or Unapproved on the VA Technical Reference Model (TRM). As a result, all projects currently utilizing any divested or unapproved technology/standards must plan to eliminate their use of the technology/standard and replace with approved options.
- System owners must ensure any third-party software used with JetBrains Rider is approved in the VA TRM and is configured according to VA approved baseline standards.
| | | [2] | 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. | | | [3] | 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. | | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | | [5] | 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. | | | [6] | 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. | | | [7] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. | | | [8] | 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 (Information System Security Officer) can advise on the ESCCB review process. | | | [9] | 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). | | | [10] | 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. | | | [11] | 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. | | | [12] | Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize the Docker Compose (Community), as it is unapproved for use on the TRM.
Per the Security Assessment Review, users must abide by the following constraints:
- To mitigate, an administrator shall monitor the .exe and .dll files used by the application with a file integrity checker to ensure no unauthorized changes occur.
- To mitigate, system owners must ensure they are using the most recent, TRM approved, version of JetBrains Rider.
- JetBrains Rider will require a 3rd party FIPS 140-2 or its successor certified solution for any data containing PHI/PII or VA sensitive information.
- 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.
JetBrains Rider shall 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 JetBrains Rider. Please reference the TRM for an approved solution and the Baseline Configuration Management website for more information.
- A vulnerability exists because JetBrains Rider v2023.3.2 installs multiple Open-source software applications, many of which are
listed as Divest or Unapproved on the VA Technical Reference Model (TRM). As a result, all projects currently utilizing any divested or unapproved technology/standards must plan to eliminate their use of the technology/standard and replace with approved options.
- System owners must ensure any third-party software used with JetBrains Rider is approved in the VA TRM and is configured according to VA approved baseline standards.
|
|
| Note: |
At the time of writing, version 2024.1.2 is the most current version, released 05/07/2024. |
