Rapid Application Development (RAD) Studio

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:	Rapid Application Development (RAD) Studio is an Integrated Development Environment (IDE) for building Win32 and Win64 applications. The RAD Studio IDE provides a set of utilities that are designed to streamline and simplify the development life cycle. This product stores user preferences in the Windows registry. Data created by the user (such as source code and projects) are saved wherever the user places them. By default, this is on the local hard drive. Additionally, the FireDAC component has the ability to access several VA-supported relational databases and manipulate the data within the data source it connects to. RAD Studio is available in three editions: Professional, Enterprise, and Architect. This entry covers all three editions. This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: https://dvagov.sharepoint.com/sites/OITMT/SitePages/MTHome.aspx 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 v24.2
Decision Date:	02/02/2024 at 03:08:03 UTC
Aliases:	RAD Studio
Introduced By:	TRM Request
Vendor Name:	Embarcadero Technologies

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	06/15/1999
6	06/15/2001
7	08/15/2002
2006	11/23/2005	04/15/2008	08/21/2009
2007	03/16/2007	12/15/2008	06/09/2021
XE	08/30/2010	09/04/2012	09/11/2013
XE2	08/21/2011	05/15/2013	09/11/2013
XE3	09/04/2012	05/15/2013	04/15/2014
XE4	04/22/2013	09/11/2013	09/02/2014
XE5	09/11/2013	04/15/2014	04/15/2015
XE6	04/15/2014	09/02/2014	09/01/2015
XE7	09/02/2014	04/15/2015	04/15/2016
XE8	05/27/2015	09/01/2015	03/22/2017
10.0 Seattle	08/31/2015	04/20/2016	11/05/2018
10.1 Berlin	04/20/2016	03/22/2017	11/05/2018
10.2.x Tokyo	03/22/2017	11/05/2018	05/26/2020
10.3.x Rio	02/14/2019	05/26/2020	09/09/2021
10.4.x Sydney	05/26/2020	09/09/2021	11/09/2023
11.x Alexandria	09/09/2021	11/09/2023
12.x Athens	11/09/2023

Current Decision Matrix (01/29/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

CY2017

CY2018

CY2019

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

2006

Unapproved

2007

Unapproved

XE

Unapproved

XE2

Unapproved

XE3

Unapproved

XE4

Unapproved

XE5

Unapproved

XE6

Divest
[2, 3, 4]

Unapproved

XE7

Divest
[2, 3, 4]

Divest
[2, 5, 6]

Divest
[2, 7, 8]

Divest
[2, 7, 9]

Divest
[2, 7, 10]

Unapproved

XE8

Approved w/Constraints
[2, 3, 4]

Divest
[2, 5, 6]

Divest
[2, 7, 8]

Divest
[2, 7, 9]

Divest
[2, 7, 10]

Unapproved

10.0 Seattle

Approved w/Constraints
[2, 3, 4]

Approved w/Constraints
[2, 5, 6]

Approved w/Constraints
[2, 7, 8]

Approved w/Constraints
[2, 7, 9]

Approved w/Constraints
[2, 7, 10]

Divest
[2, 7, 10]

10.1 Berlin

Approved w/Constraints
[2, 3, 4]

Approved w/Constraints
[2, 5, 6]

Approved w/Constraints
[2, 7, 8]

Approved w/Constraints
[2, 7, 9]

Approved w/Constraints
[2, 7, 10]

Divest
[2, 7, 10]

10.2.x Tokyo

Unapproved

Approved w/Constraints
[2, 3, 4]

Approved w/Constraints
[2, 5, 6]

Approved w/Constraints
[2, 7, 8]

Approved w/Constraints
[2, 7, 9]

Approved w/Constraints
[2, 7, 10]

Divest
[2, 7, 10]

10.3.x Rio

Unapproved

Approved w/Constraints
[2, 7, 10]

10.4.x Sydney

Unapproved

11.x Alexandria

Unapproved

12.x Athens

Unapproved

Decision Constraints


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

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

[3]	Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review.

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

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

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

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

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

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

Note:

At the time of writing, version 12.0 is the most current version.

Please note that the instances of this technology are listed with a separate schema from how the vendor markets their versions as scans follows what registers in programs and features as 23.0. This release is under the RAD Studio 12.0 umbrella.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	RAD Studio Product Editions		This webpage provides a chart of information on detailing the differences between versions of this software.
*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
C++ Builder	C++ Builder is a rapid application development environment for writing programs in the C++ programming language. C++ Builder combines the Visual Component Library and Integrated Development Environment (IDE) written in Object Pascal with multiple C++ compilers.
Delphi	Delphi is an IDE for rapid application development that includes a code editor, a visual designer, an integrated debugger, a source code control component, and support for third-party plugins.
FireDAC	FireDAC is a Universal Data Access library for developing applications, connected to enterprise databases. FireDAC is designed to enable native high-speed direct access from Delphi and C++ Builder to several VA-supported relational databases.
Hypertext Markup Language 5 (HTML5) Builder	Hypertext Markup Language 5 (HTML5) Builder enables users to build web and mobile applications with a single codebase using web standards.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Development Tools	Build and Deployment Tools
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
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Java Runtime Environment (JRE) - Oracle
Microsoft .NET Framework
Windows Subsystem for Linux (WSL) - (required for some configurations)

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

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.
There are minimal other TRM-approved technologies that provide the same functionality.
This technology has a comprehensive set of documentation.
This technology may improve productivity for specific staff whose responsibilities include application development.

Adoption Risks

This technology can integrate with and alter database technologies.
A vulnerability exists because the firewall rules changed to any/any (local IP/remote IP) with undefined ports for the bds.exe file which is the core application.
This technology can potentially use Python, SQLite, Open Secure Socket Layer (OpenSSL), and 7-Zip which users must ensure that approved versions are utilized.
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.
A vulnerability exists because RAD Studio 12 v23.0 installs Open-Source Software (OSS).
- Python v3.7.4
- SQLite3 v3.28.0.0
- Microsoft.VisualStudio v14.0.25407.0
- Json.NET v9.0.1.19813
- StreamJsonRpc v2.0.208.14008
- VaWPFTheming v1.0.0.0
- Newtonsoft Json.NET Windows Phone v4.0.0.0
- Json v4.8.4084.0
- OpenSSL library v1.1.1c
- 7-Zip v4.42 Standalone Plugin
Python v3.7.4, SQLite3 v3.28.0.0, OpenSSL v1.1.1c and 7-Zip v4.42 are Unapproved within the Department of Veterans Affairs.
A vulnerability exists because RAD Studio 12 v23.0 installs .exe files without a digital signature. This prevents the verification of the control`s publisher and assurance that it has not been tampered with since being published.
A vulnerability exists because RAD Studio 12 v23.0 utilizes commercial cloud computing services.
This technology requires My Structured Query Language (MySQL) Database - Community Editions, an unapproved technology.
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 product can be configured with a MySQL Commercial Edition 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 has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
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.
This technology can potentially use Firebird, Windows Subsystem for Linux (WSL) and SQLAnywhere, unapproved technologies.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved operating systems.
This technology can use a VA-preferred database.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

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 (01/29/2024)

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 (01/29/2024)

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