Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Tool for Oracle Application Developers (TOAD) for Oracle

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:	Tool for Oracle Application Developers (TOAD) for Oracle provides a set of Oracle Database development tools for developers, database designers, administrators, and testers to work with relational databases. This technology enables users to build and execute queries, create and modify database objects, and automate testing and development of Structured Query Language (SQL) and Procedural Language/SQL (PL/SQL) code. Additionally, TOAD for Oracle is designed to help users determine database application performance during and after testing. There are five editions of TOAD for Oracle: Base, Professional, Professional Database Admin (DBA), Xpert, and Developer. This entry covers all five editions. TOAD for Oracle creates a connection to one or more databases and allows users to view and manipulate data. This technology supports Oracle Database as a Service on Amazon Elastic Computing Cloud (EC2) and Oracle Cloud. 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.11
Decision Date:	11/02/2023 at 18:47:59 UTC
Aliases:	Toad for Oracle; Quest Software Toad for Oracle; TOAD Development Suite for Oracle
Introduced By:	TRM Request
Vendor Name:	Quest

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
8.6.1	04/04/2006
9.0.1	11/01/2006
9.1	08/03/2007
9.5	10/25/2007
9.6	03/08/2008
9.7	08/25/2008
10.0	10/01/2009
10.5	04/21/2010	10/01/2011	04/01/2012
10.6	09/16/2010	10/01/2012	04/01/2013
11.0	09/21/2011
11.5	04/19/2012
11.6	10/01/2012
12.0	06/19/2013
12.1	09/18/2013
12.6	08/31/2014
12.7	06/30/2015
12.8	10/31/2015
12.10	09/29/2016
12.11	06/19/2017
12.12	09/29/2017
13.x	04/20/2018
14.x	11/09/2020
15.x	09/13/2021
16.x	04/13/2022
17.x	10/30/2023

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

CY2017

CY2018

CY2019

Future>

Release

8.6.1

Unapproved

9.0.1

Unapproved

9.1

Unapproved

9.5

Unapproved

9.6

Unapproved

9.7

Unapproved

10.0

Unapproved

10.5

Unapproved

10.6

Unapproved

11.0

Unapproved

11.5

Unapproved

11.6

Unapproved

12.0

Unapproved

12.1

Divest
[3, 4, 5]

Divest
[5, 6, 7]

Divest
[6, 7, 8, 9]

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

Unapproved

12.6

Divest
[3, 4, 5]

Divest
[5, 6, 7]

Divest
[6, 7, 8, 9]

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

Unapproved

12.8

Approved w/Constraints
[3, 4, 5]

Approved w/Constraints
[5, 6, 7]

Divest
[6, 7, 8, 9]

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

Divest
[6, 7, 9, 11, 12]

Unapproved

12.10

Approved w/Constraints
[3, 4, 5]

Approved w/Constraints
[5, 6, 7]

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

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

Approved w/Constraints
[6, 7, 9, 11, 12]

Divest
[6, 7, 9, 11, 12]

12.11

Unapproved

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

Approved w/Constraints
[6, 7, 9, 11, 12]

Divest
[6, 7, 9, 11, 12]

12.12

Unapproved

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

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

Approved w/Constraints
[6, 7, 9, 11, 12]

Divest
[6, 7, 9, 11, 12]

13.x

Unapproved

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

Approved w/Constraints
[6, 7, 9, 11, 12]

14.x

Unapproved

15.x

Unapproved

16.x

Unapproved

17.x

Unapproved

Decision Constraints


[1]	Projects using this technology must meet Veterans Affairs (VA) Directive 6500 and implement Federal Information Processing Standards (FIPS 199) for all laptop devices and National Institute of Standards and Technology Special Publication 800-53 for all desktop devices when VA sensitive information is involved, or additional mitigating controls must be documented in an approved System Security Plan (SSP) to prevent potential disclosure of PII/PHI data.

[2]	Per the Initial Product Review: Enterprise Security Solutions Services (ESSS) conducted a pre-assessment and security requirements verification of TOAD for Oracle. It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied: It is a requirement that VA sensitive data is properly protected in accordance with VA Handbook 6500, Federal Information Security Management Act (FISMA), and FIPS 140-2 standards. TOAD does not meet the aforementioned requirements. FIPS data protection should be employed if sensitive data is used with this application. Applications developed in TOAD must follow safe coding practices in order to prevent the introduction of vulnerabilities in the VA Enterprise environment. The required controls for safe coding are available in the Department of Veterans Affairs (VA) Handbook 6500, Appendix F System and Information Integrity (SI) section. Further guidance can be found on the Veterans Affairs Software Assurance Resource Site in the document `Securing Applications During Development.` All source code developed using TOAD should be reviewed at selected times so as to monitor and capture any malicious code injections. User access should also be controlled and limited to privileges that are needed to perform specific duties. Auditing logs should be reviewed in accordance with the Department of Veterans Affairs (VA) Handbook 6500 on a weekly basis, minimally, by the ISO to monitor access to sensitive information and information systems.

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

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

[5]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Per the Initial Product Review: Enterprise Security Solutions Services (ESSS) conducted a pre-assessment and security requirements verification of Tool for Application Developers (TOAD) for Oracle. It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied: It is a requirement that VA sensitive data is properly protected in accordance with VA Handbook 6500, Federal Information Security Management Act (FISMA), and FIPS 140-2 standards. TOAD does not meet the aforementioned requirements. FIPS data protection should be employed if sensitive data is used with this application. Applications developed in TOAD must follow safe coding practices in order to prevent the introduction of vulnerabilities in the VA Enterprise environment. The required controls for safe coding are available in the Department of Veterans Affairs (VA) Handbook 6500, Appendix F System and Information Integrity (SI) section. Further guidance can be found on the Veterans Affairs Software Assurance Resource Site in the document `Securing Applications During Development.` All source code developed using TOAD should be reviewed at selected times so as to monitor and capture any malicious code injections. User access should also be controlled and limited to privileges that are needed to perform specific duties. Auditing logs should be reviewed in accordance with the Department of Veterans Affairs (VA) Handbook 6500 on a weekly basis, minimally, by the ISO to monitor access to sensitive information and information systems.

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

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

[8]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Per the Initial Product Review: Enterprise Security Solutions Services (ESSS) conducted a pre-assessment and security requirements verification of Tool for Application Developers (TOAD) for Oracle. It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied: It is a requirement that VA sensitive data is properly protected in accordance with VA Handbook 6500, Federal Information Security Management Act (FISMA), and FIPS 140-2 standards. TOAD does not meet the aforementioned requirements. FIPS data protection should be employed if sensitive data is used with this application. Applications developed in TOAD must follow safe coding practices in order to prevent the introduction of vulnerabilities in the VA Enterprise environment. The required controls for safe coding are available in the Department of Veterans Affairs (VA) Handbook 6500, Appendix F System and Information Integrity (SI) section. Further guidance can be found on the Veterans Affairs Software Assurance Resource Site in the document `Securing Applications During Development.` All source code developed using TOAD should be reviewed at selected times so as to monitor and capture any malicious code injections. User access should also be controlled and limited to privileges that are needed to perform specific duties. Auditing logs should be reviewed in accordance with the Department of Veterans Affairs (VA) Handbook 6500 on a weekly basis, minimally, by the ISO to monitor access to sensitive information and information systems.

[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]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Per the Initial Product Review: Enterprise Security Solutions Services (ESSS) conducted a pre-assessment and security requirements verification of Tool for Application Developers (TOAD) for Oracle. It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied: It is a requirement that VA sensitive data is properly protected in accordance with VA Handbook 6500, Federal Information Security Management Act (FISMA), and FIPS 140-2 standards. TOAD does not meet the aforementioned requirements. FIPS data protection should be employed if sensitive data is used with this application. Applications developed in TOAD must follow safe coding practices in order to prevent the introduction of vulnerabilities in the VA Enterprise environment. The required controls for safe coding are available in the Department of Veterans Affairs (VA) Handbook 6500, Appendix F System and Information Integrity (SI) section. Further guidance can be found on the Veterans Affairs Software Assurance Resource Site in the document `Securing Applications During Development.` All source code developed using TOAD should be reviewed at selected times so as to monitor and capture any malicious code injections. User access should also be controlled and limited to privileges that are needed to perform specific duties. Auditing logs should be reviewed in accordance with the Department of Veterans Affairs (VA) Handbook 6500 on a weekly basis, minimally, by the ISO to monitor access to sensitive information and information systems.

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

[12]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Per the Initial Product Review: Enterprise Security Solutions Services (ESSS) conducted a pre-assessment and security requirements verification of Tool for Oracle Application Developers (TOAD) for Oracle. It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied: It is a requirement that VA sensitive data is properly protected in accordance with VA Handbook 6500, Federal Information Security Management Act (FISMA), and FIPS 140-2 standards. TOAD does not meet the aforementioned requirements. FIPS data protection should be employed if sensitive data is used with this application. Applications developed in TOAD must follow safe coding practices in order to prevent the introduction of vulnerabilities in the VA Enterprise environment. The required controls for safe coding are available in the Department of Veterans Affairs (VA) Handbook 6500, Appendix F System and Information Integrity (SI) section. Further guidance can be found on the Veterans Affairs Software Assurance Resource Site in the document `Securing Applications During Development.` All source code developed using TOAD should be reviewed at selected times so as to monitor and capture any malicious code injections. User access should also be controlled and limited to privileges that are needed to perform specific duties. Auditing logs should be reviewed in accordance with the Department of Veterans Affairs (VA) Handbook 6500 on a weekly basis, minimally, by the ISO to monitor access to sensitive information and information systems.

Note:

At the time of writing, version 17.0.341.1977 is the most current version released.

The following reference(s) are associated with this entry:
Type	Name	Description
Vendor Provided*	Tool for Oracle Application Developers (TOAD) for Oracle Documentation	This webpage provides documentation for current and past versions of this technology to include release notes, installation guides, and user guides.
Requirement	Technical Documentation	This webpage outlines the technical specifications and release notes for the TOAD for Oracle technology.
*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
Benchmark Factory	The Benchmark Factory is a database performance testing tool that allows you to conduct database workload replay, industry-standard benchmark testing, and scalability testing.
Code Tester For Oracle	The Code Tester for Oracle automates the process of testing PL/SQL programs, making it possible for you to identify bugs and verify program correctness in a fraction of the time it has taken previously
Database Admin (DBA) Module	The DB Admin Module is designed to ensure database health and stability. The Database Browser provides navigation across multiple databases and deep object-level browsing for any Oracle Database using an embedded schema browser. The Database Monitor alerts users to performance issues that can be diagnosed with Spotlight on Oracle. The DB Admin Module allows users to execute a 200-point inspection across multiple virtualized databases with categories that include vulnerability assessment, configuration, performance, and storage.
Spotlight on Oracle	Spotlight on Oracle is a diagnostic and resolution application for Oracle Databases. Spotlight is designed to diagnose the performance of Oracle instances running on individual host machines. Users are provided with a visual representation of the database`s activity.
Structured Query Language (SQL) Optimizer for Oracle	The SQL Optimizer for Oracle automates the SQL optimization process and maximizes the performance of your SQL statements.
Toad Data Modeler	The Toad Data Modeler helps organizations create, maintain and document their database systems with a graphical interface.


Information Management Technologies Data Management	Database-Related Management Tools

- The information contained on this page is accurate as of the Decision Date (11/02/2023 at 18:47:59 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 (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

Architectural Risks

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

Architectural Risks

EMAIL UPDATES