Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 25.12

Kerberos Configuration Manager for Structured Query Language (SQL) Server

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:	Kerberos Configuration Manager for Structured Query Language (SQL) Server is an authentication software. This software provides users with a secure method to authenticate users and server entities on a network. When users use Kerberos authentication with (SQL Server), a Service Principal Name (SPN) must be registered with Active Directory, which is playing the role of the Key Distribution Center in a Windows domain. The Kerberos Configuration Manager for SQL Server is a diagnostic technology that helps users to troubleshoot Kerberos related connectivity issues with SQL Server, SQL Server Reporting Services (SSRS), and SQL Analysis Services (SSAS).
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 System Security Officer (ISSO), 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 v25.6
Decision Date:	06/23/2025 at 02:36:57 UTC
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).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
3.1	01/31/2017
4.1	11/22/2017
4.2.x	01/17/2020

Current Decision Matrix (06/13/2025)

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 System Security Officer (ISSO), 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 VAIT 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.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized 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	Authorized w/ Constraints (POA&M): 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	Authorized w/ Constraints (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 unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): 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 authorized 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 authorized 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.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2025

CY2026

CY2027

Future>

Release

3.1

Authorized w/ Constraints (POA&M)

4.1

Authorized w/ Constraints (POA&M)

4.2.x

Authorized w/ Constraints
[9, 11, 12, 14, 15, 16, 17]

Note:

At the time of writing, version 4.2.1 is the most current version, released 07/15/2024.

Decision Constraints


[9]	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]	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 authorized and the user should take the proper steps to decline those installations.

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

[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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

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

[16]	Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

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

Name	Description
No components have been identified for this entry.


Security Identity and Access Management	Authentication
Systems Management Systems Management Tools	System Change and Configuration Management

General Analysis

Adoption Benefits

This technology may improve productivity for specific staff whose responsibilities include troubleshooting Kerberos related connectivity issues with SQL Server.
This is a well-documented technology.
There is no licensing fee associated with this technology.
The vendor of this technology is an industry leader in the subject matter.

Adoption Risks

There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
This technology was discovered by an automated software inventory application rather than being requested via a TRM user request.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
There is no indication based on either the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
This technology can integrate with and alter database technologies.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
This technology is available as freeware. As such this technology may be without clearly defined support options which may result in suboptimal enterprise level support.

Architectural Benefits

This technology can use a VA-preferred database.

Architectural Risks

This technology is not portable as it runs only on Windows platforms.

- The information contained on this page is accurate as of the Decision Date (06/23/2025 at 02:36:57 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 25.12

General Information

Vendor Release Information

Current Decision Matrix (06/13/2025)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional 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 25.12

General Information

Vendor Release Information

Current Decision Matrix (06/13/2025)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework