Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Microsoft Access

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Microsoft Access, also known as Microsoft Office Access, is a database management system from Microsoft that combines a relational database engine with a graphical user interface and software-development tools.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has been assessed by the Section 508 Office and found non-conformant. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.2
Decision Date:	02/27/2024 at 03:43:30 UTC
Aliases:	MS Access; MS Office Access; Microsoft Office Access
Introduced By:	TRM Analysis
Vendor Name:	Microsoft

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
Office 11.0/2003	11/17/2003	04/08/2014	04/08/2014
Office 12.0/2007	01/27/2007	10/10/2017	10/10/2017
Office 14.0/2010	07/15/2010	10/13/2020	10/13/2020
Office 15.0/2013	07/16/2012	04/11/2023	04/11/2023
Office 16.0/2016	09/22/2015	10/14/2025	10/14/2025
Office 19.0/2018	09/24/2018

Current Decision Matrix (02/22/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time 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. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2017

CY2018

CY2019

Future>

Release

Office 11.0/2003

Unapproved

Office 12.0/2007

Divest
[5, 6, 9, 10]

Divest
[5, 6, 10, 11]

Unapproved

Office 14.0/2010

Approved w/Constraints
[5, 6, 9, 10]

Approved w/Constraints
[5, 6, 10, 11]

Approved w/Constraints
[10, 12, 13, 14]

Approved w/Constraints
[4, 10, 13, 14, 15]

Divest
[4, 10, 13, 14, 16]

Unapproved

Office 15.0/2013

Unapproved

Office 16.0/2016

Approved w/Constraints
[1, 5, 6, 9, 10]

Approved w/Constraints
[5, 6, 10, 11]

Approved w/Constraints
[10, 12, 13, 14]

Approved w/Constraints
[4, 10, 13, 14, 15]

Approved w/Constraints
[4, 10, 13, 14, 16]

Approved w/Constraints
[10, 12, 13, 14]

Office 19.0/2018

Unapproved

Decision Constraints


[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]	Per VA Handbook 6500 (Appendix F) all systems with a Moderate or High risk assessment are required to use a FIPS 140-2 compliant DBMS solution to protect information at rest or have mitigating controls documented in an approved System Security Plan (SSP) for the system. It is the responsibility of the system owner to ensure that an appropriate DBMS technology is selected or that mitigating controls are in place and documented in the SSP. Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Microsoft Office images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to. Office 15.0/2013 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 Client Services or an AERB waiver while under evaluation.

[3]	Configuration and deployment standards for databases 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 VA has ELAs in place for preferred RDBMS technologies (Microsoft SQL Server and Oracle DB). Customers should get their licenses through these channels, not via independent, uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx Usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. Desktop DBMS technologies may not be used to support line of business operations requiring data durability/ persistence. Storage of PHI/PII/VA sensitive data in databases built on desktop DBMS platforms is Prohibited. Desktop DBMS systems are to be phased out and decommissioned by 2017 in accordance with the VA Enterprise Technology Strategic Plan.

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

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

[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]	Configuration and deployment standards for databases 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 VA has ELAs in place for preferred RDBMS technologies (Microsoft SQL Server and Oracle DB). Customers should get their licenses through these channels, not via independent, uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx Usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. Desktop DBMS technologies may not be used to support line of business operations requiring data durability/ persistence. Storage of PHI/PII/VA sensitive data in databases built on desktop DBMS platforms is Prohibited. Office 15.0/2013 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 Client Services or an AERB waiver while under evaluation.

[8]	Configuration and deployment standards for databases 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 VA has ELAs in place for preferred RDBMS technologies (Microsoft SQL Server and Oracle DB). Customers should get their licenses through these channels, not via independent, uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx Usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. Desktop DBMS technologies may not be used to support line of business operations requiring data durability/persistence. Office 15.0/2013 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 Client Services or an AERB waiver while under evaluation.

[9]	Configuration and deployment standards for databases and their host server images must be followed and adhered to. Information on these standards may be found at https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx VA has ELAs in place for preferred RDBMS technologies (Microsoft SQL Server and Oracle DB). Customers should get their licenses through these channels, not via independent, uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx Usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. Desktop DBMS technologies may not be used to support line of business operations requiring data durability/persistence. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. The VA will not being deploying or approving the use of Office 2013 or its components (InfoPath, Excel, OneNote, Outlook, PowerPoint, Publisher, Access and Word) as Enterprise System Engineering (ESE) is testing and working on a deployment plan for Office 365 ProPlus (Office 2016). As such, Windows Office 365 ProPlus (16.x) is under evaluation and is currently not approved for production. When properly configured as a front-end client, no data at rest should be stored by Microsoft (MS) Access. MS Access may only be used with sensitive data as part of a secured system when Access is configured as a client front-end to an appropriately secured MS SQL Server or MS SharePoint Server following VA security configuration baselines and connected via a Federal Information Processing Standard (FIPS) 140-2 certified encrypted connection.

[10]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[11]	Configuration and deployment standards for databases and their host server images must be followed and adhered to. Information on these standards may be found at https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx VA has ELAs in place for preferred RDBMS technologies (Microsoft SQL Server and Oracle DB). Customers should get their licenses through these channels, not via independent, uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx If free trialware is utilized, the software must be purchased or removed at the end of the trial period. The VA will not being deploying or approving the use of Office 2013 or its components (InfoPath, Access, Excel, OneNote, Outlook, PowerPoint, Publisher, Access and Word) as Solution Delivery (SD) is deploying Office 365 ProPlus (Office 2016). For Microsoft Access 2010 and prior versions, usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. For Microsoft Access 2010 and prior versions, Microsoft Access may not be used to support line of business operations requiring data durability/persistence. Further, when properly configured as a front-end client, no data at rest should be stored by Microsoft (MS) Access 2010 and prior. These older versions may only be used with sensitive data as part of a secured system when Access is configured as a client front-end to an appropriately secured MS SQL Server or MS SharePoint Server following VA security configuration baselines and connected via a Federal Information Processing Standard (FIPS) 140-2 certified encrypted connection. For Microsoft Access 2016 and subsequent versions, the security configuration baseline must comply to the DISA STIG for Microsoft Access 2016 or subsequent version. When Microsoft Access 2016 and subsequent versions are used for business processes OR used with VA sensitive data including PHI and PII, the data files must be stored in storage location encrypted by FIPS 140-2 certified encryption. Further, the files must be securely backed up on a regular basis for recovery purposes, and access controls to that encrypted storage location must be restricted to only those individuals that are allowed access to the data. Users must not solely rely on Microsoft Access application passwords to protect sensitive data from unauthorized access. Appropriate authorization and role-based access control should be enforced to ensure only authorized staff have access to the data files and controls. There should be a clear delineation of duties for staff supporting and utilizing the tool. For example, access to the security controls should be restricted to certain staff who require it to accomplished assigned tasks. All instances used for business processes OR VA sensitive data including PHI and PII, must be reviewed and approved by the local ISO and privacy officer.

[12]	Configuration and deployment standards for Microsoft Office products (including Microsoft Access) are defined and managed at the enterprise level by ITOPS Solution Delivery Client Services (email: OIT ITOPS SD EE Desktop and Device Engineering) and must be followed. VA has ELAs in place for preferred RDBMS technologies (Microsoft SQL Server and Oracle DB). Customers should get their licenses through these channels, not via independent, uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx If free trialware is utilized, the software must be purchased or removed at the end of the trial period. The VA will not being deploying or approving the use of Office 2013 or its components (InfoPath, Access, Excel, OneNote, Outlook, PowerPoint, Publisher, Access and Word) as Solution Delivery (SD) is deploying Office 365 ProPlus (Office 2016). For Microsoft Access 2010 and prior versions, usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. For Microsoft Access 2010 and prior versions, Microsoft Access may not be used to support line of business operations requiring data durability/persistence. Further, when properly configured as a front-end client, no data at rest should be stored by Microsoft (MS) Access 2010 and prior. These older versions may only be used with sensitive data as part of a secured system when Access is configured as a client front-end to an appropriately secured MS SQL Server or MS SharePoint Server following VA SQL Server security configuration baselines (located at: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx) and connected via a Federal Information Processing Standard (FIPS) 140-2 certified encrypted connection. For Microsoft Access 2016 and subsequent versions, the security configuration baseline defined and managed at the enterprise level by ITOPS Solution Delivery Client Services (email: OIT ITOPS SD EE Desktop and Device Engineering) must comply with the DISA STIG for Microsoft Access 2016 or subsequent version. When Microsoft Access 2016 and subsequent versions are used for business processes OR used with VA sensitive data including PHI and PII, the data files must be stored in storage location encrypted by FIPS 140-2 certified encryption. Further, the files must be securely backed up on a regular basis for recovery purposes, and access controls to that encrypted storage location must be restricted to only those individuals that are allowed access to the data. Users must not solely rely on Microsoft Access application passwords to protect sensitive data from unauthorized access. Appropriate authorization and role-based access control should be enforced to ensure only authorized staff have access to the data files and controls. There should be a clear delineation of duties for staff supporting and utilizing the tool. For example, access to the security controls should be restricted to certain staff that requires it to accomplished assigned tasks. All instances used for business processes OR VA sensitive data including PHI and PII, must be reviewed and approved by the local ISO and privacy officer.

[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]	Configuration and deployment standards for Microsoft Office products (including Microsoft Access) are defined and managed at the enterprise level by ITOPS Solution Delivery Client Services (email: OIT ITOPS SD EE Desktop and Device Engineering) and must be followed. VA has ELAs in place for preferred RDBMS technologies (Microsoft SQL Server and Oracle DB). Customers must get their licenses through these channels, not via independent, uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx If free trialware is utilized, the software must be purchased or removed at the end of the trial period. The VA will not being deploying or approving the use of most Office 2013 components (Access, Excel, OneNote, Outlook, PowerPoint, Publisher, Access and Word) as Solution Delivery (SD) is deploying Office 365 ProPlus (Office 2016). For Microsoft Access 2010 and prior versions, usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. For Microsoft Access 2010 and prior versions, Microsoft Access may not be used to support line of business operations requiring data durability/persistence. Further, when properly configured as a front-end client, no data at rest may be stored by Microsoft (MS) Access 2010 and prior. These older versions may only be used with sensitive data as part of a secured system when Access is configured as a client front-end to an appropriately secured MS SQL Server or MS SharePoint Server following VA SQL Server security configuration baselines (located at: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx) and connected via a Federal Information Processing Standard (FIPS) 140-2 certified encrypted connection. For Microsoft Access 2016 and subsequent versions, the security configuration baseline defined and managed at the enterprise level by ITOPS Solution Delivery Client Services (email: OIT ITOPS SD EE Desktop and Device Engineering) must comply with the DISA STIG for Microsoft Access 2016 or subsequent version. When Microsoft Access 2016 and subsequent versions are used for business processes OR used with VA sensitive data including PHI and PII, the data files must be stored in storage location encrypted by FIPS 140-2 certified encryption. Further, the files must be securely backed up on a regular basis for recovery purposes, and access controls to that encrypted storage location must be restricted to only those individuals that are allowed access to the data. Users must not solely rely on Microsoft Access application passwords to protect sensitive data from unauthorized access. Appropriate authorization and role-based access control must be enforced to ensure only authorized staff have access to the data files and controls. There must be a clear delineation of duties for staff supporting and utilizing the technology. For example, access to the security controls must be restricted to certain staff that requires it to accomplished assigned tasks. All instances used for business processes OR VA sensitive data including PHI and PII, must be reviewed and approved by the local ISO and privacy officer.

[16]	Configuration and deployment standards for Microsoft Office products (including Microsoft Access) are defined and managed at the enterprise level by ITOPS Solution Delivery Client Services (email: OIT ITOPS SD EE Desktop and Device Engineering) and must be followed. VA has ELAs in place for preferred RDBMS technologies (Microsoft SQL Server and Oracle DB). Customers must get their licenses through these channels, not via independent, uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx If free trialware is utilized, the software must be purchased or removed at the end of the trial period. The VA will not being deploying or approving the use of most Office 2013 components (Access, Excel, OneNote, Outlook, PowerPoint, Publisher, Access and Word) as Solution Delivery (SD) is deploying Office 365 ProPlus (Office 2016). For Microsoft Access 2010 and prior versions, usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. For Microsoft Access 2010 and prior versions, Microsoft Access may not be used to support line of business operations requiring data durability/persistence. Further, when properly configured as a front-end client, no data at rest may be stored by Microsoft (MS) Access 2010 and prior. These older versions may only be used with sensitive data as part of a secured system when Access is configured as a client front-end to an appropriately secured MS SQL Server or MS SharePoint Server following VA SQL Server security configuration baselines (located at: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx) and connected via a Federal Information Processing Standard (FIPS) 140-2 certified encrypted connection. For Microsoft Access 2016 and subsequent versions, the security configuration baseline defined and managed at the enterprise level by ITOPS Solution Delivery Client Services (email: OIT ITOPS SD EE Desktop and Device Engineering) must comply with the DISA STIG for Microsoft Access 2016 or subsequent version. When Microsoft Access 2016 and subsequent versions are used for business processes OR used with VA sensitive data including PHI and PII, the data files must be stored in storage location encrypted by FIPS 140-2 certified encryption. Further, the files must be securely backed up on a regular basis for recovery purposes, and access controls to that encrypted storage location must be restricted to only those individuals that are allowed access to the data. Users must not solely rely on Microsoft Access application passwords to protect sensitive data from unauthorized access. Appropriate authorization and role-based access control must be enforced to ensure only authorized staff have access to the data files and controls. There must be a clear delineation of duties for staff supporting and utilizing the technology. For example, access to the security controls must be restricted to certain staff that requires it to accomplished assigned tasks. All instances used for business processes OR VA sensitive data including PHI and PII, must be reviewed and approved by the local ISO and privacy officer.

Note:

The use of Office 2013 components is unapproved as Solution Delivery (SD) has moved to baseline the use of Office 365 ProPlus (Office 2016). Office 2019 is unapproved as a baseline configuration of the version has not yet been developed.

Note: the 16.0 scheme does not limit the patches and updates the vendor releases that remedy bugs and security issues. At the time of writing, the current baselined versions of this technology is 16.0.5044.1000.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
No components have been identified for this entry.


Information Management Technologies Data Management	Desktop Database Management Systems (DBMS)	Per ELT decision, all future requests for Desktop DBMS technologies will be Prohibited.	1/13/2015 12:00:00 AM
Information Management Technologies Data Management	Relational DBMS	Microsoft SQL Server and Oracle DB are the preferred Relational DBMS platforms in VA. Per ELT decision, all future requests for Relational DBMS technologies will be Unapproved.	1/13/2015 12:00:00 AM

- The information contained on this page is accurate as of the Decision Date (02/27/2024 at 03:43:30 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (02/22/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (02/22/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES