|
[1] | 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. |
|
[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] | 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). |
|
[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 contractor 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 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 contractor into this ELA. |
|
[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] | 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). |
|
[8] | 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. |
|
[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.
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 contractor into this ELA. |
|
[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.
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. |
|
[13] | 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. |
|
[14] | 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). |
|
[15] | 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). |
|
[16] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft Internet Explorer (IE), Microsoft .NET Framework, and Acrobat Reader are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
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. |
|
[17] | 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. |
|
[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). |
|
[19] | 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). |
|
[20] | 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). |
|
[21] | 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). |
|
[22] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
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. |
|
[23] | 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 VA Handbook 6500. |
|
[24] | 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 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). |
|
[25] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft Access, Microsoft Excel, and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
TOAD for SQL Server is not Federal Information Processing Standards (FIPS) 140-2 certified. This technology will require third party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
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. |
|
[26] | 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. |
|
[27] | 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). |
|
[28] | 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. |