|
| [1] | VA has a License Agreement in place for this technology. All license needs for this technology should be coordinated through the Technology Innovation Program (TIP). See the license section of this entry for more details.
Configuration and deployment standards for Oracle Database images and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
Unapproved versions and versions constrained from full production use can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.)
For all uses of Oracle 12c, the DISA STIG for Oracle 11g must be applied in lieu of a current Oracle 12g baseline. Once updated STIGs, guidance, and baselines are available for Oracle 12g, all Oracle12g users will be expected to migrate to the new Oracle 12g standards.
After 4/1/2015, Oracle 12c is not approved for any new production deployments except as part of an official Enterprise System Engineering (ESE) production pilot or production test of this version as approved by ESE Core Systems Engineering. Use of Oracle 12c in production should be limited to only solid business cases where the benefit outweighs the risks of operating on the older Oracle 11g baseline. All new Oracle 12g deployments after 4/1/2015 must be reviewed and approved via the AERB waiver process.
Oracle 10g is unapproved. Therefore, use of Oracle 10g should be limited to only solid business cases where the benefit outweighs the risks of operating to the newer Oracle 11g baseline. In order to use Oracle 10g, the DISA STIG for Oracle 11g must be applied and this exception reviewed and approved via the AERB waiver process. |
|
| [2] | 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. |
|
| [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] | 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] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
|
|
| [6] | VA has a License Agreement in place for this technology. All license needs for this technology should be coordinated through the Technology Innovation Program (TIP). See the license section of this entry for more details.
Configuration and deployment standards for Oracle Database images and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
Unapproved versions and versions constrained from full production use can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.)
For all uses of Oracle 12c, the Oracle 12c DISA STIG and the VA Baseline for Oracle 11g must be applied in lieu of a VA Oracle 12g baseline. Once VA releases an updated Oracle 12c baseline on or about June 1, 2016, all Oracle 12g users will be expected to migrate to the new Oracle 12g standards.
After 4/1/2015, Oracle 12c is not approved for any new production deployments except as part of an official Enterprise System Engineering (ESE) production pilot or production test of this version as approved by ESE Core Systems Engineering. Use of Oracle 12c in production should be limited to only solid business cases where the benefit outweighs the risks of operating on the older Oracle 11g baseline until the VA Baseline for Oracle 12c is released on or about June 1, 2016. All new Oracle 12g deployments after 4/1/2015 must be reviewed and approved via the AERB waiver process.
Oracle 10g is unapproved. Therefore, use of Oracle 10g should be limited to only solid business cases where the benefit outweighs the risks of operating to the newer Oracle 11g baseline. In order to use Oracle 10g, the DISA STIG for Oracle 11g must be applied and this exception reviewed and approved via the AERB waiver process. |
|
| [7] | VA has a License Agreement in place for this technology. All license needs for this technology should be coordinated through the Technology Innovation Program (TIP). See the license section of this entry for more details.
Configuration and deployment standards for Oracle Database images and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
Unapproved versions and versions constrained from full production use can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.)
For all uses of Oracle 12c, the Oracle 12c DISA STIG and the VA Baseline for Oracle 11g must be applied in lieu of a VA Oracle 12g baseline. Once VA releases an updated Oracle 12c baseline on or about end of QTR 1 2017, all Oracle 12g users will be expected to migrate to the new Oracle 12g standards.
After 4/1/2015, Oracle 12c is not approved for any new production deployments except as part of an official Enterprise System Engineering (ESE) production pilot or production test of this version as approved by ESE Core Systems Engineering. Use of Oracle 12c in production should be limited to only solid business cases where the benefit outweighs the risks of operating on the older Oracle 11g baseline until the VA Baseline for Oracle 12c is released on or about end of QTR 1 2017. All new Oracle 12g deployments after 4/1/2015 must be reviewed and approved via the AERB waiver process.
Oracle 10g is unapproved. Therefore, use of Oracle 10g should be limited to only solid business cases where the benefit outweighs the risks of operating to the newer Oracle 11g baseline. In order to use Oracle 10g, the DISA STIG for Oracle 11g must be applied and this exception reviewed and approved via the AERB waiver process. |
|
| [8] | 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). |
|
| [9] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. |
|
| [10] | VA has a License Agreement in place for this technology. All license needs for this technology should be coordinated through the Technology Innovation Program (TIP). See the license section of this entry for more details.
Configuration and deployment standards for Oracle Database images and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
Unapproved versions and versions constrained from full production use can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.)
Versions prior to 11.2.x are unapproved and should be limited to only solid business cases where the benefit outweighs the risks of complying with the latest baseline. In order to use prior versions, the DISA STIG for Oracle 11g or 12c must be applied and this exception reviewed and approved via the AERB waiver process.
Users must comply with the VA baseline. Please see the References section for the link to the baseline. |
|
| [11] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. |
|
| [12] | VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). See the license section of this entry for more details.
Configuration and deployment standards for Oracle Database images and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
Unapproved versions and versions constrained from full production use can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.)
Versions prior to 11.2.x are unapproved and must be limited to only solid business cases where the benefit outweighs the risks of complying with the latest baseline. In order to use prior versions, the DISA STIG for Oracle 11g or 12c must be applied and this exception reviewed and approved via the AERB waiver process.
Users must comply with the VA baseline. Please see the References section for the link to the baseline. |
|
| [13] | 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). |
|
| [14] | 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. |
|
| [15] | 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). |
|
| [16] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. |
|
| [17] | 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). |
|
| [18] | VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). See the license section of this entry for more details.
Configuration and deployment standards for Oracle Database images and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
Unapproved versions and versions constrained from full production use can be used only if a waiver, signed by the Deputy Chief Information Officer (CIO) of ASD and based upon a recommendation from the Strategic Technology Alignment Team (STAT), has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and STAT Waivers.)
Versions prior to 11.2.x are unapproved and must be limited to only solid business cases where the benefit outweighs the risks of complying with the latest baseline. In order to use prior versions, the Defense Information Security Agency (DISA) Security Technical Implementation Guide (STIG) for Oracle 11g or 12c must be applied and this exception reviewed and approved via the STAT waiver process.
Users must comply with the VA baseline. Please see the References section for the link to the baseline. |
|
| [19] | VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). See the license section of this entry for more details.
Configuration and deployment standards for Oracle Database images and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
Unapproved versions and versions constrained from full production use can be used only if a waiver, signed by the Deputy Chief Information Officer (CIO) of ASD and based upon a recommendation from the Strategic Technology Alignment Team (STAT), has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and STAT Waivers.)
Versions prior to 11.2.x are unapproved and must be limited to only solid business cases where the benefit outweighs the risks of complying with the latest baseline. In order to use prior versions, the Defense Information Security Agency (DISA) Security Technical Implementation Guide (STIG) for Oracle 11g or 12c must be applied and this exception reviewed and approved via the STAT waiver process.
Users must comply with the VA baseline. Please see the References section for the link to the baseline. |
|
| [20] | Configuration and deployment standards for Oracle Databases and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx |
|
| [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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
| [22] | 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. |
|
| [23] | 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). |
|
| [24] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. |
|
| [25] | 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). |
|
| [26] | 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). |
|
| [27] | Configuration and deployment standards for Oracle Databases and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx |
|
| [28] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. |
|
| [29] | 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). |
|
| [30] | 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. |
|
| [31] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. |
|
| [32] | 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). |
|
| [33] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process. |
|
| [34] | Configuration and deployment standards for Oracle Databases and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx
Users must not utilize Oracle Load Testing (OLT), as it is at the time of writing, unapproved in the TRM. |
|
| [35] | 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. |
|
| [36] | 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). |
|
| [37] | 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. |
