Tool for Oracle Application Developers (TOAD) for Oracle - The first knowledge sharing application in Vietnam

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]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]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]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:

[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 Project Special Forces (SPF) 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 ensure that Microsoft .NET Framework and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

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

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

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

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

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

Per the Initial Product Review:

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.

Users must ensure that Microsoft .NET Framework and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[20]Users must ensure that Microsoft .NET Framework, Microsoft Internet Explorer, Google Chrome, Microsoft Excel, Microsoft Word, Adobe Acrobat Reader Document Cloud (DC), and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

Users must divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.

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

Per the Initial Product Review, users must abide by the following constraints:

TOAD for Oracle will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
Applications developed in TOAD for Oracle 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, Continuous Monitoring standards.

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

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