Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Microsoft Endpoint Configuration Manager

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 Endpoint Configuration Manager, formerly System Center Configuration Manager (SCCM) and Systems Management Server (SMS), is a systems management software for managing large groups of Windows-based and other computer systems. This technology provides remote control, patch management, software distribution, operating system deployment, network access protection, and hardware and software inventory. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO This entry covers the Desktop 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 not been assessed by the Section 508 Office. 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.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.9
Decision Date:	09/28/2023 at 15:36:19 UTC
Aliases:	Systems Management Server, System Center Configuration Manager, SCCM
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 End of Life Date	Vendor Desupport Date
2007	11/29/2007	07/09/2019	07/09/2019
2012	05/30/2012	07/12/2022	07/12/2022
1511	11/01/2015	07/12/2022	07/12/2022
1602	03/01/2016
1606	07/22/2016
1607	05/12/2016
1608	09/09/2016
1710	11/20/2017
1802	04/11/2018
1806	07/31/2018
1810	11/27/2018
1902	03/27/2019
1906	07/26/2019
1910	11/29/2019		05/29/2021
2002	04/01/2020		10/21/2021
2006	08/11/2020		02/11/2022
2103	04/05/2021		10/05/2022
2107	08/02/2021		02/02/2023
2111	12/15/2021		06/01/2023
2203	04/08/2022		10/06/2023
2207	04/08/2023
2211	12/05/2022
2303	04/10/2023

Current Decision Matrix (09/27/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

2007

Unapproved

2012

Unapproved

1511

Unapproved

1602

Unapproved

1606

Unapproved

1607

Unapproved

1608

Unapproved

1710

Unapproved

1802

Unapproved

1806

Unapproved

1810

Unapproved

1902

Unapproved

1906

Unapproved

1910

Unapproved

2002

Unapproved

2006

Unapproved

2103

Divest
[12, 16, 23, 24, 25, 26, 27]

Divest
[12, 23, 24, 25, 27, 28]

Divest
[12, 23, 24, 25, 27, 29]

Unapproved

2107

Approved w/Constraints
[12, 16, 23, 24, 25, 26, 27]

Divest
[12, 23, 24, 25, 27, 28]

Divest
[12, 23, 24, 25, 27, 29]

Divest
[12, 24, 27, 29, 30, 31]

Unapproved

2111

Unapproved

2203

Approved w/Constraints
[12, 16, 23, 24, 25, 26, 27]

Approved w/Constraints
[12, 23, 24, 25, 27, 28]

Divest
[12, 23, 24, 25, 27, 29]

Divest
[12, 24, 27, 29, 30, 31]

Unapproved

2207

Unapproved

2211

Unapproved

Approved w/Constraints
[12, 23, 24, 25, 27, 28]

Divest
[12, 23, 24, 25, 27, 29]

Divest
[12, 24, 27, 29, 30, 31]

Unapproved

2303

Unapproved

Approved w/Constraints
[12, 23, 24, 25, 27, 29]

Approved w/Constraints
[12, 24, 27, 29, 30, 31]

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]	Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities. Additionally, if PII/PHI/VA sensitive information is involved, FIPS 140-2 certified encryption must be used to encrypt data in transit and the technology must be implemented within the VA production network (not in a DMZ) or additional mitigating controls must be documented in an approved System Security Plan (SSP). Finally, configuration and deployment standards for Microsoft Systems Center Configuration Manager (SCCM) 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.

[3]	Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities. Per VA Handbook 6500, Federal Information Processing Standards (FIPS) 140-2 certified encryption must be used to encrypt data in transit and at rest if Personally Identifiable Information (PII), Protected Health Information (PHI) or VA sensitive information is involved or additional mitigating controls must be documented in an approved System Security Plan (SSP). Additionally, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)). Finally, configuration and deployment standards for Microsoft Systems Center Configuration Manager (SCCM), 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.

[4]	Configuration and deployment standards for Microsoft Systems Center Configuration Manager (SCCM) which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering (Mail: VA IT Engineering CS Desktop Technologies Team) must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information.

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

[7]	Versions newer than 2012 which are listed in an evaluation status 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.

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

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

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

[11]	Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[12]	Use of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing analysis with this technology need to work closely with system owners and agree on security scanning rules, such as the assets scanned, along the schedule and frequency of those scans.

[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]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

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

[16]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft Internet Information Services (IIS), and Microsoft .NET Framework are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[17]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[18]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

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

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

[21]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

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

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

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

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

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

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

[28]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Structured Query Language (SQL) Server and Microsoft Internet Information Services (IIS), are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[29]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Structured Query Language (SQL) Server and Microsoft Internet Information Services (IIS) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

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

[31]	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 2303 (5.00.9106.1022) is the most current version, released 04/10/2023.

A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 2211 (5.00.9096.1024), and version 2303 (5.00.9106.1022) is under testing and development for 4-6 weeks from 09/20/2023

The following reference(s) are associated with this entry:
Type	Name	Description
Vendor Provided*	Updates for Microsoft Endpoint Configuration Manager	This site links to Microsoft`s list of updates for Microsoft Endpoint Configuration Manager.
Vendor Provided*	Release Notes	This website links to the release notes for this technology.
Vendor Provided*	Updates and servicing for Configuration Manager	This site lists current updates and versioning details.
*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
Advanced Client	The Advanced Client is a software package that is installed on supported Desktops or Servers and allows functions to be carried out on the device by the servers.
Application Delivery	Application Delivery allows administrators to create one application package that can be delivered to all user devices.
Compliance & Settings Management	Compliance & Settings Management allows for monitoring of client`s configuration and settings, and allows the creation of a baseline for the desired configuration state, and then helps ensure that all user devices comply with that baseline through either auto remediation or alerts.
Device Management & Client Health & Monitoring	Device Management & Client Health & Monitoring provides for device configuration, device status and health monitoring and alerting.
Inventory and Asset Intelligence	Inventory and Asset Intelligence allows for hardware and software inventory and associated analysis and reporting in the organization.
Operating System Deployment (OSD)	Operating System Deployment is used to automate OS deployments through the use of task sequences.
Power Management	Power Management works with the capabilities built into the Windows operating system to manage power settings.
Remote Tools	Remote Tools allows for remote system administration and control. Secure RDS (Remote Desktop Services) Connections use FIPS140-2 compliant encryption. Remote Tools must use Federal Information Processing Standard (FIPS) Publication 140-2, (FIPS PUB 140-2) compliant encryption and should only be used within the VA Production network and not in a demilitarized zone.
Software Update Management	Software Update Management delivers and manages updates to IT systems across the enterprise including updates of Microsoft products, third-party applications, hardware drivers, and system BIOS to a variety of devices, including desktops, laptops, servers, and mobile devices.
Virtual Desktop Management	Virtual Desktop Management is used to manage client desktops, thin clients, mobile devices, and virtual desktops. It extends inventory, updating, and configuration capabilities to VDI sessions and supports application delivery across multiple desktop virtualization platforms.


Systems Management Systems Management Tools	Data Center Automation Software
Systems Management Systems Management Tools	System Change and Configuration Management

- The information contained on this page is accurate as of the Decision Date (09/28/2023 at 15:36: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 (09/27/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

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (09/27/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

Architectural Risks

EMAIL UPDATES