|
<Past |
Future> |
| SQL Server 2000 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| SQL Server 2005 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| SQL Server 2008 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| SQL Server 2008 R2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| SQL Server 2012 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| SQL Server 2014 |
Divest
[31, 33, 35, 36, 37, 38, 39] |
Divest
[31, 33, 35, 36, 37, 38, 39] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| SQL Server 2016 |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
| SQL Server 2017 Win |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| SQL Server 2017 Lin |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| SQL Server 2019 Win |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
| SQL Server 2019 Lin |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| SQL Server 2022 Win |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39] |
| SQL Server 2022 Lin |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | | | [1] | 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. | | | [2] | 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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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 evaluation 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.)
SQL Server 2014 is under evaluation and is currently not approved for production 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 SQL Server 2014 in production should be limited to only solid business cases where the benefit outweighs the risks of operating on the older SQL Server 2012 baseline. In order to use SQL Server 2014, the DISA STIG for SQL Server 2012 must be applied in lieu of a current SQL Server 2014 baseline and this exception reviewed and approved via the AERB waiver process. Once updated STIGs, guidance, and baselines are available for SQL Server 2014, any waivered projects will be expected to migrate to the new SQL Server 2014 standards.
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 should be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 baseline. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 must be applied and this exception reviewed and approved via the AERB waiver process. | | | [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] | 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. | | | [5] | 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. | | | [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] | 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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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 evaluation 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.)
SQL Server 2014 is under evaluation and is currently not approved for production 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 SQL Server 2014 in production should be limited to only solid business cases where the benefit outweighs the risks of operating on the older SQL Server 2012 baseline. In order to use SQL Server 2014, the DISA STIG for SQL Server 2012 must be applied in lieu of a current SQL Server 2014 baseline and this exception reviewed and approved via the AERB waiver process. Once updated STIGs, guidance, and baselines are available for SQL Server 2014, any waivered projects will be expected to migrate to the new SQL Server 2014 standards.
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 should be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 baseline. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 must be applied and this exception reviewed and approved via the AERB waiver process.
SQL Server Reporting Services (SSRS) is not to be used for new projects or added to existing projects until such time as the SSRS product is made fully Section 508 complaint by the vendor. In order to use SSRS in new projects or add SSRS into existing projects after 4/8/2015, the exception must be reviewed and approved via the AERB waiver process. | | | [8] | 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.
| | | [9] | 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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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 evaluation 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.)
SQL Server 2014 is under evaluation and is currently not approved for production 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 SQL Server 2014 in production should be limited to only solid business cases where the benefit outweighs the risks of operating on the older SQL Server 2012 baseline. In order to use SQL Server 2014, the DISA STIG for SQL Server 2012 must be applied in lieu of a current SQL Server 2014 baseline and this exception reviewed and approved via the AERB waiver process. Once updated STIGs, guidance, and baselines are available for SQL Server 2014, any waivered projects will be expected to migrate to the new SQL Server 2014 standards.
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 should be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 baseline. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 must be applied and this exception reviewed and approved via the AERB waiver process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and should not be used by any end-user applications. | | | [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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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 evaluation 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.)
SQL Server 2014 and 2016 are under evaluation and are currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test as approved by ESE Core Systems Engineering. Use of SQL Server 2014 or 2016 in production should be limited to only solid business cases where the benefit outweighs the risks of operating on the older SQL Server 2012 baseline. In order to use SQL Server 2014 or 2016, the DISA STIG for SQL Server 2012 must be applied in lieu of a current SQL Server 2014 or 2016 baseline and this exception reviewed and approved via the AERB waiver process. Once updated STIGs, guidance, and baselines are available for SQL Server 2014 or 2016, any waivered projects will be expected to migrate to the new SQL Server 2014 or 2016 standards.
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 should be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 baseline. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 must be applied and this exception reviewed and approved via the AERB waiver process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and should not be used by any end-user applications. | | | [11] | 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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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 evaluation 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.)
SQL 2016 is under evaluation and are currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test as approved by ESE Core Systems Engineering. Use of SQL Server 2016 in production must be limited to only solid business cases where the benefit outweighs the risks of operating on the older SQL Server 2014 baselines. In order to use SQL Server 2016, the DISA STIG for SQL Server 2014 must be applied in lieu of a current SQL Server 2016 baseline and this exception reviewed and approved via the AERB waiver process. Once updated STIGs, guidance, and baselines are available for SQL Server 2016, any waivered projects will be expected to migrate to the new SQL Server 2016 standards.
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 or 2014 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 or 2014 must be applied and this exception reviewed and approved via the AERB waiver process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications. | | | [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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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
SQL 2016 requires risk acceptance and mitigation by the implementing organization approved by the project ISO. While Solution Delivery highly recommends that no project in VA use SQL Server 2016 until the DISA STIGs are released and the corresponding VA baseline for SQL Server 2016 is ratified, there are some projects within VA that are willing to accept the risks of not following the recommendations of Solution Delivery. The risk and responsibility of proceeding to use SQL Server 2016 Database and applying the SQL Server 2014 baseline to it, rests solely with the project. Solution Delivery does not endorse or advocate proceeding without an established baseline utilizing published SQL Server 2016 DISA STIGs. See the SQL Server 2016 Alpha Baseline in the reference tab for more information.
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 or 2014 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 or 2014 must be applied and this exception reviewed and approved via the STAT waiver process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications. | | | [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] | 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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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
At this time there is no VA baseline for SQL Server 2017. Until a baseline has been created and published on the BCM website, SQL Server 2017 is unapproved. Users may use SQL Server 2012, 2014 and also 2016 with risk acceptance and following all listed constraints.
SQL 2016 requires risk acceptance and mitigation by the implementing organization approved by the project ISO. While Solution Delivery highly recommends that no project in VA use SQL Server 2016 until the DISA STIGs are released and the corresponding VA baseline for SQL Server 2016 is ratified, there are some projects within VA that are willing to accept the risks of not following the recommendations of Solution Delivery. The risk and responsibility of proceeding to use SQL Server 2016 Database and applying the SQL Server 2014 baseline to it, rests solely with the project. Solution Delivery does not endorse or advocate proceeding without an established baseline utilizing published SQL Server 2016 DISA STIGs. See the SQL Server 2016 Alpha Baseline in the reference tab for more information.
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 or 2014 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 or 2014 must be applied and this exception reviewed and approved via the STAT waiver process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications. | | | [16] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place. | | | [17] | 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. | | | [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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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
At this time there is no VA baseline for SQL Server 2017. Until a baseline has been created and published on the BCM website, SQL Server 2017 is unapproved. Users may use SQL Server 2012, 2014, and 2016 following all listed constraints.
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012, 2014, or 2016 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012, 2014, or 2016 must be applied and this exception reviewed and approved via the STAT waiver process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications. | | | [19] | Users must ensure they are only using Structured Query Language (SQL) Server with Windows Platforms
Structured Query Language (SQL) Server 2017 and 2019 are in planning and only Solution Delivery Platform Engineering may use or authorize the technology for planning and pilot evaluation purposes until the VA baseline for SQL Server 2017 and 2019 is published. No production deployment date for SQL Server 2017 and 2019 have been set as of this writing.
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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012, 2014, or 2016 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012, 2014, or 2016 must be applied and this exception reviewed and approved via the STAT waiver process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications. | | | [20] | 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. Contact your local CIO office if more information is needed in regards to the use of this technology. | | | [21] | Users must ensure they are only using Structured Query Language (SQL) Server with Windows Platforms
Structured Query Language (SQL) Server 2019 is in planning and only Solution Delivery Platform Engineering may use or authorize the technology for planning and pilot evaluation purposes until the VA baseline for SQL Server 2019 is published. No production deployment date for SQL Server 2019 have been set as of this writing. As of this writing VA has no plans to support SQL Server 2017 and will bypass support of this version.
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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012, 2014, or 2016 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012, 2014, or 2016 must be applied and this exception reviewed and approved via the STAT waiver process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications. | | | [22] | Users must ensure they are only using Structured Query Language (SQL) Server with Windows Platforms
As of this writing VA has no plans to support SQL Server 2017 and will bypass support of this version.
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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012, 2014, 2016 or 2019 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012, 2014, or 2016 must be applied and this exception reviewed and approved via the POAM process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications. | | | [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 ISO (Information 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 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). | | | [25] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place. | | | [26] | Users must ensure they are only using Structured Query Language (SQL) Server with Windows Platforms
Users much ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
As of this writing VA has no plans to support SQL Server 2017 and will bypass support of this version.
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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, 2008 and 2012 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2014, 2016 or 2019 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2014, or 2016 must be applied and this exception reviewed and approved via the POAM process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications. | | | [27] | At the time of writing, the baseline configuration supports only Windows Server installations. Users must not utilize this technology on Linux environments until a baseline configuration is developed for Linux systems.
As of this writing VA has no plans to support SQL Server 2017 and will bypass support of this version.
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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, 2008 and 2012 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2014, 2016 or 2019 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2014, or 2016 must be applied and this exception reviewed and approved via the POAM process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications. | | | [28] | 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. | | | [29] | At the time of writing, the baseline configuration supports only Windows Server installations. Users must not utilize this technology on Linux environments until a baseline configuration is developed for Linux systems.
As of this writing VA has no plans to support SQL Server 2017 and will bypass support of this version.
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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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
SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, 2008 and 2012 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2016 or 2019 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2014, or 2016 must be applied and this exception reviewed and approved via the POAM process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications. | | | [30] | 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). | | | [31] | 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. | | | [32] | 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. | | | [33] | 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. | | | [34] | 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). | | | [35] | 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. | | | [36] | 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. | | | [37] | At the time of writing, the baseline configuration supports only Windows Server installations. Users must not utilize this technology on Linux environments until a baseline configuration is developed for Linux systems.
As of this writing VA has no plans to support SQL Server 2017 and will bypass support of this version.
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). Refer to the license section of this entry for more details.
Configuration and deployment standards for SQL Server images and their host Windows 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://dvagov.sharepoint.com/sites/OITBCM/lists/secure_configuration_baselines/generalview.aspx
SQL Server 2000, 2005, 2008, and 2012 are unapproved. Therefore, use of SQL Server 2000, 2005, 2008 and 2012 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2016 or 2019 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2014, or 2016 must be applied and this exception reviewed and approved via the POAM process.
Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications.
Users must not utilize Structured Query Language (SQL) Backup Pro, as it is at the time of writing, unapproved in the TRM. | | | [38] | 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. | | | [39] | 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). |
|
| Note: |
At the time of writing, version 2022 (Windows & Linux) build 2022.160.4105.2 is the most current version.
A baseline configuration of this technology was developed by the BCM team. At the time of writing, the approved baseline versions are 2016, 2019, & 2022. The VA will bypass usage of SQL Server 2017. |
