Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Microsoft Entity Framework (EF)

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 Entity Framework (EF) is an open-source Object-Relational Mapping (ORM) framework that enables .NET developers to work with a database using .NET objects. EF uses a provider model that allows EF to map with and access many databases, which enables developers to work with data in the form of domain-specific objects and properties and create and maintain data-oriented applications with less code than in traditional applications. All EF applications have two major layers: a modeling layer and an object layer. EF uses the modeling layer to transform operations against entity objects, such as create, read, update, and delete, into equivalent operations in a connected database. EF supports Microsoft Structured Query Language (SQL) Server, DB2, MySQL, Oracle Database, Maria Database (MariaDB) and PostgreSQL. This entry covers both Entity Framework and Entity Framework Core.
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.6
Decision Date:	06/25/2024 at 15:27:59 UTC
Aliases:	Entity Framework Core; ActiveX Data Object (ADO) Entity Framework; ADO.NET Entity Framework
Introduced By:	TRM Request
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 Desupport Date
1.1	04/24/2003
2.0	11/07/2005
3.0	11/06/2006
3.5	11/19/2007
4.0	04/12/2010
4.1	04/12/2011
4.5	08/01/2012
5.0	08/15/2012
6.0	10/17/2013
6.1.x	03/10/2015
6.2.x	10/26/2017
6.3.x	09/23/2019
6.4.x	12/01/2019	06/14/2024
6.5.x	06/14/2024
Core 1.0.x	06/27/2016	06/27/2019
Core 1.1.x	11/16/2019	06/27/2019
Core 2.0.x	08/14/2017	10/01/2018
Core 2.1.x	05/30/2018	08/21/2021
Core 2.2.x	12/04/2018	12/23/2019
Core 3.0.x	09/23/2019	03/03/2020
Core 3.1.x	03/24/2020	12/13/2022
Core 5.0.x	01/14/2020	05/10/2022
Core 6.0.x	11/08/2021	11/12/2024
Core 7.0.x	11/09/2022	05/14/2024
Core 8.0.x	11/14/2023	11/10/2026

Current Decision Matrix (06/21/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

CY2023

CY2024

CY2025

Future>

Release

1.1

Unapproved

2.0

Unapproved

3.0

Unapproved

3.5

Unapproved

4.5

Unapproved

5.0

Unapproved

6.0

Unapproved

6.1.x

Unapproved

6.2.x

Unapproved

6.3.x

Unapproved

6.4.x

Approved w/Constraints
[14, 16, 17, 18, 19, 20, 21, 22]

Divest
[9, 14, 16, 20, 22, 23, 24, 25]

Divest
[9, 14, 16, 20, 23, 24, 25, 26]

Unapproved

6.5.x

Unapproved

Divest
[9, 14, 16, 20, 23, 24, 25, 26]

Core 1.0.x

Unapproved

Core 1.1.x

Unapproved

Core 2.0.x

Unapproved

Core 2.1.x

Unapproved

Core 2.2.x

Unapproved

Core 3.0.x

Unapproved

Core 3.1.x

Unapproved

Core 5.0.x

Unapproved

Core 6.0.x

Approved w/Constraints
[14, 16, 17, 18, 19, 20, 21, 22]

Divest
[9, 14, 16, 20, 22, 23, 24, 25]

Divest
[9, 14, 16, 20, 23, 24, 25, 26]

Unapproved

Core 7.0.x

Approved w/Constraints
[14, 16, 17, 18, 19, 20, 21, 22]

Divest
[9, 14, 16, 20, 22, 23, 24, 25]

Divest
[9, 14, 16, 20, 23, 24, 25, 26]

Unapproved

Core 8.0.x

Unapproved

Approved w/Constraints
[9, 14, 16, 20, 22, 23, 24, 25]

Approved w/Constraints
[9, 14, 16, 20, 23, 24, 25, 26]

Divest
[9, 14, 16, 20, 23, 24, 25, 26]

Decision Constraints


[1]	The CVE associated with this technology can only be exploited when users are using version 4 or earlier of Microsoft .NET Framework. When using this technology, version 4.5 or later of .NET Framework must be used to avoid potential security threats associated with this technology`s CVE.

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

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

[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]	Use of MySQL Database to store Protected Heath Information (PHI), Personally Identifiable Information (PII) or VA-sensitive information is unapproved until VA develops and approves a security configuration baseline to meet VA`s security requirements for PHI/PII/VA-sensitive information. See the VA baseline website site referenced above for more information. Any use of this product for PHI/PII/VA-sensitive information must be waivered for use by the AERB waiver process. At the time of this writing, NIST and NSOC had not made a distinction if any known vulnerabilities have been remediated in the enterprise edition. This will need to be considered if VA were to develop a security configuration baseline for either edition.

[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]	Use of MySQL Database to store Protected Heath Information (PHI), Personally Identifiable Information (PII) or VA-sensitive information is unapproved until VA develops and approves a security configuration baseline to meet VA`s security requirements for PHI/PII/VA-sensitive information. See the VA baseline website site referenced above for more information. Any use of this product for PHI/PII/VA-sensitive information must be waivered for use by the AERB waiver process. At the time of this writing, NIST and NSOC had not made a distinction if any known vulnerabilities have been remediated in the enterprise edition. This will need to be considered if VA were to develop a security configuration baseline for either edition

[8]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

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

[10]	Users must ensure that Microsoft .Net Framework, Microsoft Structured Query Language (SQL) Server, Microsoft Visual Studio, Oracle Database, and PostgreSQL are implemented with VA-approved baselines.

[11]	Users must ensure that Microsoft .NET Framework, Microsoft Structured Query Language (SQL) Server, Microsoft Visual Studio, Oracle Database, and PostgreSQL are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

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

[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]	This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details.

[15]	Users must ensure that Microsoft .NET Framework, Microsoft Structured Query Language (SQL) Server, Oracle Database, and PostgreSQL are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) My Structured Query Language (MySQL) Database - Community Editions, an unapproved technology, must not be used.

[16]	If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details.

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

[18]	Users must ensure that Microsoft Structured Query Language (SQL) Server, My Structured Query Language (MySQL) Database - Commercial Editions, Oracle Database and PostgreSQL are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’).

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

[20]	Users should check with their supervisor, Information System Security Officer (ISSO) 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.

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

[22]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[23]	Users must ensure that Microsoft Structured Query Language (SQL) Server, MySQL Database, MongoDB Enterprise Advanced, Oracle Database and PostgreSQL are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’). Users must not utilize Firebird and Maria Database (MariaDB) Server, as it is at the time of writing, unapproved in the TRM.

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

[25]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

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

Note:

At the time of writing, version 8.0.6 is the most current version, released 06/03/2024.

Although Entity Framework 6.x is still supported, it is no longer being developed and will only receive fixes for security issues.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

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
Microsoft Synchronization Services for ADO.NET	Microsoft Synchronization Services for ADO.NET 1.0 is an application programming interface (API) that provides the ability to synchronize data from disparate sources. This optional component enables synchronization between a server database and an SQL Compact database running on a desktop or mobile device.


Information Management Technologies Data Management	Database-Related Management Tools

- The information contained on this page is accurate as of the Decision Date (06/25/2024 at 15:27:59 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 (06/21/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (06/21/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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

EMAIL UPDATES