|
| [1] | Toad is available under VA Enterprise License Agreement (ELA) for Quest products including Toad Development Suite with DBA Module for Oracle and Toad Development Suite for SQL Server. Additional product titles were included at the vendor`s discretion and are described below.
With the award of this ELA, all VA entities and VA contractor organizations are encouraged to use the VA ELA for Quest Toad product through duration of contract to avoid duplication of fees if additional procurements or maintenance renewals are established in parallel to the ELA. The VA ELA Administrator will provide additional guidance necessary to transition the VA entity or contactor into this ELA.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. |
|
| [2] | Toad is available under VA Enterprise License Agreement (ELA) for Quest products including Toad Development Suite with DBA Module for Oracle and Toad Development Suite for SQL Server. Additional product titles were included at the vendor`s discretion and are described below. With the award of this ELA, all VA entities and VA contractor organizations are required to use the VA ELA for Quest Toad product through duration of contract to avoid duplication of fees if additional procurements or maintenance renewals are established in parallel to the ELA. The VA ELA Administrator will provide additional guidance necessary to transition the VA entity or contactor into this ELA.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. |
|
| [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] | TOAD is available under VA Enterprise License Agreement (ELA) for Quest products including TOAD Development Suite with DBA Module for Oracle and TOAD Development Suite for SQL Server. Additional product titles were included at the vendor`s discretion and are described below. With the award of this ELA, all VA entities and VA contractor organizations are required to use the VA ELA for Quest TOAD product through duration of contract to avoid duplication of fees if additional procurements or maintenance renewals are established in parallel to the ELA. The VA ELA Administrator will provide additional guidance necessary to transition the VA entity or contactor into this ELA.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. |
|
| [5] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
TOAD is available under VA Enterprise License Agreement (ELA) for Quest products including TOAD Development Suite with DBA Module for Oracle and TOAD Development Suite for SQL Server. Additional product titles were included at the vendor`s discretion and are described below. With the award of this ELA, all VA entities and VA contractor organizations are encouraged to use the VA ELA for Quest TOAD products through duration of contract to avoid duplication of fees if additional procurements or maintenance renewals are established in parallel to the ELA. The VA ELA Administrator will provide additional guidance necessary to transition the VA entity or contractor into this ELA. |
|
| [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] | 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). |
|
| [8] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. |
|
| [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 with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
| [10] | 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 with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
| [11] | 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. |
|
| [12] | 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 with the Project Special Forces (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
| [13] | 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 with the VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
| [14] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize Citrix XenApp and Ingres Database, as it is at the time of writing, unapproved in the TRM.
Users must ensure that Microsoft .NET Framework, Microsoft Access, Microsoft Structured Query Language (SQL) Server, My Structured Query Language (MySQL) Database, Oracle Database, PostgreSQL, and VMware vSphere are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) |
|
| [15] | 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. |
|
| [16] | 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. |
|
| [17] | 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. |
|
| [18] | 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). |
