Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Microsoft .NET Framework

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 .NET Framework is a software framework that runs primarily on Windows. It includes a large class library and provides interoperability across several programming languages (e.g. C#, Visual Basic .NET, Windows PowerShell, J#, and others) by allowing each language to use code written in other languages. Product allows developers to build applications to a common supported standard in the Windows environment. Be sure to read the version forecast notes regarding the nuances of how this product is supported on different Microsoft OS. This entry covers the Desktop and Server Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx
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 v23.11
Decision Date:	11/16/2023 at 20:31:19 UTC
Aliases:	MS .NET Framework; Common Language Infrastructure (CLI)
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
3	11/06/2011	07/02/2011	07/02/2011
3.5	11/19/2007		07/12/2011
3.5 SP1	11/18/2008	10/01/2028	10/01/2028
4	03/31/2010		01/12/2016
4.5	08/15/2012		01/12/2016
4.5.1	10/17/2013		01/12/2016
4.5.2	05/05/2014		04/26/2022
4.6.x	08/02/2016
4.6.0 (Client)			04/26/2022
4.6.0 (Server)			04/26/2022
4.6.1 (Client)			04/26/2022
4.6.1 (Server)			04/26/2022
4.6.2 (Client)	08/02/2016
4.6.2 (Server)	08/02/2016
4.7.x	04/11/2017
4.7.0 (Client)	04/11/2017
4.7.0 (Server)	04/11/2017
4.7.1 (Client)	10/17/2017
4.7.1 (Server)	10/17/2017
4.7.2 (Client)	04/20/2018
4.7.2 (Server)	04/20/2018
4.8.x	04/18/2019
4.8.0 (Client)	04/18/2019
4.8.0 (Server)	04/18/2019

Current Decision Matrix (11/16/2023)

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

Unapproved

3.5

Unapproved

3.5 SP1

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

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

Unapproved

4.5

Unapproved

4.5.1

Unapproved

4.5.2

Unapproved

4.6.x

Unapproved

4.6.0 (Client)

Unapproved

4.6.0 (Server)

Unapproved

4.6.1 (Client)

Unapproved

4.6.1 (Server)

Unapproved

4.6.2 (Client)

Unapproved

4.6.2 (Server)

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

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

4.7.x

Unapproved

4.7.0 (Client)

Unapproved

4.7.0 (Server)

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

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

4.7.1 (Client)

Unapproved

4.7.1 (Server)

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

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

4.7.2 (Client)

Unapproved

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

4.7.2 (Server)

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

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

4.8.x

Unapproved

4.8.0 (Client)

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

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

4.8.0 (Server)

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

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

Decision Constraints


[1]	Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration, version, and deployment standards for Microsoft .NET Framework images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted.

[2]	Due to multiple NIST security vulnerabilities, extra vigilance should be applied to ensure the product remains properly patched to mitigate known and future vulnerabilities.

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

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

[6]	Microsoft .Net Framework on Windows Client version combinations, baseline configuration and deployment standards which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering (ESE) must be followed and adhered to. The current build for this baseline is version 4.7.03062.

[7]	Microsoft .Net Framework on Windows Client version combinations, baseline configuration and deployment standards which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering (ESE) must be followed and adhered to. The current build for this baseline is version 4.7.03062. Note: Microsoft .NET Framework 4.6.x to permanent divest status note it will be divested as long as it continues to be supported by updated releases of Windows 10.

[8]	Microsoft .Net Framework on Windows Client version combinations, baseline configuration and deployment standards which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering (ESE) must be followed and adhered to. The current build for this baseline includes version 4.7.2. Client users may install 4.8 on a VA endpoint, but they will not be in compliance with the VA Win 10 baseline and may need to patch version 4.8.x on their own since they may not be patched by enterprise processes. Note: Microsoft .NET Framework 4.6.x to permanent divest status note it will be divested as long as it continues to be supported by updated releases of Windows 10.

[9]	Microsoft .NET Framework on Windows Client version combinations, baseline configuration and deployment standards which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering (ESE) must be followed and adhered to. The current build for this baseline includes version 4.8.0.

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

[11]	Microsoft .NET Framework is a software framework that runs primarily on Windows. Microsoft .NET Framework on Windows Client version combinations, baseline configuration and deployment standards which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering (ESE) must be followed and adhered to. The current build for this baseline includes version 4.8.0.

[12]	Microsoft .NET Framework is a software framework that runs primarily on Windows. Microsoft .NET Framework on Windows Client version combinations, baseline configuration and deployment standards which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering (ESE) must be followed and adhered to. The current build for this standard includes version 4.8.0.

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

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

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

Note:

At the time of writing, version 4.8.1 is the most current version, released 08/09/2022. A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard versions are 4.7.2 and 4.8.0.

The following reference(s) are associated with this entry:
Type	Name	Description
Vendor Provided*	.NET Framework Supported Operating Systems	This page outlines the operating system versions that are supported by Microsoft .NET Framework.
Vendor Provided*	Lifecycle Frequently Asked Questions (FAQ) for Microsoft .NET Framework	This link points to the Lifecycle Frequently Asked Questions (FAQ) for Microsoft .NET Framework. This includes details regarding the specific versions of windows that are supported by versions of .NET Framework.
Vendor Provided*	Microsoft .NET Framework Product Lifecycle	This page outlines Microsoft`s planned support schedule for this technology.
*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
No components have been identified for this entry.


Application Technology Development Tools	Development Frameworks

- The information contained on this page is accurate as of the Decision Date (11/16/2023 at 20:31:19 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 (11/16/2023)

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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (11/16/2023)

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

EMAIL UPDATES